We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
use
This plugin relied on the following pattern:
In a use extension:
const options = Vue.component(type).options; Vue.component(type, { extends: options, // my stuff });
In Kirby 4, however, Vue.component(type) always seems to return undefined.
Vue.component(type)
undefined
Defer the execution to the next javascript tick, at that point the components are accessible.
setTimeout(() => { const options = Vue.component(type).options; Vue.component(type, { extends: options, // my stuff }); }, 0);
The text was updated successfully, but these errors were encountered:
probably duplicate of getkirby/kirby#5183
Sorry, something went wrong.
Yes, would expect this to be solved with getkirby/kirby#5202 as well
fixed in alpha 2
No branches or pull requests
The
use
plugins seem to be run before the Kirby components have been registered.This plugin relied on the following pattern:
In a
use
extension:In Kirby 4, however,
Vue.component(type)
always seems to returnundefined
.Workaround
Defer the execution to the next javascript tick, at that point the components are accessible.
The text was updated successfully, but these errors were encountered: