-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Linter for pubspec.yaml #19407
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
Comments
This comment was originally written by @kaendfinger I'll work on a 'pub validate' command |
This comment was originally written by @seaneagan I wouldn't mind adding this to den: http://pub.dartlang.org/packages/den which is focused on pubspec analysis and manipulation, and it should be trivial to add once issue #21169 is fixed. Of course, I'd be fine with it being in pub itself as well. |
This comment was originally written by @seaneagan The |
A number of pub-related lints are being proposed for the dart linter (https://github.com/dart-lang/linter/) and I'm well on the way to having the plumbing in place to start implementing them... Feel free to add ideas there! |
This issue has been moved to dart-lang/pub#1009. |
This issue was originally filed by [email protected]
Based on this discussion at the Sublime Text package repo:
guillermooo/dart-sublime-bundle#94
At the moment, when you run
pub install
and the pubspec.yaml contains errors, you get error information spat back at you. But there is nosanitize only
option; you must run the install process every time.If you could tell pub to simply check the file for errors, the user could be warned in advance by tools such as Sublime Text.
This is a long-winded way of asking for a
pubspecanalyzer
in the spirit ofdartanalyzer
. :)The text was updated successfully, but these errors were encountered: