Skip to content

Add an option to auto-launch DevTools when starting a debug session #1557

Closed

Description

@DanTup

Probably we should allow the user to specify which types to do this for (Dart, webdev daemon, Flutter).

@jacob314 I think this requires the ability to launch the DevTools from the DevTools server (so it can track the process it spawned). Do you know if there are issues open to track that?

Activity

  1. added this to the v2.26.0 milestone on Mar 25, 2019
  2. added
    is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.
    in commandsRelates to commands (usually invoked from the command Palette)
    on Mar 25, 2019
  3. jacob314 commented on Mar 25, 2019

    @jacob314

    Added a devtools issue to track the server piece of this.
    flutter/devtools#463

    I would only suggest launching automatically for flutter_web and flutter.

  4. changed the title [-]Add an option to auto-launch DevTools when starting a debug session[/-] [+]VS Code: Add an option to auto-launch DevTools when starting a debug session[/+] on Mar 25, 2019
  5. changed the title [-]VS Code: Add an option to auto-launch DevTools when starting a debug session[/-] [+]P1.5: VS Code: Add an option to auto-launch DevTools when starting a debug session[/+] on Apr 1, 2019
  6. modified the milestones: v2.26.0, v2.26.1 on Apr 25, 2019
  7. DanTup commented on Apr 29, 2019

    @DanTup
    MemberAuthor

    I don't think this works very well right now, as every time you stop/start a session, you get a new browser tab. Maybe we should try a querystring param in DevTools to have it close its tab when the VM connection drops (assuming we can), and then we could pass that in the case where the tools are being auto-launched at the start of each session?

    @csells @jacob314 WDYT?

  8. DanTup commented on Apr 30, 2019

    @DanTup
    MemberAuthor

    @jacob314 I've opened flutter/devtools#612

    I wonder if we should also have an option for when we call launchDevTools to say "if it's already open, just bring the browser+tab to the front"? (I don't think it'll work for the ChromeOS native-browser case, but maybe for those we own the processes for?).

    FWIW, unless anyone shouts, I'm going to move this to a future release. I think it's non-critical and I want to stop making changes for vNext ASAP (ideally today).

  9. removed this from the v2.26.1 milestone on Apr 30, 2019
  10. 5 remaining items

  11. modified the milestones: On Deck, v3.5.0 on Sep 9, 2019
  12. added a commit that references this issue on Sep 9, 2019
    4c917c3
  13. modified the milestones: v3.5.0, On Deck on Sep 17, 2019
  14. modified the milestones: On Deck, v3.6.0 on Oct 2, 2019
  15. added a commit that references this issue on Oct 7, 2019
    2997d7a
  16. added 5 commits that reference this issue on Oct 16, 2019
    3d8ce0c
    6c2bd2b
    52b381a
    d3aa0f7
    fab99d1
  17. added a commit that references this issue on Oct 23, 2019
    a2d6ec5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

in commandsRelates to commands (usually invoked from the command Palette)is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions