-
Notifications
You must be signed in to change notification settings - Fork 15
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
chore: let travis build with dev channel of dart #72
Conversation
0b2867d
to
c3453ad
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may also want to consider testing running this library's code with preview dart 2 at runtime. That'll catch issues that the analyze won't be able to (runtime only ones). Something like:
dart --preview-dart-2 example/simpleusage.dart
dart --preview-dart-2 test/mustache_all.dart
dartanalyzer --strong --fatal-warnings lib/*.dart test/*.dart | ||
dartanalyzer="dartanalyzer --strong --fatal-warnings lib/*.dart test/*.dart" | ||
if [ "$TRAVIS_DART_VERSION" = "dev" ]; then | ||
dartanalyzer="$dartanalyzer --preview-dart-2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just fyi, at this point, --preview-dart-2
to the analyzer is the same as --strong
plus supporting optional new and const.
I'll give it a try. If not in |
Just FYI, all of the type changes for Dart 2 are backwards compatible with Dart 1. There are some constant renames (dart:convert JSON ==> json) that will be removed from Dart 1 - doing those renames wouldn't be backwards compatible. |
--preview-dart-2
to the analyzer