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
It seems to me that a client generated using OpenAPI/swagger would be 'more complete' and also more up-to-date as the REST API evolves. Would you agree? Why or why not?
The text was updated successfully, but these errors were encountered:
I think that generating a client via Swagger works well. The Swagger definition is "mostly complete" but there are a few spots that will require manual fix-ups. But you will get most of the endpoints "out of the box". I think you will also need to write your own OAuth connector if you would like to use OAuth. Overall I think if your interested in using a swagger/openAPI generated client , it is worth giving it a try to see if it meets your needs.
Cool. Thanks for the response. We are currently using a version of this client, so we will need to do some work to use a swagger client. I'm trying to weigh costs vs benefits of doing that. We are currently using basic auth, and I don't currently see us changing that part of things.
It seems to me that a client generated using OpenAPI/swagger would be 'more complete' and also more up-to-date as the REST API evolves. Would you agree? Why or why not?
The text was updated successfully, but these errors were encountered: