Skip to content
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

Properties as Table like function properties #109

Closed
ozum opened this issue Nov 11, 2019 · 2 comments
Closed

Properties as Table like function properties #109

ozum opened this issue Nov 11, 2019 · 2 comments
Labels
next Fix available in the '@next' release

Comments

@ozum
Copy link
Contributor

ozum commented Nov 11, 2019

Hi,

Is it possible to document interface parameters like function properties as a table instead of listed one by one.

The reason I'm asking is that, I'm using typedoc to create README.md files and interface parameters make the page very long.

Thanks,

@ozum ozum changed the title Parameters and Properties as Table Properties as Table like function properties Nov 11, 2019
@capraynor
Copy link

Hi, @ozum @tgreyuk

The requirement might be different from different case.

Some project's API document (property comments) are simple (one-line), so that project might need a property-table markdown description to make the document clean & tidy.

However, some project's API document are complex (like they needs to include a example-code-comment inside the property comment).
In this situation, the comment is a multi-line comment.
Due to the markdown table has poor support for multiline-text,
So markdown table may not fit this situation.
So the list mode is still needed in this situation.

If someone is willing to implement this, I suggest to provide a configuration to switch the document style:

Table mode, that render the properties to table, which fits the one-line comment in properties.

List mode, that render the properties to a list (current behavior), witch fits the multi line comments in properties.

@tgreyuk
Copy link
Member

tgreyuk commented May 3, 2024

@tgreyuk tgreyuk closed this as completed May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next Fix available in the '@next' release
Projects
None yet
Development

No branches or pull requests

3 participants