Skip to content

Plugin promoting #58253

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
amorenew opened this issue Oct 26, 2020 · 3 comments
Open

Plugin promoting #58253

amorenew opened this issue Oct 26, 2020 · 3 comments
Labels
area-devexp For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages. devexp-linter Issues with the analyzer's support for the linter package P3 A lower priority bug or feature request type-documentation A request to add or improve documentation type-enhancement A request for a change that isn't a bug

Comments

@amorenew
Copy link

I found a very helpful plugin and I wonder why there is no section for popular linter plugins?

The plugin I found is there:
https://github.com/wrike/dart-code-metrics

@bwilkerson
Copy link
Member

We should definitely consider promoting contributions from the community like this.

A couple of nits. First, technically plugins are supported by the analysis server, not the linter, so the linter documentation isn't necessarily the best place for such a list. (The linter package provides a subset of the analysis checks provided by the analysis server. The linter package can be thought of as a built-in plugin.) Second, I don't believe that we currently have any way of measuring the popularity of plugins, though it would be interesting to think about how best to do that so that we could use popularity as an indicator of quality.

@amorenew
Copy link
Author

@bwilkerson popularity is not a big issue for now as the plugins will be few
The main purpose of plugins is to add common lint rules from other languages like Javascript ESLint
I think plugins will be a maximum of 5 and if it will be more we could use sub-readme

But anyway I couldn't see any other plugin than dart-code-metrics if you know others it would be nice to mention it.

@pq pq added type-documentation A request to add or improve documentation type-enhancement A request for a change that isn't a bug labels Dec 23, 2020
@incendial
Copy link
Contributor

Considering this comment #58533 the problem of analyzer plugins discoverability is real and I personally think that any team can benefit from a code quality tools like Dart Code Metrics plugin.

A couple of nits. First, technically plugins are supported by the analysis server, not the linter, so the linter documentation isn't necessarily the best place for such a list.

If it's appropriate to mention our plugin somewhere in the docs, could you help find the right place for it? The only example I have is Flutter state management solutions page https://flutter.dev/docs/development/data-and-backend/state-mgmt/options and it really helps people find a state manager.

@pq pq added the P3 A lower priority bug or feature request label Nov 15, 2022
@devoncarew devoncarew added devexp-linter Issues with the analyzer's support for the linter package legacy-area-analyzer Use area-devexp instead. labels Nov 18, 2024
@devoncarew devoncarew transferred this issue from dart-archive/linter Nov 18, 2024
@bwilkerson bwilkerson added area-devexp For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages. and removed legacy-area-analyzer Use area-devexp instead. labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-devexp For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages. devexp-linter Issues with the analyzer's support for the linter package P3 A lower priority bug or feature request type-documentation A request to add or improve documentation type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

5 participants