Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create new rule for no aliasing imports and clean out repo for use for future rules #4

Merged
merged 4 commits into from
Mar 14, 2025

Conversation

CDeltakai
Copy link
Contributor

Description

This PR implements the first custom rule which is no-alias-imports which will disallow the use of alias imports in configured files and optionally provide an auto-fix that will replace said import with a relative import instead.

This PR will also clean out the repo of unnecessary files from its original template (js-logger) and prepare it for use as a linter plugin.

Issues Fixed

Tasks

  • 1. Implement no-aliased-imports linting rule
  • 2. Clean out repo of unnecessary files from original template rpo
  • 3. Prepare it for import into other codebases

Final checklist

  • Domain specific tests
  • Full tests
  • Updated inline-comment documentation
  • Lint fixed
  • Squash and rebased
  • Sanity check the final build

@CDeltakai CDeltakai self-assigned this Mar 14, 2025
@CDeltakai CDeltakai merged commit 76649e7 into staging Mar 14, 2025
2 of 4 checks passed
@tegefaulkes
Copy link
Contributor

Is this done? why was it merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Create NPM project for custom linter rule for replacing aliased imports
2 participants