Typo at FeathersVuexFind
See original GitHub issuehttps://github.com/feathersjs-ecosystem/feathers-vuex/blob/master/src/FeathersVuexFind.ts#L81
It should be check for params
, not for query
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Renderless Data Components | FeathersVuex
The FeathersVuexFind component retrieves data from the API server, puts it in the Vuex store, then transparently retrieves the live, reactive data from...
Read more >feathers-vuex/FeathersVuexFind.ts at master - GitHub
Integration of FeathersJS, Vue, and Nuxt for the artisan developer - feathers-vuex/FeathersVuexFind.ts at master · feathersjs-ecosystem/feathers-vuex.
Read more >Renderless Data Components - FeathersVuex
These components use Vuex getters (to query data from the local store) and actions (to query data from the API server). When a...
Read more >feathers-vuex: Versions - Openbase
This fixes the useFind Vue Composition API utility. The haveLoaded property will now always be set to true when local: true is enabled...
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
@shabanovd is right. Good catch! Before
feathers-vuex@3.12.0
FeathersVuexFind
only worked with:query="..."
. Now it also supports:params="{}"
This is a leftover from #521 .@J3m5 I think the philosophy of
feathers-vuex
is to always provide at least an empty query to prevent accidentally complete requests. From time to time it annoys me but I think over all it’s more helpful.Should be fixed in #529
It appears that it has the same behavior than the makeFindMixin and the useFind hook. It is consistent so it’s not such a big deal. I think that it should be left as is for now and ask what others think about it. The only use case I see is if you want to explicitly not return the items but it can be achieved by passing $limit: 0. Anyway, we’ll see