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
When testing edit app endpoint using new or existing application, if a non-existent field is added to the payload,
for example field "chocolate", API returns 200, and field is not added.
This is a confusing behaviour, it could throw an error to forbid adding non-existent fields.
Tested the same endpoint using new or existing application, edit query to only contain "id" and no "update",
API returns 200, and the application object is not updated.
This is confusing, it should not allow edit when "update" is missing.
The text was updated successfully, but these errors were encountered:
Descriptions
When testing edit app endpoint using new or existing application, if a non-existent field is added to the payload,
for example field "chocolate", API returns 200, and field is not added.
This is a confusing behaviour, it could throw an error to forbid adding non-existent fields.
Tested the same endpoint using new or existing application, edit query to only contain "id" and no "update",
API returns 200, and the application object is not updated.
This is confusing, it should not allow edit when "update" is missing.
The text was updated successfully, but these errors were encountered: