1. 22 Oct, 2017 1 commit
  2. 21 Sep, 2017 1 commit
  3. 14 Jul, 2017 1 commit
  4. 30 Jun, 2017 1 commit
  5. 23 Jun, 2017 1 commit
    • Ian Hickson's avatar
      Deep linking: automatically push the route hiearchy on load. (#10894) · 9adb4a78
      Ian Hickson authored
      The main purpose of this PR is to make it so that when you set the
      initial route and it's a hierarchical route (e.g. `/a/b/c`), it
      implies multiple pushes, one for each step of the route (so in that
      case, `/`, `/a`, `/a/b`, and `/a/b/c`, in that order). If any of those
      routes don't exist, it falls back to '/'.
      
      As part of doing that, I:
      
       * Changed the default for MaterialApp.initialRoute to honor the
         actual initial route.
      
       * Added a MaterialApp.onUnknownRoute for handling bad routes.
      
       * Added a feature to flutter_driver that allows the host test script
         and the device test app to communicate.
      
       * Added a test to make sure `flutter drive --route` works.
         (Hopefully that will also prove `flutter run --route` works, though
         this isn't testing the `flutter` tool's side of that. My main
         concern is over whether the engine side works.)
      
       * Fixed `flutter drive` to output the right target file name.
      
       * Changed how the stocks app represents its data, so that we can
         show a page for a stock before we know if it exists.
      
       * Made it possible to show a stock page that doesn't exist. It shows
         a progress indicator if we're loading the data, or else shows a
         message saying it doesn't exist.
      
       * Changed the pathing structure of routes in stocks to work more
         sanely.
      
       * Made search in the stocks app actually work (before it only worked
         if we happened to accidentally trigger a rebuild). Added a test.
      
       * Replaced some custom code in the stocks app with a BackButton.
      
       * Added a "color" feature to BackButton to support the stocks use case.
      
       * Spaced out the ErrorWidget text a bit more.
      
       * Added `RouteSettings.copyWith`, which I ended up not using.
      
       * Improved the error messages around routing.
      
      While I was in some files I made a few formatting fixes, fixed some
      code health issues, and also removed `flaky: true` from some devicelab
      tests that have been stable for a while. Also added some documentation
      here and there.
      9adb4a78
  6. 20 Jun, 2017 1 commit
  7. 15 Jun, 2017 1 commit
  8. 13 Jun, 2017 2 commits
  9. 05 May, 2017 1 commit
  10. 04 May, 2017 1 commit
  11. 03 May, 2017 2 commits
  12. 04 Apr, 2017 1 commit
  13. 31 Mar, 2017 1 commit
  14. 28 Mar, 2017 1 commit
    • Phil Quitslund's avatar
      Bump to Dart SDK 1.23.0-dev.10 (#9051) · ab6df3af
      Phil Quitslund authored
      * Bump to Dart SDK 1.23.0-dev.10
      
      * allows us to understand flutter usage via telemetry
      * brings in `@immutable`
      
      Fixes: #9042
      
      * completer fix
      
      * Update to platform 1.1.1.
      ab6df3af
  15. 15 Mar, 2017 1 commit
  16. 04 Mar, 2017 1 commit
  17. 16 Feb, 2017 1 commit
  18. 14 Feb, 2017 1 commit
  19. 06 Feb, 2017 1 commit
    • Jacob Richman's avatar
      Small Flutter strong mode cleanup fixes. (#7825) · 53fc96da
      Jacob Richman authored
      * Small Flutter strong mode cleanup fixes.
      
      These are cases where strong mode down cast composite errors
      generally indicated cases that would performance or correctness
      issues if Flutter code was run in a strong mode VM.
      
      * Fix Command API so that it is always in terms of Map<String,String>.
      
      * Fix typedef
      53fc96da
  20. 28 Jan, 2017 1 commit
  21. 24 Jan, 2017 1 commit
  22. 23 Jan, 2017 2 commits
  23. 21 Jan, 2017 1 commit
  24. 20 Jan, 2017 1 commit
  25. 19 Jan, 2017 2 commits
    • Ian Hickson's avatar
      Remove randomness from port assignment during coverage collection. (#7548) · 3f1d6d3b
      Ian Hickson authored
      Also, defer to test package for throttling (this will require a test
      package update as well).
      
      Also, add a lot more instrumentation to --verbose mode for tests, and
      fix minor trivial things here and there, and add error handling in
      more places.
      
      Also, refactor how coverage works to be simpler and not use statics.
      3f1d6d3b
    • Todd Volkert's avatar
      Fix sky_shell test flakiness caused by CPU throttling (#7543) · 4e8628c1
      Todd Volkert authored
      When a machine is heavily loaded, it can severely delay the time it
      takes for the OS to start a process once it's asked to do so. Our
      5 second timeout that we were giving the test process to connect
      to the test harness seemed like plenty of time, were it not for the
      fact that the test process itself was not being started in time when
      CPU throttling was in effect.
      
      This change updates the test timeout to begin counting only once the
      test process has been started. We keep the original timeout in play
      in the event that the test process *never* starts up for some reason,
      but we up that timeout value to 5 minutes.
      4e8628c1
  26. 12 Jan, 2017 1 commit
    • Todd Volkert's avatar
      Fix race condition in coverage collection (#7455) · 4f9e5c8d
      Todd Volkert authored
      Previously, it was possible for the test harness to bail
      and the test runner to complete before the platform plugin
      triggered the collection of coverage data. This fixes the
      race condition such that the pending coverage collection
      task is recorded immediately after starting the process.
      4f9e5c8d
  27. 10 Jan, 2017 2 commits
  28. 09 Jan, 2017 1 commit
  29. 07 Jan, 2017 1 commit
    • Todd Volkert's avatar
      Update flutter_tools to use package:file throughout (#7385) · 8bb27034
      Todd Volkert authored
      This removes direct file access from within flutter_tools
      in favor of using `package:file` via a `FileSystem` that's
      accessed via the `ApplicationContext`.
      
      This lays the groundwork for us to be able to easily swap
      out the underlying file system when running Flutter tools,
      which will be used to provide a record/replay file system,
      analogous to what we have for process invocations.
      8bb27034
  30. 15 Dec, 2016 2 commits
  31. 13 Dec, 2016 1 commit
  32. 05 Dec, 2016 1 commit
  33. 30 Nov, 2016 1 commit
  34. 18 Nov, 2016 1 commit