Problem description
In code/API_definitions/click-to-dial.yaml, two of the three mandatory info.description blocks have no blank line directly after their <!-- CAMARA:MANDATORY:...:BEGIN --> marker: authorization-and-authentication and request-body-strictness. Commonalities r4.4 added this blank line to the canonical info-description-templates.yaml so Swagger Editor renders the following Markdown heading; without it, the heading fails to render. additional-error-responses already has the blank line.
Expected behavior
Add one blank line directly after the BEGIN marker for authorization-and-authentication and request-body-strictness, matching the canonical code/common/info-description-templates.yaml, on all three mandatory blocks before the public release.
Alternative solution
None.
Additional context
camaraproject/tooling#456 / camaraproject/tooling#457 add validator detection for this gap (will ship with the next tooling release), so this would otherwise start firing as a warning/error automatically once picked up.
Problem description
In
code/API_definitions/click-to-dial.yaml, two of the three mandatoryinfo.descriptionblocks have no blank line directly after their<!-- CAMARA:MANDATORY:...:BEGIN -->marker:authorization-and-authenticationandrequest-body-strictness. Commonalities r4.4 added this blank line to the canonicalinfo-description-templates.yamlso Swagger Editor renders the following Markdown heading; without it, the heading fails to render.additional-error-responsesalready has the blank line.Expected behavior
Add one blank line directly after the
BEGINmarker forauthorization-and-authenticationandrequest-body-strictness, matching the canonicalcode/common/info-description-templates.yaml, on all three mandatory blocks before the public release.Alternative solution
None.
Additional context
camaraproject/tooling#456 / camaraproject/tooling#457 add validator detection for this gap (will ship with the next tooling release), so this would otherwise start firing as a warning/error automatically once picked up.