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

core(tsc): add type defs for Chrome Remote Debugging Protocol #4816

Merged
merged 2 commits into from
Mar 20, 2018

Conversation

brendankenny
Copy link
Member

@brendankenny brendankenny commented Mar 19, 2018

vscode-chrome-debug-core has up-to-date type defs for the protocol. Pull those in until ChromeDevTools/devtools-protocol#55 is fixed

This exposes the types on LH.Crdp.* (e.g. LH.Crdp.Network.Response). Happy to bikeshed.

Once again github is tricked by indentation. Check out ?w=1 for a better diff

devtoolsLog: Array<void>;
trace: {trraceEvents: Array<LH.TraceEvent>}
export interface LoadData {
networkRecords: Array<Crdp.Network.Response>;
Copy link
Collaborator

Choose a reason for hiding this comment

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

this seems like the response from the protocol which is quite different from the JS class we use from WebInspector

https://github.com/Microsoft/vscode-chrome-debug-core/blob/ab5a12544ccd32db4648e2bd6146ce396c047dab/crdp/crdp.d.ts#L6688

Copy link
Member Author

Choose a reason for hiding this comment

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

yeah, that was just a check that it's working. First person to use it can expand to the actual type :)

@brendankenny brendankenny merged commit adf4f86 into master Mar 20, 2018
@brendankenny brendankenny deleted the crdp branch March 20, 2018 01:07
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.

4 participants