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
{{ message }}
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
Please describe the feature that you want to propose
Context
Currently, we have the canvas representation for the Rest DSL. This works fine but as soon as we get a big OpenAPI spec, the canvas cannot zoom out enough to see the whole flow.
Goal
Provide an alternative view for the Rest DSL, similar to Swagger or Apicurio, that displays a table with the endpoints.
Proposed user journey
Starting from a dedicated user interface, the user adds an OpenAPI spec URI or uploads a file.
With that information in the context, the user can now click on "Generate all routes" to populate the Rest DSL table
Alternatively, the user could use the routes list to select "Create a new route from direct URI" which later on will display a list of the available URIs
In addition to that, said context should be available for the Direct step, meaning that the URI could be written from a Rest DSL list.
The text was updated successfully, but these errors were encountered:
Please describe the feature that you want to propose
Context
Currently, we have the canvas representation for the Rest DSL. This works fine but as soon as we get a big OpenAPI spec, the canvas cannot zoom out enough to see the whole flow.
Goal
Provide an alternative view for the Rest DSL, similar to Swagger or Apicurio, that displays a table with the endpoints.
Proposed user journey
The text was updated successfully, but these errors were encountered: