Expose true filename to rules

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.

[btmills]

Option 2, getPhysicalFilename(), works for me.

[ljharb]

This should be reopened; it affects the plugin ecosystem.