You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is
I hope to modify the primary in color through certain configurations, so that all places based on primary can automatically become the color I set. For example, after I change primary to red, buttons everywhere change to red.
I hope to make global modifications, rather than changing in every place where it is used.
This would be indeed very helpful to be able to override the primary color once and have an easy way to customize the default color palette. But it looks like the blue is hardcoded in a few places (for the buttons at least)
I'm also completely lost on how to redefine the Svelte color scheme. I've looked over and over at the Svelte UI documentation and stitches.js documentation. I've tried using globalCss().
I'm not sure this is a bug, or just a documentation issue. If it's just a documentation issue, it would be great to have some documentation with a specific example of how to change the primary color globally.
Hey, right now we don't have a workaround besides setting the color prop in each component. We are moving away from our current styling solution, so this will definitely be changed in the future.
What package has an issue
@svelteuidev/core
A clear and concise description of what the bug is
I hope to modify the primary in color through certain configurations, so that all places based on primary can automatically become the color I set. For example, after I change primary to red, buttons everywhere change to red.
I hope to make global modifications, rather than changing in every place where it is used.
I have tried Custom theme but it didn't work.
In which browser(s) did the problem occur?
Chrome, Other - list in description
Steps To Reproduce
+layout.svelte
Do you know how to fix the issue
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix
Yes
Relevant Assets
No response
The text was updated successfully, but these errors were encountered: