fix playwright test failures on admin dashboard#1665
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 📝 WalkthroughWalkthroughThe changes update the debouncing logic in the DebouncedInput component by replacing Changes
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Don't use DebouncedInput in FilterBar as it's causing Playwright test failures where links briefly aren't clickable. Doing the debouncing directly in FilterBar eliminates the issue.
|
Might be superseded by #1666: this PR still had some test failures, but if we just get rid of the DebouncedInput component entirely and just use PlainInput, where we're not binding to both the undebounced and debounced value at the same time, that eliminates all test failures. So instead of modifying DebouncedInput, #1666 just gets rid of it. EDIT: It all goes away in the squash anyway. Closing #1666 in favor of this one instead. |
No longer used anywhere
|
@hahn-kev - Although you started this PR, the code that will actually be merged is all mine. So really, you should review it, but GitHub won't let me request your review. Want to give it an unofficial (from GitHub's perspective) review which I will then rubber-stamp? |
|
I'm trying a few things out myself before I surrender to the fact that we're incapable of making a stable DebouncedInput component 😭... |
myieye
left a comment
There was a problem hiding this comment.
Well, I tried a few things and none of them worked.
So, it's probably a good idea to go with this for the time being.
Good job making it not break anymore Robin.
there were cycles between
valueanddebouncer.currentwhich triggered issues in tests