-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vue__WEBPACK_IMPORTED_MODULE_0__.getCurrentInstance() is null since 8.20 #6360
Comments
Flow settings interface is not usable otherwise, specifically the mode selector. An issue is filed upstream at nextcloud-libraries/nextcloud-vue#6360 Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
In general case, it isn't valid to mix several Vue frameworks inside a single render (render a Vue-component using one copy of Vue framework as a part of Vue-component rendered by another copy of Vue framework.). ExplanationVue is stateful, and its rendering implementation uses Vue internal state.
In you case, we have Vue.js framework twice in the document. It would be fine it they are used in different, separated apps, rendering different nodes. But in the Workflow app, During the rendering:
In the past it worked by chance, because:
Thus, this is neither |
A proper way to render two independent Vue apps inside each others are:
It would also allow to not bind to a specific Vue version, e.g., develop workflow plugins in Vue 3, or update server to Vue 3 without breaking Vue 2 plugins, or develop plugins without Vue at all |
Thanks for the explanation @ShGKme |
I am trying to build workflow_pdf_converter, which has very puny vue code base:
The builds succeeds, but the the NcSelect component is unusable in Personal Settings → Flow. It does not have the default value assigned, and changing the value is not taken over either.
This is what I see in the browser console. The `setup()` function that is mentioned belongs to the NcSelect component.
The error starts to appear with 8.20. When building with up to 8.19, everything is fine and the UI is usable and functional.
Please advice, cc @kyteinsky @ShGKme @julien-nc @hamza221
The text was updated successfully, but these errors were encountered: