We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It should be possible for users to define the header for their sphinx topic via the README file.
To support this, users will be able to supply an H1 in their README file which will be used instead of the module name for the topic's first heading.
The text was updated successfully, but these errors were encountered:
Sphinx improvements
dc00c8f
* Fix #228: allow readme file to define sphinx topic header * Fix #185: move multi-language tabs after readme * Update README
feat(sphinx): allow readme file to define sphinx header and reorganiz…
405da9c
…e topic (#229) * Fix #228: allow readme file to define sphinx topic header * Fix #185: move multi-language tabs after readme * Update README
v0.7.6 (#239)
04cb6bb
Bug Fixes ====================== * Sphinx generated incorrect type references for display ([#232](#232)) ([b664805](b664805)) * **jsii:** Defaulted parameters were not rendered as optional ([#234](#234)) ([578bf9c](578bf9c)), closes [#233](#233) * **jsii:** Don't skip emit on TS errors when in "watch" mode ([#236](#236)) ([30d1491](30d1491)), closes [#235](#235) * **jsii:** Optional `any` represented as required ([#237](#237)) ([91074f3](91074f3)), closes [#230](#230) Features ====================== * **sphinx:** allow readme file to define sphinx header and reorganize topic ([#229](#229)) ([405da9c](405da9c)), closes [#228](#228) [#185](#185) * Document overriden/inherited members ([#238](#238)) ([7a6278a](7a6278a)), closes [#196](#196)
No branches or pull requests
It should be possible for users to define the header for their sphinx topic via the README file.
To support this, users will be able to supply an H1 in their README file which will be used instead of the module name for the topic's first heading.
The text was updated successfully, but these errors were encountered: