-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Description
I commonly use extensions with PVMT to add custom property to Capella elements.
The generated XHTML documentation has a weird behaviour as shown in this example
I defined an sys.API extension with PVMT to be assigned to ExchangeItem with ExchangeMechanism=OPERATION, with two properties: Method and Response.
The generated documentation include the property values associated to the items and the definitions imported from the extensions. I think that this behavious is annoying and the repeated properties should be removed, leaving only the first part as shown below
The extension documentation is already provided extension tree.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels