1. 17 Feb, 2016 1 commit
  2. 10 Feb, 2016 1 commit
  3. 09 Feb, 2016 1 commit
  4. 31 Jan, 2016 1 commit
  5. 28 Jan, 2016 1 commit
  6. 24 Jan, 2016 1 commit
  7. 16 Jan, 2016 2 commits
  8. 13 Jan, 2016 3 commits
  9. 12 Jan, 2016 1 commit
  10. 16 Dec, 2015 1 commit
  11. 14 Dec, 2015 2 commits
  12. 04 Dec, 2015 1 commit
    • Ian Hickson's avatar
      Analyzer improvements · 0290622b
      Ian Hickson authored
      - strengthen analyzer against error messages that point past the
        bottom of the file.
      
      - ignore any errors in intl's auto-generated files.
      0290622b
  13. 29 Nov, 2015 1 commit
    • Adam Barth's avatar
      Clean up code organization in flutter_tools · 9662d49e
      Adam Barth authored
      1) Moved basic utility code into base/ directory to make it clear which code
         doesn't depend on Flutter-specific knowldge.
      2) Move the CommandRunner subclasses into a runner/ directory because these
         aren't commands themselves.
      9662d49e
  14. 28 Nov, 2015 1 commit
    • Ian Hickson's avatar
      dev/update_packages.dart --upgrade · 92a62120
      Ian Hickson authored
      Add an --upgrade flag to the dev/update_packages.dart flag which runs
      'pub upgrade' instead of 'pub get'. Tell people to use this when using
      'flutter analyze' since 'pub get' doesn't have the same guarantee of
      getting everything in sync.
      92a62120
  15. 20 Nov, 2015 1 commit
  16. 17 Nov, 2015 1 commit
  17. 12 Nov, 2015 3 commits
    • Hixie's avatar
      Make the analyzer actually work. · 8ab229f8
      Hixie authored
      Turns out that ignoring all error lines that match the empty string is a
      poor way to go.
      
      Also, we have to update all the example packages now too, since we
      analyze them. So just have travis use our update script.
      
      Also, remove flutter_tools' old travis stuff. It's now part of a bigger
      repo.
      
      Also, make travis use the dev Dart SDK, since we need the new analyzer.
      Stable is way too out of date, e.g. it still complains about libraries
      not having names and mixins using 'super', and the strong mode hints are
      even more aggressive than on dev.
      8ab229f8
    • Hixie's avatar
      Delete analyzer temporary directories · 4a5713ac
      Hixie authored
      4a5713ac
    • Hixie's avatar
      flutter analyze command · a0227cab
      Hixie authored
      Other changes in this patch:
      - Make the 'flutter' tool say "Updating flutter tool..." when it calls
        pub get, to avoid confusion about what the pub get output is about.
      - Make the bash flutter tool call pub get when the revision has
        changed. (This was already happening on Windows.)
      - Fix a raft of bugs found by the analyzer.
      - Fix some style nits in various bits of code that happened to be near
        things the analyzer noticed.
      - Remove the logic in "flutter test" that would run "pub get", since
        upon further reflexion it was determined it didn't work anyway.
        We'll probably have to add better diagnostics here and say to run the
        updater script.
      - Remove the native velocity tracker script, since it was testing code
        that has since been removed.
      
      Notes on ignored warnings:
      - We ignore warnings in any packages that are not in the Flutter repo or
        in the author's current directory.
      - We ignore various irrelevant Strong Mode warnings. We still enable
        strong mode because even though it's not really relevant to our needs,
        it does (more or less accidentally) catch a few things that are
        helpful to us.
      - We allow CONSTANTS_LIKE_THIS, since we get some of those from other
        platforms that we are copying for sanity and consistency.
      - We allow one-member abstract classes since we have a number of them
        where it's perfectly reasonable.
      - We unfortunately still ignore warnings in mojom.dart autogenerated
        files. We should really fix those but that's a separate patch.
      - We verify the actual source file when we see the 'Name non-constant
        identifiers using lowerCamelCase.' lint, to allow one-letter variables
        that use capital letters (e.g. for physics expressions) and to allow
        multiple-underscore variable names.
      - We ignore all errors on lines that contain the following magic
        incantation and a "#" character:
          // analyzer doesn't like constructor tear-offs
      - For all remaining errors, if the line contains a comment of the form
          // analyzer says "..."
        ...then we ignore any errors that have that "..." string in them.
      a0227cab