You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User object is empty.
The component works fine without params.
The query return the expected results without the component.
The issue is how the component use the store getters. According to the documentation fetchParams is only used for the API for the API server, and the component should only use the resource id on the store getters. But currently, params and fetchParams are used in the same way:
Steps to reproduce
Expected behavior
User object with nested profile object
Actual behavior
User object is empty.
The component works fine without params.
The query return the expected results without the component.
The issue is how the component use the store getters. According to the documentation
fetchParams
is only used for the API for the API server, and the component should only use the resource id on the store getters. But currently,params
andfetchParams
are used in the same way:feathers-vuex/src/FeathersVuexGet.ts
Lines 119 to 121 in 4ae03ba
Because the params are passed to the store getters, the store returns null.
feathers-vuex/src/FeathersVuexGet.ts
Lines 95 to 105 in 4ae03ba
getArgs
return[0: 42, 1: { query : { $eager: '[profile]' }}]
and the query is passed as args to the store getters.Replacing
by
produce the expected results confirming the issue.
System configuration
Latest version of the package.
The text was updated successfully, but these errors were encountered: