fix: add safety check for command.clone when cmd does not have args #20998
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.
While pulling in the logGroup changes into within in the 10.x branch, I noticed two consistent command failures with the following error:
The test flow could be summarized like:
When a command is replayed, it's cloned and injected into the command queue.
When the command is cloned, it pull sanitize the commands args list to pull forward an create a new command. Generally commands have args, but because the injected end-logGroup command did not have args passed, it was undefined and caused this error.
This check just ensures commands lacking args can successfully be cloned.
User facing changelog
n/a
PR Tasks
cypress-documentation
?type definitions
?cypress.schema.json
?