fix: Prevent null snapshots from being stored and causing errors #16015
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.
User facing changelog
Cannot read property 'name' of null
Additional details
Snapshotting can fail for various reasons. In the issue this closes, it was because the snapshot happens before the page fully loads, but it can also fail if the page is cross-origin. We catch such failures when creating the snapshot and return
null
, but the log adds thatnull
value to the list of snapshots. When the user hovers over the command and we try to display the snapshot, it's expected to be a proper snapshot object and throws when we try to access properties on it. The solution is simply to not addnull
snapshots to the list of the log's snapshots. Then it's properly recognized as "missing" (which is correct, since we can't get a snapshot of it) and we display that to the user without erroring.How has the user experience changed?
Hovering over commands with a missing snapshot no longer errors.
PR Tasks
cypress-documentation
?type definitions
?cypress.schema.json
?