Skip to content

Repo: Internal linter rule for absolute imports from eslint packages #8345

Closed
@kirkwaiblinger

Description

@kirkwaiblinger

Suggestion

This issue comes from #8216 (comment).
When contributors are working on this codebase, their editors may suggest long relative imports to other packages in the repo. We'd like to be sure, though, that they use the absolute paths from the repo root, e.g. @typescript-eslint/utils, rather than these long relative paths.

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issuelocked due to agePlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.repo maintenancethings to do with maintenance of the repo, and not with code/docs

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions