feat(linter/plugins): implement SourceCode.getDisableDirectives method

[KuSh]

Used by eslint-plugin-unicorn

It crashes when trying to use it through jsPlugins (for unicorn/expiring-todo-comments)

ESLint documentation says its optional but unicorn doesn't seem to guard against its absence

[overlookmotel]

Sorry I'm so slow to get to this PR.

As I mentioned on #21492, ideal solution would be to pass the disable comments from Rust side (as we're already doing the work of parsing comments there), but I'm not sure how easy that would be.

A pure-JS solution like in this PR is a good interim solution (and who knows how long it'll be until we get to doing it "properly", so "interim" might actually mean quite a long time).

All that's lacking, I think, is:

1. Tests (apps/oxlint/test/fixtures).
2. A citation showing the match patterns match either (a) ESLint or (b) whatever pattern we use on Rust side in Oxlint.

@KuSh Would you have the time and inclination to add those to this PR?

[KuSh]

Yes sure, I'll see if I find time in the next weeks! Thanks for the feedback @overlookmotel

I thought of trying to pass the disable comments from Rust side, but as that part seems to be touchy and hard to optimize, and that specific function doesn't seem to be used a lot by plugins. I tought I would propose a simpler first version to have feedback ^^

[KuSh]

@overlookmotel I've added a fixture test. I've also added a comment about what patterns match. I hope that's what you had in mind.

[christophehurpeau]

This is the last thing missing to fully migrate to oxlint. If this PR is merged it would be much appreciated 🙏

[camc314]

As I mentioned on #21492, ideal solution would be to pass the disable comments from Rust side (as we're already doing the work of parsing comments there), but I'm not sure how easy that would be.

This is going to be a bunch of extra work, which I don't think is currently worth it. We can address this in future

A pure-JS solution like in this PR is a good interim solution (and who knows how long it'll be until we get to doing it "properly", so "interim" might actually mean quite a long time).

This has been implemented - I've pushed up a follow up commit added support for the enable comments.

All that's lacking, I think, is:

1. Tests (apps/oxlint/test/fixtures).
2. A citation showing the match patterns match either (a) ESLint or (b) whatever pattern we use on Rust side in Oxlint.

@ KuSh Would you have the time and inclination to add those to this PR?

I think both of these should be done!

[camc314]

@overlookmotel going to merge this now-ish, if you could take a retrospective look that would be appreciated!

thanks!

[Copilot]

Pull request overview

This PR adds SourceCode.getDisableDirectives() to the JS plugin SourceCode surface so ESLint-compatible plugins (notably unicorn helpers) can inspect inline disable/enable comments instead of crashing when the method is missing.

Changes:

• Adds a new directives.ts helper that parses eslint-* / oxlint-* disable and enable comments into { problems, directives }.
• Exposes getDisableDirectives on the shared JS plugin SOURCE_CODE object.
• Adds a new CLI fixture covering plugin access to the method and snapshotting the reported directive counts.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
apps/oxlint/test/fixtures/getDisableDirectives/plugin.ts	New fixture plugin that calls sourceCode.getDisableDirectives() and asserts returned counts/shape.
apps/oxlint/test/fixtures/getDisableDirectives/output.snap.md	Snapshot for the new fixture’s expected lint output.
apps/oxlint/test/fixtures/getDisableDirectives/files/test.js	Test input containing various oxlint/eslint disable and enable directives.
apps/oxlint/test/fixtures/getDisableDirectives/.oxlintrc.json	Enables the new fixture plugin/rule.
apps/oxlint/src-js/plugins/source_code.ts	Wires the new directive helper onto the public SourceCode API.
apps/oxlint/src-js/plugins/directives.ts	Implements directive parsing and malformed-comment problem collection.

[camc314]

thank you!

[KuSh]

@camc314 follow up PR #22238 as this wasn't enough to make unicorn work (at least for expiring-todo-comments rule)