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 Jan 7, 2022. It is now read-only.
Currently the form for updating an event type would happily allow you to omit some fields which are marked as required in the form itself, e.g. "Owning application" and "Audience". Then the API responds with 400 Bad Request which is sometimes not really straightforward to parse.
In case of omitting the owning application, no error occurs at all. So this is contradictory to the marking of the field as required.
Preferably, the HTML form in UI would highlight the required and missing fields with red color when the user tries to submit it, avoiding the API call in the first place.
The text was updated successfully, but these errors were encountered:
Currently the form for updating an event type would happily allow you to omit some fields which are marked as required in the form itself, e.g. "Owning application" and "Audience". Then the API responds with
400 Bad Request
which is sometimes not really straightforward to parse.In case of omitting the owning application, no error occurs at all. So this is contradictory to the marking of the field as required.
Preferably, the HTML form in UI would highlight the required and missing fields with red color when the user tries to submit it, avoiding the API call in the first place.
The text was updated successfully, but these errors were encountered: