When issuing commands with _async the response will not be what the spec defines, instead one with executeId and jobId
For this OpenAPI spec to be a faithful reproduction of the rclone rc API, should any job which uses GlobalAsyncParam also have a oneOf with a an AsyncJobResponse?
Another idea would be to to see if a 202 could be returned by rcd when _async is sent, and then this would be fairly easy to handle here and in clients, since the response code would allow for generators to handle this as well.
That would require patching rclone, which may not be accepted.
Curious your thoughts?
Thank you for the work on this OpenAPI spec, it's really valuable to have this resource to generate clients!
When issuing commands with
_asyncthe response will not be what the spec defines, instead one with executeId and jobIdFor this OpenAPI spec to be a faithful reproduction of the rclone rc API, should any job which uses
GlobalAsyncParamalso have aoneOfwith a an AsyncJobResponse?Another idea would be to to see if a 202 could be returned by
rcdwhen_asyncis sent, and then this would be fairly easy to handle here and in clients, since the response code would allow for generators to handle this as well.That would require patching rclone, which may not be accepted.
Curious your thoughts?
Thank you for the work on this OpenAPI spec, it's really valuable to have this resource to generate clients!