-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MarkdownPlugin populates route
property
#20
Conversation
does not nest references, also depths aren't 100% accurate yet.
works really well, does not rewrite references.
to make rendering headings really easy. Compiler turns all `@#+` tags into `tag: "heading"`, but can't populate `route` yet. Page operates on "page" and "heading" tags (so readable!).
with fully qualified path to the resource: `path/to/page[.heading]`. remove obsolete heading/pageReference options as all slugification happens inside MarkdownPlugin.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! Please also regen the docs
* Type guard to determine if a `contents` node is an `@tag` statement. | ||
* Optionally tests tag name too, if `tagName` arg is provided. | ||
*/ | ||
export function isTag(node: StringOrTag, tagName?: string): node is ITag { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
handy!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep very proud of this
add fake _nav page in markdown testPreview: docs |
minor polishPreview: docs |
IHeadingTag extends ITag
with route & level to make rendering headings really easy.@#+
tags intotag: "heading"
, but can't populateroute
yet.route
property in pages and nav with fully qualified path to the resource:path/to/page[.heading]
.