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
I'd be interested in having the ability to see and copy the color information as a JSON-compatible snippet in addition to the existing JavaScript snippet.
My use case is for tooling around colors that involve reading and consuming something like colors.json in some parts of the application but could also be used to inject as parsed JSON into tailwind.config.js.
Right now I'm doing this in my tailwind.config.js:
Which is fine, but it would be nicer if I could maintain colors.json instead of colors.js and not have an extra build step required to get colors.json to exist.
I would argue that converting JS to valid JSON is kinda trivial :D But it could definitely be included. Maybe in a dropdown option under the copy button, just like "save as new" is currently for shades? If you have something better in mind, let me know
I think I'll leave this one for now. :) I don't have enough time to figure out how to do this and I already have a workaround. Thanks for merging #44. That is the main thing that will make my life easier. :)
I'd be interested in having the ability to see and copy the color information as a JSON-compatible snippet in addition to the existing JavaScript snippet.
My use case is for tooling around colors that involve reading and consuming something like
colors.json
in some parts of the application but could also be used to inject as parsed JSON intotailwind.config.js
.Right now I'm doing this in my
tailwind.config.js
:Which is fine, but it would be nicer if I could maintain
colors.json
instead ofcolors.js
and not have an extra build step required to getcolors.json
to exist.Is this something you'd consider adding or supporting if I sent a PR?
The text was updated successfully, but these errors were encountered: