-
Notifications
You must be signed in to change notification settings - Fork 119
Replace handwritten Chrome Protocol .d.ts with better system #46
Comments
What about https://github.com/cyrus-and/chrome-remote-interface? Has support for auto-detecting the support Used by Google too. |
Callback-based :/. Also, we have an extra need to implement the server-side, for adapters. I think that's part of @nojvek's motivation to build his own. |
We should keep the notion of adapters, etc our of the core, but simply aim to have a runtime agnostic client that works with any CDP compliant endpoint. |
Right, we need something that reads the protocol.json and does the code and typings generation for both sides. This repo would use it for the client side, and another repo would use it for the server side, or both sides. |
I'm a bit unsure of what you mean by client and server side. Using a 3rd party library for the actual CDP connection makes sense, while exposing a vscode debugger abstraction for other debuggers in this library makes sense to me. |
On one end of the connection, a client is sending |
👍. I think the abstraction could be cleaner. I'll submit a PR. On Wednesday, October 5, 2016, Rob Lourens notifications@github.com wrote:
|
Something like https://github.com/DickvdBrink/chrome-debug-protocol - generating a .d.ts from the package.json. Would have to replace the callbacks with Promises. Would be great if the build fails automatically when the protocol changes.
The text was updated successfully, but these errors were encountered: