-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenAPI support for endpoint introspection #25
Comments
@dekimir Suggest to add TypeScript decorators for describing the shape of the endpoint inputs and outputs. |
this must be optional. Something we work well without (in which case we show the result of |
Update: pretty much everybody hits the issue of not finding the correct URL for their endpoints when deploying to the ChiselStrike platform. We need this introspection support to show the endpoints in the web UI. |
Although OpenAPI would be nice, this is not strictly necessary to solve the user's issue. It may be advisable to change that output to json so we can show models, endpoints and policies separately. That's not to say OpenAPI won't make things better (as it will include documentation for the endpoints as well), but we should do something to show the output of describe as well. |
@glommer OpenAPI is not an issue at all here. I can trivially generate an OpenAPI JSON with the endpoint paths. The real issue is that those paths don't translate into meaningful developer experience. You need to know what HTTP methods they support at minimum and preferrably you should also know what kind of parameters they accept. You do, however, have a point that perhaps we should indeed do something simple now to address the issue of people tripping over wrong URLs all the time. @glommer Would you prefer |
if we can generate basic openapi skeletons that just show the endpoint names without user change, then we can do it. (I don't know enough). Otherwise we should go with the describe route |
There's now preliminary support for OpenAPI added in commit a3e5944 |
(ignore my comments I deleted on this one, seeing I thought it was the other ticket that got closed) |
I am closing this as we support OpenAPI. There's a follow-up issue #1071 to make the APIs more discoverable. |
Let's add support for OpenAPI to allow Swagger or Postman introspection of the endpoints.
The text was updated successfully, but these errors were encountered: