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
We currently have multiple getters and even some state in the session.js Vuex module that is accessed throughout Kolibri.
We have started migrating these references to instead use the useUser core composable, but the composable still does not expose all the needed getters and state that are referenced across Kolibri.
To remedy this, all the getters that are defined in the session.js module should be exposed through the useUser composable in a similar way to those that have already been wrapped.
In addition, all state in the session module should be exposed for consumption via the composable as well.
The text was updated successfully, but these errors were encountered:
I have reviewed, @dhruvpal05 - thanks for your efforts, but you seem to have misunderstood the issue. Please feel free to ask further clarifying questions on my review.
We currently have multiple getters and even some state in the session.js Vuex module that is accessed throughout Kolibri.
We have started migrating these references to instead use the useUser core composable, but the composable still does not expose all the needed getters and state that are referenced across Kolibri.
To remedy this, all the getters that are defined in the session.js module should be exposed through the useUser composable in a similar way to those that have already been wrapped.
In addition, all state in the session module should be exposed for consumption via the composable as well.
The text was updated successfully, but these errors were encountered: