1. 12 Mar, 2018 1 commit
  2. 16 Feb, 2018 1 commit
  3. 02 Feb, 2018 1 commit
  4. 01 Feb, 2018 1 commit
  5. 29 Jan, 2018 1 commit
    • Todd Volkert's avatar
      Extensibility improvements to flutter_tools (#14299) · 1859e82a
      Todd Volkert authored
      * Make the current command injected into the AppContext, allowing
        other classes to inject the current command.
      * Introduce `AssetBundleFactory`, an injected factory class for
        spawning instances of `AssetBundle`. This allows other run contexts
        to use custom asset bundling logic.
      * Clean up RunCommand by removing a 'packages' argument that duplicated
        a global argument by the same name (and for the same purpose).
        Duplicate arguments are confusing and error-prone.
      1859e82a
  6. 24 Jan, 2018 1 commit
  7. 26 Sep, 2017 1 commit
  8. 22 Jun, 2017 1 commit
  9. 10 Mar, 2017 1 commit
  10. 04 Mar, 2017 1 commit
  11. 20 Feb, 2017 1 commit
  12. 14 Feb, 2017 1 commit
  13. 22 Jan, 2017 1 commit
    • Dan Rubel's avatar
      Refactor DevFS for kernel code (#7529) · 0295def2
      Dan Rubel authored
      Refactor DevFS so that it's easier to add new types of content such as kernel code
      * add tests for DevFS package scanning
      * add tests for DevFS over VMService protocol
      * which covers _DevFSHttpWriter and ServiceProtocolDevFSOperations
      * replace AssetBundleEntry and DevFSEntry with DevFSContent
      * refactor to cleanup common code and replace some fields with locals
      * rework .package file generation refactor away DevFSOperations.writeSource
      * only update .package file if it has changed
      * only write/delete/evict assets that have been changed/removed
      0295def2
  14. 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
  15. 13 Dec, 2016 1 commit
  16. 15 Nov, 2016 2 commits