CPLAT-11574: Investigate CLI integration
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 432
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
CPLAT-11574
Providing diagnostics in the IDE is valuable, but there's also value in running those diagnostics in CI to ensure a certain set of changes doesn't introduce bad code.
We need to determine whether we can run the plugin from the command-line using existing tooling:
dartanalyzer(doesn't work out of the box)tuneup
There may be special flags or something we need to pass to pull in plugins, if the tool doesn't run plugins out of the box.
If we can't, we should research whether the Dart team plans on supporting that.
If it's not supported and won't be for a while, we may want to follow up with work on a custom tool to run these checks via command-line.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by testing whether dartanalyzer and tuneup can run the plugin from the command line, including any plugin-related flags or configuration. Determine whether current Dart tooling supports this, check whether future support is planned if it does not, and document the findings and whether a custom command-line tool should follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100