Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

consider auto-registering vm service protocol registration #35

Open
pq opened this issue Oct 16, 2018 · 0 comments
Open

consider auto-registering vm service protocol registration #35

pq opened this issue Oct 16, 2018 · 0 comments
Labels
api enhancement New feature or request
Milestone

Comments

@pq
Copy link
Owner

pq commented Oct 16, 2018

It would be great to avoid needing to explicitly initialize VM service hooks.

That is, it would be nice to do away w/ the need to call:

logManager.initServiceExtensions();

Thoughts:

  1. we could do this proactively in the manager (con: carry the cost of an extra service extension even if it's not used; pro: would work in profile / release and not require any code changes or client footwork)
  2. clients could do this (e.g., IntelliJ could use EvalOnDartLibrary to call something like initServiceExtensions()) -- con: only works for apps being debugged
@pq pq added enhancement New feature or request api labels Oct 16, 2018
@pq pq added this to the 1.0 milestone Oct 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant