-
Notifications
You must be signed in to change notification settings - Fork 3
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
Allow TS variables to be documented #111
Conversation
test/ts-parser.test.js
Outdated
expect(parsedData.constructs.map(function(c) { | ||
return c.node.name; | ||
})).to.eql(['param.Message', 'param.path', | ||
'Greeter', 'PathParameterValues']); | ||
'Greeter', 'PathParameterValues', 'greeter']); |
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.
Why do we also not check for the namespace param
?
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.
Namespace param
has become a prefix for its members.
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.
So it's impossible to generate docs based on the api docs directly on top of the namespace currently, right?
@shimks I have improved how |
For example: export namespace a { export const X = 1; export const Y = 2; } export const B = 'b';
This is awesome, thank you @raymondfeng 👏 |
For example:
Description
Related issues
Checklist
guide