Skip to content

Create NPM project for custom linter rule for replacing aliased imports #3

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

Closed
CDeltakai opened this issue Mar 14, 2025 · 1 comment · Fixed by #4 or #6
Closed

Create NPM project for custom linter rule for replacing aliased imports #3

CDeltakai opened this issue Mar 14, 2025 · 1 comment · Fixed by #4 or #6
Assignees
Labels
development Standard development

Comments

@CDeltakai
Copy link
Contributor

Specification

https://github.com/MatrixAI/Polykey-Enterprise/pull/158 implements a custom linter rule which will replace aliased imports in selected folders (namely the src/ folder) with relative imports where possible.

We want to turn this custom rule into an npm project which we can import into our other codebases as a dev-dependency to enforce these import rules.

Additionally, we should try to implement it like some of the typescript es-lint packages where there is no need to import the package directly into the config and we can instead write the names of the packages and rules directly and utilise it from there.

Additional context

PR implementing the custom rule as a single-repo script: https://github.com/MatrixAI/Polykey-Enterprise/pull/158
Initial issue: https://github.com/MatrixAI/Polykey-Enterprise/issues/157

Tasks

  1. Create new repo for a new Node.js package that will implement the custom linter rule
  2. Properly structure and move custom linter script from the PR into package repo
  3. Prepare it for import into existing codebases
@tegefaulkes
Copy link
Contributor

This is still being worked on.

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