-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
[2.0.3] Modified values #3193
Comments
Gotcha Either way, this is something we're going to try to tackle as part of 2.1—definitely not a small project that we can squeeze in to 2.0.3 (due out tomorrow). |
This was referenced Nov 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
previous message:
A suggestion with easy integration: add a section in the final .js and .css docs, or even in a separate file containing info about which values have changed through the customization tool. This way, it will be easier for future library updates, as the developer will know which values to change in the customization tool for the new version.
Perhaps I should have mentioned that I'm talking about which variables the user changed, not the variables that changed in the library. For example, now when you want to update to 2.0.3 you will have to view the source of the current css file (that is using custom user variables) to see which default colors you changed, so you can set the custom values to the new library version.
Thanks!
The text was updated successfully, but these errors were encountered: