You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doc generator output in Markdown mode (doesn't seem to appear in HTML output) has an odd table formatting for an embedded object that has been "promoted" to a shared object definition for that resource.
This shows up in the Redfish SecurityPolicy schema definition, which has 6 instances of properties sharing the TLSParameterSet object definition. The table added in "Property Details" for TLSParameterSet has multiple extraneous columns which compress the available column width. This is most evident when the normative output mode is used (the LongDescription text for the properties within that object are lengthy).
I have not determined if this is an issue unique to this particular schema or object, as this re-use of an object (also embedded in another object) may be unique across all schema definitions. Note that the "common object" function itself works fine - for example, Protocol in ManagerNetworkProtocol, is used >8 times but the property details table is normal.
The text was updated successfully, but these errors were encountered:
Doc generator output in Markdown mode (doesn't seem to appear in HTML output) has an odd table formatting for an embedded object that has been "promoted" to a shared object definition for that resource.
This shows up in the Redfish SecurityPolicy schema definition, which has 6 instances of properties sharing the
TLSParameterSet
object definition. The table added in "Property Details" forTLSParameterSet
has multiple extraneous columns which compress the available column width. This is most evident when the normative output mode is used (the LongDescription text for the properties within that object are lengthy).I have not determined if this is an issue unique to this particular schema or object, as this re-use of an object (also embedded in another object) may be unique across all schema definitions. Note that the "common object" function itself works fine - for example,
Protocol
in ManagerNetworkProtocol, is used >8 times but the property details table is normal.The text was updated successfully, but these errors were encountered: