-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
breaking: remove the shouldUploadVideoOnPass configuration #27010
breaking: remove the shouldUploadVideoOnPass configuration #27010
Conversation
6583e90
to
0110c49
Compare
@@ -160,7 +160,7 @@ plugin stdout | |||
│ Pending: 1 │ | |||
│ Skipped: 0 │ | |||
│ Screenshots: 1 │ | |||
│ Video: true │ | |||
│ Video: false │ |
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.
snapshot is different because we are now deleting the video entirely, which is slightly different than videoUploadOnPasses
, which keeps the video but skips compression and does NOT upload it to the cloud.
50609b0
to
1d57c26
Compare
0110c49
to
0566edc
Compare
0566edc
to
34fdb04
Compare
@AtofStryker I know that this PR is already merged - however even though this is a breaking change, you can't just remove this config and silently swallow config that has that property present. In fact if you look at other breaking config change patterns - whenever we remove/rename config, we always leave a "check" in there that if the removed property still exists in the config we throw a nice error saying that this was removed as of If you look at other proxies for this pattern you'll find them in the code and in the error messages. Basically what we don't want to have happen is that this property is removed, but you keep the old value around and yet it no longer "works" or applies, and there's nothing prompting you that something is wrong. By throwing an error the user gets a very loud message indicating this was removed. The error message can also naturally guide them to know what to do in response to it being removed. |
@brian-mann apologies for missing that. I created #27158 which should warn the user in the terminal if the |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Additional details
see #26899 for details/rationale
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
? BREAKING: remove the videoUploadOnPasses configuration option cypress-documentation#5306type definitions
?