-
Notifications
You must be signed in to change notification settings - Fork 181
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
How to improve the formatting for types? #456
Comments
yes that would be perfect! if you can point me to a place in the code i can take a stab at it! |
So this option is already available in next version so might not be worth the effort . Options name is https://github.com/tgreyuk/typedoc-plugin-markdown/tree/next/packages/typedoc-plugin-markdown |
@tgreyuk the new version with ![]() Do you reckon anything can be done about the "Return Type" part? |
typedoc-plugin-markdown@4.0.0 https://www.typedoc-plugin-markdown.org/docs/options#usecodeblocks |
The output of
typedoc-plugin-markdown
can sometimes be very difficult to read, especially when compared to its HTML counterpart. Here's an example of HTML and Markdown outputs from the same codebase:HTML: https://metamask.github.io/keyring-api/latest/variables/KeyringAccountStruct.html
Markdown: https://docs.metamask.io/zs/keyring-doc/snaps/reference/keyring-api/modules/#keyringaccountstruct
The main difference being that the HTML output has one entry per line, whereas the Markdown output reads all on the same line, making it almost useless.
Thank you!
The text was updated successfully, but these errors were encountered: