-
Notifications
You must be signed in to change notification settings - Fork 22
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
find() with paginateOn: 'server' has query ignored if no results returned #126
Comments
Thanks @MajesticPotatoe and @1sses. This looks like a legitimate bug. It will be a while before I can do anything to fix it, so this issue will remain open until I or someone else can come up with a solution. |
no worries, pretty much my work around for the time being is to just clear store before query (not ideal but luckily it doesn't effect much for my use case) |
I'm going to update that conditional to see if it fixes our problem. It's a quick and dirty fix, since I didn't specifically update tests for it. I've just fixed the conditional in |
I'm reverting the change. Integrating into a published app fails. I'll work on this another time. |
When using useFind() with { paginateOn: 'server' } and a query is performed via find() (destructured or service().find()) that returns empty results, data doesn't update. When this occurs, the find() query is ignored and will revert to displaying whatever the previous query results (essentially ignoring the query all together). This can be observed via pinia devtools. (queriedAt for the most recent pagination doesn't even update).
This also can be seen indirectly with { paginateOn: 'hybrid' } as well.
The text was updated successfully, but these errors were encountered: