-
Notifications
You must be signed in to change notification settings - Fork 887
docs: update FE fetching data docs #11376
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
Conversation
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.
Very helpful insight on how using react query changes our patterns, thanks for updating
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.
New recommendations sound good! Just had two small comments
docs/contributing/frontend.md
Outdated
Test components without user interaction like testing if a page/component is | ||
rendered correctly depending on some parameters, if the button is showing a | ||
spinner, if the `loading` props are passing, etc. This should always be your | ||
first option since it is way easier to maintain. For this, we use |
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.
This should always be your first option since it is way easier to maintain.
I disagree with this, tbh. I think we're running into difficulties when we use visual testing as our first line of defense. Maybe something we can chat about more during the FE variety call!
Co-authored-by: Kira Pilot <kira@coder.com>
No description provided.