-
Couldn't load subscription status.
- Fork 7
Description
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:
/// @type Color
/// @access private
$color_blue_ocean: #2882c5;
/// @type Color
/// @access private
$color_red_blood: #992600;
/// @type Color
/// @access private
$color_green_forest: #005500;
// ...Semantic colors are colors with some meanings. They are basically aliases to base colors:
/// @type Color
/// @access public
$article_links: $color_blue_ocean;
/// @type Color
/// @access public
$main_background: $color_blue_ocean;
/// @type Color
/// @access public
$success_background: $color_green_forest;
/// @type Color
/// @access public
$footer_links: $color_green_forest;
/// @type Color
/// @access public
$error_background: $color_red_blood;
/// @type Color
/// @access public
$horizontal_lines: $color_red_blood;
// ...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:
/// @type Color
/// @access public // Public so that 'resolveVariables' can work
/// @hidden // Hidden in documentation despite it's public
$article_links: $color_blue_ocean;Thanks in advance!