Use 400 error instead of 500 on bad composer.json
When publishing a composer package via the API, if the composer.json file is missing or malformed, the backend returns a 500 error. This commit return a more appropriate 400 Bad Request instead.
Showing
Please register or sign in to comment