fix: (driver) add null check for browserRequestId
on responses for cy.wait
#28713
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.
Additional details
In #27806, we added sorting to the list of responses that we get in the wait command. The sorting algorithm uses the
browserRequestId
attribute to sort responses with the same aliases and return them in the order in which they were received by the browser.Sometimes this attribute isn't defined on the responses which causes us to throw an error when we call
.split
on undefined. This PR updates the sorting logic to just return the responses with the original sort order if either of the requests that we're comparing don't have abrowserRequestId
.Steps to test
I wasn't able to actually reproduce this - but adding the null check should at least make it so that we don't throw if the response doesn't have the expected properties.
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?