Replies: 4 comments
-
What do you mean by no-ui components? |
Beta Was this translation helpful? Give feedback.
0 replies
-
@Akryum Thanks for your reply, below is an example
|
Beta Was this translation helpful? Give feedback.
0 replies
-
@lcjnil you should handle login, logout, user data in Vuex |
Beta Was this translation helpful? Give feedback.
0 replies
-
@Samuell1 We prefer to use small models, not global store. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I am caught in some trouble when migrating from v3.0.0-beta.19 to 3.0.0-beta.25.
I had some no-ui vue component (eg, some model component to fetch data using graphql and used by ui component). In old version, I just wrap them with
willPrefetch
, and they will be prefetched with no errors or warnings.In latest version, I found that I should collect them manually (since they are not rendered) and pass to
ApolloSSR.prefetchAll
. However this will output first error in https://github.com/Akryum/vue-apollo/blob/v3.0.0-beta.25/ssr/index.js#L59 because they has no ui.Besides, my other ui component depends on these no-ui component, and will initialize the in
beforeCreate
hook, but in latest vue-apollo,walkTree
walked these component will find that these no-ui component is not initialized(beforeCreate hook is not executed), these will cause another error.Luckily, SSR is just fine even with these two errors, but it's bad to display these errors. My question is, what is the best practice to handle these no-ui component, and why latest version should had
walkTree
(since v19 don't need that).Beta Was this translation helpful? Give feedback.
All reactions