-
Notifications
You must be signed in to change notification settings - Fork 447
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
Make easier to create custom Vue component in plugin #9089
Comments
PR is now ready for review. |
No objections here, @jardakotesovec; can you open a PR against one of the applications with the specially-formulated submodule update commit message, so that the Travis tests integration can run over this change? |
…brary-components##
…brary-components##
@asmecher Here is the OJS PR - pkp/ojs#3977 |
Thanks, @jardakotesovec, the Travis test didn't quite complete one run but it's nothing you broke. Are you ready for #9125 to be merged and cherry-picked forward to |
…components #9089 expose UI library components
@asmecher merged&cherry picked in pkp-lib. Should I always also update the the submodules across ojs/omp/ops? |
Please leave the submodules for now; normally it's good practice to update submodule hashes but
|
...and thanks for implementing this! I'll close the issue, unless there's something left to do here. |
Its already possible to create custom vue component and than add it via smarty hooks to existing UI.
But are few small improvements to make that experience easier
Currently if plugin create custom Vue.component, its limited to the use of global components from ui-library.
The text was updated successfully, but these errors were encountered: