-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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): NetworkRequest.RESOURCE_TYPES type fix #5851
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so
Array<LH.Crdp.Page.ResourceType>
won't work anymore? Maybe I'm confused but I'm not sure why it's better now :)What are the good cases we expect to catch by having
Network.TYPES.Fetch
be just'Fetch'
instead ofLH.Crdp.Page.ResourceType
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uh, no, that will work and is way better :) fixing now.
The issue was that these are defined with
const
strings, so tsc wasn't widening them at all. e.g.was becoming only type
Array<'Document'|'Script'|'Stylesheet'>
, sotextResourceTypes.includes()
wasn't allowing you to pass it the generalLH.Crdp.Page.ResourceType
type (see microsoft/TypeScript#26255 for more on this annoyance :)But
Array<LH.Crdp.Page.ResourceType>
is a way better fix thanArray<string>
for that.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
basically the inverse of the situation with the arrays. e.g if you had
doSomething(resourceType: 'Fetch'|'XHR')
, passing itNetworkRequest.TYPES.Fetch
will be an error (since it's the full union). Not an issue in our current code, but it could be in the future.(but it sounds like you're ok with this without the regression to
Array<string>
in the original form of the PR?)