Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Rewrite these fetcher functions to return errors if they're unsuccessful? Currently we return null in a lot of places, but the loadable / useQuery pattern gives us the ability to better handle and surface errors #1209

Open
arthur-zhuk opened this issue Aug 1, 2022 · 0 comments
Open

Rewrite these fetcher functions to return errors if they're unsuccessful? Currently we return null in a lot of places, but the loadable / useQuery pattern gives us the ability to better handle and surface errors #1209

arthur-zhuk opened this issue Aug 1, 2022 · 0 comments

Comments

@arthur-zhuk
Copy link
Contributor

Should we add a task to rewrite these fetcher functions to return errors if they're unsuccessful? Currently we return null in a lot of places, but the loadable / useQuery pattern gives us the ability to better handle and surface errors

Originally posted by @hammeiam in #1195 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@arthur-zhuk