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
For each semantic colors, the option resolveVariables allows me to display a colored square with the corresponding color. It works well, but only if the resolved variable is public, probably because I configure sassdoc to hide private content.
If I set access of base colors to public, the square will be shown as expected... but the base colors will be also in the documentation. Since we want to use only semantic ones, it makes no sense to display base colors.
Is it possible to resolve a private variable with resolveVariables option?
Maybe we can take the problem upside down and think about a new annotation overloading the @access one, like this:
///@typeColor///@accesspublic // Public so that 'resolveVariables' can work/// @hidden // Hidden in documentation despite it's public$article_links: $color_blue_ocean;
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hi everyone,
Here is my use case: I have some base colors and "semantic" colors. Base colors are all the colors my application will use:
Semantic colors are colors with some meanings. They are basically aliases to base colors:
For each semantic colors, the option
resolveVariables
allows me to display a colored square with the corresponding color. It works well, but only if the resolved variable is public, probably because I configure sassdoc to hide private content.If I set access of base colors to
public
, the square will be shown as expected... but the base colors will be also in the documentation. Since we want to use only semantic ones, it makes no sense to display base colors.Is it possible to resolve a private variable with
resolveVariables
option?Maybe we can take the problem upside down and think about a new annotation overloading the
@access
one, like this:Thanks in advance!
The text was updated successfully, but these errors were encountered: