Skip to content
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

Best way to map to customized vuetify components #115

Closed
kguelzau opened this issue May 31, 2024 · 1 comment
Closed

Best way to map to customized vuetify components #115

kguelzau opened this issue May 31, 2024 · 1 comment

Comments

@kguelzau
Copy link

I am searching for a simple way to map to alternative vuetify components.
Basically we have customized / wrapped components for all vuetify components we need.
I would like use these instead of the orginal vuetify components.

Do you have any advice beside creating own custom renderes?

Sorry for opening an issue for this question, but i did not find another way to get advice.
Feel free to ignore/close it. :-)

@yaffol
Copy link
Contributor

yaffol commented Jun 5, 2024

Off the top of my head, I can't see a means without custom renderers, or making your own build where you import your library instead of the stock Vueitfy. There may be some clever aliasing that's possible with Vite that I don't know about, but that's only a guess, or using dynamic imports in some way.

It's quite easy to fork the project and build it if you do need to do that, though you might want to wait for eclipsesource/jsonforms#2341 to get merged in as this will move the vue-vuetify renderer set (this repo) into a package within the main json-forms monorepo.

In terms of the best place to ask this sort of question, there is also the community forum which has a good response level and may be an easier place to ask specific use cases and share code examples etc.

@kguelzau kguelzau closed this as completed Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants