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
Currently in order to generate general docs about the usage of a package, we're using categories. These categories are then generated as "topics" only if we actually use them inside the doc comments like {@category xyz}. It would be nice if we have an option to have general docs that we can add as .md files by adding them to dartdoc_options.yaml without specifying them inside the source as well.
It is similar. We could use the same category mechanism as far as I'm concerned in this issue without having to manually add all the categories to the main library for example:
/// {@category foo}
/// {@category bar}
library;
There is a showUndocumentedCategories option but that doesn't do this.
Currently in order to generate general docs about the usage of a package, we're using categories. These categories are then generated as "topics" only if we actually use them inside the doc comments like
{@category xyz}
. It would be nice if we have an option to have general docs that we can add as.md
files by adding them todartdoc_options.yaml
without specifying them inside the source as well.cc @jonasfj
The text was updated successfully, but these errors were encountered: