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 Dec 13, 2023. It is now read-only.
Hi
We are trying to map conductor rest API to GraphQL schemas and facing a problem, that some endpoints return incorrect status codes or bodies.
For example: POST api/metadata/workflow return status code 200 and without body, but should be 201 with/without body or 200 with the body. POST api/metadata/workflow return 500, when workflow exists, but should be 409 DELETE api/metadata/workflow// also return 200 but should 204
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
-
Hi
We are trying to map conductor rest API to GraphQL schemas and facing a problem, that some endpoints return incorrect status codes or bodies.
For example:
POST api/metadata/workflow return status code 200 and without body, but should be 201 with/without body or 200 with the body.
POST api/metadata/workflow return 500, when workflow exists, but should be 409
DELETE api/metadata/workflow// also return 200 but should 204
Is any chance to use recommended status codes?
Beta Was this translation helpful? Give feedback.
All reactions