-
Notifications
You must be signed in to change notification settings - Fork 765
Runtime configuration change? #3290
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
Comments
No, I was thinking about replacing multiple component defaults at once via the "ui object" documented here: There's a reference to |
When using updateAppConfig({ ui: { ... } }), the updates are not applied to the NuxtUI components. Only the ui: { ... } options defined in defineAppConfig() are applied as intended. |
I like this thread and I have a similar use case. With one difference: I'd like, rather than the user 'select' a theme, to switch themes based on hostname of the http request. Imagine each of the following urls is served from the same nuxt app, but they look different based on domain name: |
Description
Sorry if this information is available, but I could not find an answer in the docs or by searching.
I was hoping to be able to let users select a theme that also included changing component defaults.
Using Vue/Vite (not Nuxt), is it possible to modify the full global configuration (
ui
object) at runtime (instead of having to pass props to or wrap each component)?I'm not 100% averse to a bit of monkey patching on my current project, but a supported solution would obviously be much much better.
If this is not currently possible, please consider this a suggestion, for example via an
ui
prop on theApp
component or auseNuxtUi
composable.The text was updated successfully, but these errors were encountered: