A language for describing resource-oriented APIs & turning them into Swagger or resource diagrams. Oriented around the concepts we want to expose in the APIs.
As part of the developer portal effort, teams are being asked to add a summary to the OpenAPI specs so that the sidebar navigation in readme is easier to read in swagger ui
Currently if you put a string description above the operation in reslang it gets mapped to description in the OpenAPI spec
"A LiveRamp partner that can receive data"
subresource v2/Destination {
id: string
'/v2/destinations/{id}':
get:
operationId: Get v2/Destination
description: 'Fetch a single Destination' <== Comment goes into description
responses:
...
As part of the developer portal effort, teams are being asked to add a summary to the OpenAPI specs so that the sidebar navigation in readme is easier to read in swagger ui
Currently if you put a string description above the operation in reslang it gets mapped to description in the OpenAPI spec
See discussion at: https://liveramp.slack.com/archives/CPBAEKS9X/p1630612353029400