Open
Conversation
Contributor
|
How are you thinking we would tell sassdoc to scan for this? Would we reference a particular njk file or macro from within a Sass file? Or would we want herman to find all the njk files in a list of paths and create a new page in the documentation for each one that contains annotations (thus making documentation in templates more of an equal peer to documentation in sass rather than secondary)? |
Member
Author
|
My thought was that we pass a nunjucks folder to scan, similar to the Sass — and add the documentation to |
Contributor
|
Cool, that's my preference too in terms of functionality. I'll have to look at whether we can implement it without changing sassdoc itself. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
document macros directly in the j2/njk markup, using sassdoc-like annotations