Closed ilg-ul closed 2 weeks ago
Thanks.
In order to fix this properly I have introduced new headings "Get Signature" and "Set Signature" (these are localized typedoc strings). These additional headings are required to maintain the semantic integrity of heading levels, but also I think it clearly convey that each block documents the method signature for getting or setting a property, making it immediately obvious to readers.
Hopefully this is acceptable - fix in typedoc-plugin-markdown@4.2.10
This issue is almost the same with my previous issue (I should not close it): https://github.com/typedoc2md/typedoc-plugin-markdown/issues/701
In order to fix this properly I have introduced new headings "Get Signature" and "Set Signature" (these are localized typedoc strings).
Great!
Could you check if those headings are also rendered properly when the accessors are part of a category/group?
Yes - seems to be good. Being part of a category/group shouldn't effect the behaviour - well I hope not anyway :).
I confirm that the latest release solved this issue.
Thank you for the quick fix.
What package is the bug related to?
typedoc-plugin-markdown
Describe the issue
I have a class with an accessor (
logger
) that has both get and set methods.The Return of the getter is rendered at the end, as like being the return of the setter, and the return of the setter is not rendered:
TypeDoc configuration
Expected behavior
Two return sections: