- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 15 Feb, 2017 1 commit
-
-
Todd Volkert authored
Fixes #7166 Also cleans up from an aborted attempt at #5793
-
- 13 Feb, 2017 2 commits
-
-
Phil Quitslund authored
Fixes: #8087.
-
Dan Rubel authored
* move flutter user analysis options file * add comments referencing each of the analysis options files
-
- 23 Jan, 2017 2 commits
-
-
Ian Hickson authored
...now that we have generic methods, their types need to be specified too.
-
Ian Hickson authored
See https://github.com/dart-lang/sdk/issues/28463, which I think is a regression. This also fixes the regression introduced by https://codereview.chromium.org/2559773002 whereby we were no longer checking any of the lints.
-
- 13 Jan, 2017 1 commit
-
-
Adam Barth authored
That test intentionally has analysis errors to check how the tools react to that situation.
-
- 15 Dec, 2016 1 commit
-
-
John McCutchan authored
- [x] Introduce DependencyChecker which can determine if any dependencies have been modified. - [x] Move the DartDependencyBuilder into a separate file. - [x] Add unit tests for DartDependencyBuilder. - [x] Add unit tets for DependencyChecker Part of #7014
-
- 22 Nov, 2016 1 commit
-
-
Devon Carew authored
-
- 07 Nov, 2016 1 commit
-
-
Devon Carew authored
-
- 07 Oct, 2016 1 commit
-
-
Adam Barth authored
This patch adds `@checked` everywhere is needed to remove the `strong_mode_invalid_method_override` strong mode error.
-
- 12 Sep, 2016 1 commit
-
-
Dan Rubel authored
fixes https://github.com/flutter/flutter/issues/5788
-
- 09 Sep, 2016 2 commits
-
-
Dan Rubel authored
This adds and enables a raft of new analysis options for the flutter repository, many of which are commented out until we clean up our code and/or address any linter false positives.
-
Dan Rubel authored
This aligns the comments and fixes some misspellings in the three related analysis options files. There will be a follow on PR with more controversial changes to the repo level analysis options.
-
- 08 Sep, 2016 1 commit
-
-
Dan Rubel authored
This updates the flutter analyze command to use the .analysis_options_flutter_analyze in the repo root when either the --flutter-repo flag is supplied or the sources being analyzed reside in the flutter repo.
-
- 19 Aug, 2016 1 commit
-
-
Devon Carew authored
-
- 20 May, 2016 1 commit
-
-
Ian Hickson authored
-
- 05 May, 2016 1 commit
-
-
krisgiesing authored
* Move global analysis options file to the repo root Also restore the analysis options file for stocks example, since the global options trigger warnings on generated intl files. * Remove obsolete analysis options file for Material Gallery example
-
- 04 May, 2016 1 commit
-
-
krisgiesing authored
This aligns the analysis options used by 'flutter analyze' with the options used by Atom.
-
- 28 Apr, 2016 1 commit
-
-
Adam Barth authored
Related to #3608
-
- 11 Apr, 2016 1 commit
-
-
pq authored
As per https://github.com/dart-lang/sdk/issues/25723, moves last command-line flag to `.analysis_options`.
-
- 08 Apr, 2016 1 commit
-
-
Devon Carew authored
-
- 04 Apr, 2016 1 commit
-
-
Ian Hickson authored
* Enable the lint require documentation. * Track how many public Flutter members lack docs * Rename the .analysis_options file This makes Atom happier in the flutter_tools package.
-
- 14 Mar, 2016 4 commits
-
-
Hixie authored
-
Hixie authored
Also, some minor cleanup in activity.dart, though much more is needed (see https://github.com/flutter/flutter/issues/2668).
-
Hixie authored
-
Ian Hickson authored
-
- 12 Mar, 2016 2 commits
- 11 Mar, 2016 3 commits
-
-
pq authored
More groundwork to get `analyze` and IDE output to agree. See: https://github.com/dart-lang/sdk/issues/25723
-
Ian Hickson authored
Well, all the easy ones, anyway. For some reason `// ignore:` isn't working for me so I've disabled lints that need that. Also disabled those that require a ton of work (which I'm doing, but not in this PR, to keep it reviewable). This adds: - avoid_init_to_null - library_names - package_api_docs - package_names - package_prefixed_library_names - prefer_is_not_empty - sort_constructors_first - sort_unnamed_constructors_first - unnecessary_getters_setters
-
Hixie authored
Since we removed our operator== overload, we can now allow people to put these in collections again. Also, turn on two more analyzer lints: avoid_empty_else and hash_and_equals.
-
- 10 Mar, 2016 1 commit
-
-
Devon Carew authored
-