Jems

I've been on vacation in the mean time. I'll try to look into it in the next days but we need to agree on the way we handle this, as...

To me, it seems that we just need to handle the -1 value specifically in the find getter. Currently, it is just passed as the last parameter of the slice...

The filter-query behavior doesn't prevent us to do what I suggested. The filter-query method is called [there in the getter](https://github.com/feathersjs-ecosystem/feathers-vuex/blob/4ae03bae9b31802e5355871826626ca80236a3ce/src/service-module/service-module.getters.ts#L54), so we can still check the value of the $limit...

Hi, not yet @corepay Any idea when you can take a look @marshallswain ?

I agree that it would be a nice addition, but maybe more as a ref return from the usefind. Now, you can still query the count manually in the store...

You can safely ignore the warnings, [for context](https://github.com/feathersjs-ecosystem/feathers-vuex/issues/504#issuecomment-686640250) and [suppress it if you wish](https://github.com/feathersjs-ecosystem/feathers-vuex/issues/504#issuecomment-687072996).

I think this is the same problem as described in this [issue](https://github.com/feathersjs-ecosystem/feathers-vuex/issues/599). You must use the replaceItems option with the next release.

A possible solution would be to use the Vue set method on each properties each time an item is updated but I'm not sure if it would be good in...

Please, take a look at my comment [there](https://github.com/feathersjs-ecosystem/feathers-vuex/issues/590#issuecomment-872939295)

Ok I get it. There is one small problem however. This MR will conflict [with a previous one](https://github.com/feathersjs-ecosystem/feathers-vuex/pull/588) And I think [the added code](https://github.com/feathersjs-ecosystem/feathers-vuex/pull/607/files#diff-31460bc3932b76faa5853e7340071c1e6a04d435cf964ec16702803cf0a26e09R53-R77) could be isolated in a separate...