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
What do you think about auto generating some .md files to help with documentation? So that instead of saying the following in the README.md:
Most of the names follow the same naming convention as open props CSS variables, except the -- is replaced with $. You can find the values of all props by inspecting the scss files on npm.
You could have:
You can find the values of all the props in the relevant markdown file below:
I'm not convinced about this. It's more work to maintain, for not much benefit. If the scss output is not super readable, then I can run prettier on it before publishing next time. Is there anything else I'm missing?
What do you think about auto generating some
.md
files to help with documentation? So that instead of saying the following in theREADME.md
:Most of the names follow the same naming convention as open props CSS variables, except the -- is replaced with $. You can find the values of all props by inspecting the scss files on npm.
You could have:
You can find the values of all the props in the relevant markdown file below:
This could be done by adding the following to
generateScss.mjs
.It might also help to add prettier for the formatting.
The text was updated successfully, but these errors were encountered: