linter repo issue templates are hard to follow for a bug report

[srawlins]

Describe the issue

Here is the screen I am presented when filing an issue:

Maybe most people follow this better than I, but here's how my process went:

• "Issue report - Create a report to help us make the linter better." I don't really know what that means, but I know for certain I don't want to create a report.
• "Lint proposal - Propose a new lint rule or a modification to an existing one." Er... I suppose I'm proposing a modification, when I'm filing a bug.

This leads me to this template:

This looks a little odd, as I'm "proposing a modification." None of these prompts seem to make sense... This led me to fill out the very bizzare issue: #58876

[bwilkerson]

I agree that the current options are confusing. Let's figure out the different kinds of issues users typically report (that we want to gather different information for) and create a menu based on that.

I can think of a couple:

Lint proposal
Propose or request the addition of a new lint rule.

Lint bug report
Report a bug with or propose a modification to, an existing lint.

Dart team recommended lints
Propose including or excluding a lint in the core, recommended, or flutter lint sets, or discuss any other aspect of those lint sets.

Request a fix for a lint
Request that a fix be added for an existing lint.

What am I missing? Do we need/want the "Report a security vulnerability" item?

[srawlins]

Hmm what's the difference between "Lint bug report" and "Request a fix for a lint"?

I can't think of any other items though.

[pq]

Hmm what's the difference between "Lint bug report" and "Request a fix for a lint"?

Maybe the intention is "Quick Fix"?

Otherwise, LGTM!

[bwilkerson]

Yes, I meant quick fix. (I like having a pointer to other repos where the issue is more appropriate to limit the number of issues we have to transfer.) Clearly it could use some word-smithing. :-)

[srawlins]

Ah of course. Yes, I like it!

[srawlins]

Thanks @pq !