Skip to content

📌 Meta: Implementing existing rules #354

@JoshuaKGoldberg

Description

@JoshuaKGoldberg

As of #303 and related issues & PRs, https://flint.fyi/rules now has a big table comparing rule implementations across linters. Those rule names are mostly what I'd like to have implemented in Flint.

As of writing, there are approximately 575 rules to be implemented. That includes rules across languages (JSON, Markdown, TypeScript, ...), plugins (core-to-language, sorting, ...), and plugin presets (logical, stylistic, ...). That's quite a lot of rules to implement!

I'm going to try to automate rule implementations as much as possible. As much as I find the bombastic hype around modern AI irritating, this actually is quite a good job for it. Each of the rules in the table have at least one reference implementation + tests + docs page to pull from. And the more important a rule is, the more likely it has multiple references to go off of.

#348 is the first PR that I've sent using Copilot. Copilot ... well, it got the job mostly done. It needed a lot of extra prompting and hinting. Overall it didn't save me time for this one PR but amortized across many dozens or even hundreds of PRs I think it will be worth it.

Once I've hit the limits of what Copilot is able to do effectively, I'll reach for a purportedly more capable tool such as Claude.

https://github.com/JoshuaKGoldberg/flint-rule-issue-creator is a handy CLI I made to create issues based on comparisons data.

Copilot PR instructions were here. I moved them to #365 -> #399.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions