-
Notifications
You must be signed in to change notification settings - Fork 182
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
Inline Defined in
headings
#746
Comments
This issue also applies to Classes and Enums. As discussed in #743 it potentially makes more sense to move the defined in with the symbol as inline text rather than a heading placed at the bottom of the symbol. This would be placed directly under the heading or declaration/signature block. This would be implemented across the board for example: InterfaceType AliasI actually think this would be welcomed by users as this heading can create quite a lot of noise on auto-generated tocs. |
Very much agree with this direction, thanks @tgreyuk! |
## Defined in
headingDefined in
headings
@techfg as discussed "Defined in" headings have been moved inline as per example in above discussion. Available in |
Looks good in v4.4.0 @tgreyuk, thank you! |
What package is the bug related to?
typedoc-plugin-markdown
Describe the issue
As mentioned here, interfaces do not currently contain an h2 for
Defined in
, which is inconsistent compared to html equivalent. Type aliases do contain h2 forDefined in
as expected.Repro: https://stackblitz.com/edit/vitejs-vite-ejmybzgn
TypeDoc configuration
Expected behavior
An h2 for
Defined in
should appear for each interfaceThe text was updated successfully, but these errors were encountered: