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
Currently the readme that is generated for user defined types is that it supports 1 level for exposing the properties in the readme.
For example: if a UDT contains (A, B) properties, then the readme will expose A and B separately in the readme. Which is great.
However, if the UDT contains (A, B (B1, B2)) .. then (B.B1) and (B.B2) will not be shown in the readme.
Ideally we should be able to drill down in the nesting so that the guidance is clear for nested properties as well.
The text was updated successfully, but these errors were encountered:
Example:
source
Sorry, something went wrong.
AlexanderSehr
Successfully merging a pull request may close this issue.
Description
Currently the readme that is generated for user defined types is that it supports 1 level for exposing the properties in the readme.
For example: if a UDT contains (A, B) properties, then the readme will expose A and B separately in the readme. Which is great.
However, if the UDT contains (A, B (B1, B2)) .. then (B.B1) and (B.B2) will not be shown in the readme.
Ideally we should be able to drill down in the nesting so that the guidance is clear for nested properties as well.
The text was updated successfully, but these errors were encountered: