-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
feat: Support for reference tag [#153] #154
Conversation
@@ -74,6 +76,37 @@ export default function ApiItem({ readme: Readme, route }: ApiItemProps) { | |||
[nextItem, prevItem], | |||
); | |||
|
|||
// Add @reference categories. | |||
const referenceCategories: Record<string, { title: string; children: number[] }> = {}; |
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.
This data should probably be built before even making it to the react side of things.
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.
Fixed. Please re-review.
Hi @milesj Can you take a look when you have a chance? |
Hello @milesj Can you please review this when you get a chance? |
Can you post a screenshot of what this looks like in practice? |
@milesj The screenshot in PR description is taken from a real example. The new sections |
@milesj One last question, how can we release the changes? Is it automatically triggered? |
I have to manually do it. I'll get around to it later today. |
This PR adds support to show
@reference
tag, which is a custom tag, as discussed in #153You can use this tag as
@reference <Name> {@link <Exported class>}
E.g.
It would look like,
If your IDE complains about using
@reference
tag, which is a custom tag not supported in TypeDoc, then you will need to extend their schema definition by putting a newtsdoc.json
in the root of your directory.