Setting paginate to false does not work with find getter
See original GitHub issueSteps to reproduce
Use service getters to find a value and set params.paginate to false:
const res = store.getters['myService/find']({ paginate: false })
Expected behavior
res
should be an Array
console.log(res) // [ ... ]
Actual behavior
res
will always be a pagination object:
console.log(res) // { total: n, limit: n, skip: n, data: [ ... ] }
Module versions (especially the part that’s not working):
feathers-vuex 1.1.4
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Setting paginate to false does not work with find getter #108
Setting params.paginate to false has a new function in Feathers-vuex@2.x. Server-side pagination is now fully supported on the client with the ...
Read more >Bypass mongoose getter - Stack Overflow
Another option would be to set password to 'select: false' in the schema. var AccountSchema = new Schema({ password: { type: String, ...
Read more >Spring Data JPA Pagination - Dan Vega
In this tutorial, you are going to learn how to work with pagination in Spring Data JPA. If you have a few records...
Read more >Service Module API - FeathersVuex
You can set params.paginate to false to disable pagination for a single request. ... It works the same way as get requests in...
Read more >standardSetController pagination is not working for setter
standardSetController pagination is not working for setter ... both work absolutely fine when I use getter method to get the values of lists ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@HarisHashim Thanks for pointing out that line. It was definitely inaccurate. Pagination is always controlled from the server. I’m not sure where my brain was when I wrote that line.
@dkrotts Ah, yes. The docs definitely require updating.
The current behavior is the expected behavior, but the docs need to be updated. I’ve just gotten sick of writing guards in my code for when a service has pagination enabled or disabled, or changes between them. So, getters always return the data at
data
. Feathers will do the same thing in a future release.