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
We're using C4/Structurizr to model a series of microservices and are publishing versions of the model each time we release a new service. These are becoming quite popular with developers, and we’re looking to improve what we’re doing by including each services API as part of the versioned output.
To this end, we’re looking to have a “swagger-ui” like rendering of the OpenAPI YAML/JSON files as part of the documentation output from Structurizr, using something like Redoc or swagger-ui
Was just wondering if you’d consider extending the DSL, to include a openAPI keyword for a Container or Component, to enable the provision of a URL or file path reference to the OpenAPI file to be rendered for this component?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're using C4/Structurizr to model a series of microservices and are publishing versions of the model each time we release a new service. These are becoming quite popular with developers, and we’re looking to improve what we’re doing by including each services API as part of the versioned output.
To this end, we’re looking to have a “swagger-ui” like rendering of the OpenAPI YAML/JSON files as part of the documentation output from Structurizr, using something like Redoc or swagger-ui
Was just wondering if you’d consider extending the DSL, to include a
openAPI
keyword for a Container or Component, to enable the provision of a URL or file path reference to the OpenAPI file to be rendered for this component?Beta Was this translation helpful? Give feedback.
All reactions