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.
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
fix(@cypress/react): Devtools unpredictable resets #15612
fix(@cypress/react): Devtools unpredictable resets #15612
Changes from 1 commit
29b8f8f
46d53a2
6de75b9
f38d40d
e220db0
90512bf
02f26e3
643d83f
7cd14ef
b5be9d7
343e404
0e750df
d9e6ad4
8c5befe
9c611c0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Sorry, @elevatebart I appreciate your help, but I still don't understand why this should be a part of webpack-dev-server. It looks like not the job of the dev server at all.
I understand that turning this on requires additional import and we can make a specific entry point for this. Ideally, it should be something like:
If somebody is going to not use our framework – let him clean up his code on his own. It just looks like trying to solve a problem that does not exist.
For reference: the testing library provides auto cleanup just like we do, but if you do can also use it manually I think for tests like this
https://testing-library.com/docs/svelte-testing-library/api/#cleanup