-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Gather analyzer
package API references in a facade class.
#57431
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
Labels
devexp-linter
Issues with the analyzer's support for the linter package
legacy-area-analyzer
Use area-devexp instead.
type-task
A well-defined stand-alone task
Comments
dart-archive/linter#395 gets us most of the way there. Still TODO:
which are trickier since they reach into tokens and the resolver. |
pq
referenced
this issue
in dart-archive/linter
Feb 3, 2017
* Gather analyzer API references in a facade class. See: #394 * formatting
pq
referenced
this issue
in dart-archive/linter
Feb 3, 2017
* roundup all non-API calls * enable `implementation_imports` lint Fixes: #394
pq
referenced
this issue
in dart-archive/linter
Feb 3, 2017
* roundup all non-API calls * enable `implementation_imports` lint Fixes: #394
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
devexp-linter
Issues with the analyzer's support for the linter package
legacy-area-analyzer
Use area-devexp instead.
type-task
A well-defined stand-alone task
Part of the effort to manage
analyzer
dependencies.See: #57427 .
The text was updated successfully, but these errors were encountered: