Skip to content

☂️ [task] remove DartProject #58734

New issue

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

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

Already on GitHub? # to your account

Closed
6 of 10 tasks
pq opened this issue May 12, 2022 · 1 comment
Closed
6 of 10 tasks

☂️ [task] remove DartProject #58734

pq opened this issue May 12, 2022 · 1 comment
Assignees
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). devexp-linter Issues with the analyzer's support for the linter package legacy-area-analyzer Use area-devexp instead. type-code-health Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable type-task A well-defined stand-alone task

Comments

@pq
Copy link
Member

pq commented May 12, 2022

DartProject has never worked completely w/ server (see #57250) and since it's creation, LinterContext has been introduced which, moving forward, is the right way to answer the kinds of questions it was designed to address. Since the lints that are currently using it are failing fast, my thinking is that we can safely remove all references to it from the existing lints as a non-breaking change. We can then follow-up with a new set of changes that updates the (already) broken lints to use LinterContext methods. These changes will produce a bunch of new diagnostics which though (now) correct may have ecosystem impact so we'll want to carefully vet their roll-out.


Plan

@pq pq added type-task A well-defined stand-alone task type-code-health Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). labels May 12, 2022
@pq pq self-assigned this May 12, 2022
copybara-service bot referenced this issue May 16, 2022
See: https://github.com/dart-lang/linter/issues/3395

Change-Id: Id0d342d4a15676acbe5bdd26b245b1325764922f
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/244760
Commit-Queue: Phil Quitslund <pquitslund@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
copybara-service bot referenced this issue May 19, 2022
See: https://github.com/dart-lang/linter/issues/3395

Change-Id: I6e4213983abae2b48e4bbbbbc766784e1756b0ed
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/245240
Commit-Queue: Phil Quitslund <pquitslund@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
@pq
Copy link
Member Author

pq commented Nov 14, 2022

This is at a natural stopping point. If the functionality additions get picked up, they can get tracked in their own issues.

@pq pq closed this as completed Nov 14, 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 19, 2024
@devoncarew devoncarew transferred this issue from dart-archive/linter Nov 19, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). devexp-linter Issues with the analyzer's support for the linter package legacy-area-analyzer Use area-devexp instead. type-code-health Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable type-task A well-defined stand-alone task
Projects
None yet
Development

No branches or pull requests

2 participants