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 is a bug, the implementation is incomplete. I would prefer 400 bad request since the route exists, it's the payload that is nonsensical.
A check to verify that the developer id exists should be sufficient to fix this.
In addition to verifying that the developer exists, we should also verify that the request is from the same developer. Control api will take care of the authentication and make it available on the connection as metadata. I'll write up a proposal on what data will be made available and how it is expected to be accessed.
The
issue_key
always issues key even it developer is not registered. The correct behaviour is to fail with 404 or bad request.The text was updated successfully, but these errors were encountered: