-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Removal of erraneous functionality in CT #24328
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
Comments
Hey team! Please add your planning poker estimate with Zenhub @amehta265 @astone123 @lmiller1990 @marktnoonan @mike-plummer @rockindahizzy @warrensplayer @ZachJW34 |
I feel like this has been answered but wanted an explicit answer to this: For functionality that is being removed, do we deprecate, deprecate + throw error when used or deprecate + noop/log when used? |
@ZachJW34, my vote is to deprecate + throw. @marktnoonan, could you give us the preferred method? |
It looks like we didn't share the final conclusion to the question in the post above by @rockindahizzy. We will deprecate |
The code for this is done in cypress-io/cypress#24419, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Uh oh!
There was an error while loading. Please reload this page.
We want to remove functionality that was deemed as erraneous with regards to critical functionality in Component Testing. Use the
no-dead-code
paradigm when practical to ensure users don't experience unnecessary blockers.Things that need to be removed
Global
mount-utils
).React
mountHook
functionunmount
function should no longer be exportedVue
The text was updated successfully, but these errors were encountered: