1. 21 Jan, 2022 1 commit
  2. 15 Dec, 2021 1 commit
  3. 02 Apr, 2021 1 commit
  4. 27 Jan, 2021 1 commit
  5. 23 Jan, 2021 1 commit
  6. 21 Jan, 2021 1 commit
  7. 16 Sep, 2020 2 commits
  8. 08 Sep, 2020 1 commit
    • Jonah Williams's avatar
      [flutter_tools] standardize patterns for integration.shard (#64980) · 6b444c4d
      Jonah Williams authored
      Integration tests must only go through the real file system/process manager/platform. The global indirection makes this code harder to understand than if it directly referred to the concrete instances that are being used.
      
      Update the integration shard to use a const instance of a LocalFIleSystem, LocalProcessManager, and LocalPlatform. Remove global usage and apply testWithoutContext.
      6b444c4d
  9. 31 Aug, 2020 2 commits
  10. 29 Aug, 2020 1 commit
  11. 28 Aug, 2020 2 commits
  12. 27 Aug, 2020 1 commit
    • Ben Konyi's avatar
      Re-enable the Dart Development Service (DDS) (#64671) · d7d12412
      Ben Konyi authored
      This change re-enables DDS and outputs the DDS URI in place of the VM
      service URI on the console. If --disable-dds is not provided,
      --host-vmservice-port will be used to determine the port for DDS rather
      than the host port for the VM service, which will instead be randomly
      chosen.
      d7d12412
  13. 29 Jul, 2020 2 commits
  14. 21 Jul, 2020 2 commits
  15. 20 Jul, 2020 2 commits
  16. 16 Jul, 2020 2 commits
  17. 14 Jul, 2020 3 commits
  18. 10 Jul, 2020 2 commits
  19. 24 Jun, 2020 1 commit
    • Jonah Williams's avatar
      [flutter_tools] de-flake integration tests (#60221) · f8c9e1bb
      Jonah Williams authored
      The vm_service_integration test flake is caused by trying to call the method before the framework is initialized (and the extension added). The run errors failure is caused by the error taking some time to propagate to the harness
      f8c9e1bb
  20. 18 Jun, 2020 1 commit
    • Jonah Williams's avatar
      [flutter_tools] add toggle `b` and service extension to change platform brightness (#59571) · e1f4cfb4
      Jonah Williams authored
      A frequent request from the last Flutter developer survey was for an easier method of testing light/dark mode changes. Currently, a user needs to manually change the theme settings or adjust phone settings to see the difference. Instead we should add a toggle from the CLI, and eventually devtools/Intellij/Vscode that allows developers to override the current setting.
      
      Fixes #59495
      
      Adds flutter.ext.brightnessOverride service protocol which either queries the current platform brightness, or overrides it to a new value. This accepts either Brightness.light or Brightness.dark as a value.
      
      Adds a CLI toggle b which allows the setting to be toggled manually.
      
      Requires an update to the MediaQuery, to conditionally use a debug override when not in release mode
      e1f4cfb4
  21. 27 May, 2020 1 commit
  22. 14 May, 2020 1 commit
  23. 04 May, 2020 1 commit
  24. 14 Apr, 2020 1 commit