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

Refresh Queries is wrongly marked as suspend #78

Closed
futursolo opened this issue Jul 23, 2023 · 0 comments · Fixed by #81
Closed

Refresh Queries is wrongly marked as suspend #78

futursolo opened this issue Jul 23, 2023 · 0 comments · Fixed by #81
Labels
A-query Area: Bounce Query API C-bug Something isn't working

Comments

@futursolo
Copy link
Member

futursolo commented Jul 23, 2023 •
edited
Loading

Discovered by Rek Malorm on Discord.

Refresh Queries should not suspend the component and instead keeping the last fresh value until a new value is available.
However, sometimes it is possible for the use_query to suspend the component on a refresh query.
This can lead to unintentional fallback screen after data is loaded and is not desirable.
@futursolo futursolo added C-bug Something isn't working A-helmet Area: Helmet API labels Jul 23, 2023
@futursolo futursolo mentioned this issue Jul 31, 2023
Merged
4 tasks
@futursolo futursolo added A-query Area: Bounce Query API and removed A-helmet Area: Helmet API labels Jul 31, 2023
@jsievenpiper jsievenpiper mentioned this issue Apr 14, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-query Area: Bounce Query API C-bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Do not suspend refresh queries futursolo/bounce
1 participant
@futursolo