-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[test] Fix warnings in the demos #25140
Conversation
9b31cef
to
a646047
Compare
a646047
to
02b095c
Compare
02b095c
to
803194a
Compare
803194a
to
26de707
Compare
e9fb8ff
to
fa25748
Compare
@eps1lon There is a tradeoff to make between running the visual regression tests in dev mode and having the dev warnings vs. running them in production mode and having them run faster. In dev mode, it's about 50% slower. I would be leaning toward keeping the production mode enable, but no strong point of view. |
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.
The idea is great but the current implementation will be frustrating to debug with.
9b4ff98
to
94bb357
Compare
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.
Let's follow the approach we have for the unit tests and collect all during a test, throw them in afterEach
and clear them in beforeEach
. That way we don't swallow console calls and make sure tests don't leak if they fail.
Haha, I'm not surprised you asked for this. The docs wasn't covering the API to stop listening to an event. But I might not have searched enough. Ok, I'm on it. |
I noticed this as well. But it should have |
I have pushed it further. I have done my best, taking your feedback into account. If it's not good enough. I would propose I simply fix the warnings, and we can come back to adding safety in the CI later. I'm going over the time budget I can spend on this. I have tried using on/off but it wasn't delivering. It seems to create more complexity than solving any problem. For instance, we need to catch the console log that popup even before we start taking screenshots (during bootstrap). |
63eecc8
to
03a6ccd
Compare
…t screenshots are the bottleneck, not React
03a6ccd
to
21e2d53
Compare
I have reduced the ambition of the changes. It's about fixing existing warnings in the demos. For the tests, it was reverted in 21e2d53. If we are happy with the approach, I can replay the commit (I personally think that it's good enough), otherwise for another time. |
Fix 4 of the 6 errors existing, what's left: