Skip to content

Expose true filename to rules #11989

Description

@Conduitry

The version of ESLint you are using.

6.0.1

The problem you want to solve.

This. Some rules, like eslint-plugin-import's no-unresolved, need to know the true path of the current file, not a path that's been potentially assembled using a processor's named code block.

Your take on the correct solution to problem.

I'm not entirely sure, but perhaps a new option to context.getFilename() to return the true path rather than the one potentially created from a processor's named code blocks.

Are you willing to submit a pull request to implement this change?

Yes.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    acceptedThere is consensus among the team that this change meets the criteria for inclusionarchived due to ageThis issue has been archived; please open a new issue for any further discussioncoreRelates to ESLint's core APIs and featuresenhancementThis change enhances an existing feature of ESLintgood first issueGood for people who haven't worked on ESLint before

    Type

    No type

    Projects

    • Status
      Complete

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions