Skip to content

[WIP] Expose minimal API for flutter_tools consumption #440

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

Closed

Conversation

jonahwilliams
Copy link
Contributor

This allows flutter tools to inject its own serving logic for certain assets.

@jonahwilliams
Copy link
Contributor Author

Re-using this to discuss some ideas with the API structure

export 'src/serve/debugger/app_debug_services.dart' show AppDebugServices;
export 'src/serve/debugger/devtools.dart' show DevTools;

Future<WebDevHandler> connectToWebdev(
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the first stab at a basic API - I tried to expose as little as possible - really only the configuration needed to initialize the server and the interfaces we use to get the vm service or debug. See https://github.com/flutter/flutter/pull/34252/files#diff-01a7653ade6cc1a5182fdebf929ad64bR291 for example usage

@jonahwilliams jonahwilliams changed the title [WIP] Expose a handler for flutter_tools in the configuration [WIP] Expose minimal API for flutter_tools consumption Jun 14, 2019
@grouma grouma closed this Jul 11, 2019
@jonahwilliams jonahwilliams deleted the flutter_tools_updates branch July 11, 2019 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants