Don't throw 400 when validation fail in Model.save() #14

New Issue

ashpie · 2021-01-21T16:34:53+01:00

ashpie commented

2021-01-21 16:34:53 +01:00

Sometimes, models are created as a side effect and not primary intent.

Throwing a 400 when a model fails validation on save if the request was not explicitely made to save that model is a mistake and should instead throw a 500.

Sometimes, models are created as a side effect and *not* primary intent. Throwing a 400 when a model fails validation on save if the request was not explicitely made to save that model is a mistake and should instead throw a 500.

ashpie added this to the v0.24.0 milestone 2021-01-21 16:34:53 +01:00

ashpie added the

bug

label 2021-01-21 16:34:53 +01:00

ashpie self-assigned this 2021-01-21 16:34:53 +01:00

ashpie modified the milestone from v0.24.0 to v0.26.0

2021-11-09 19:41:22 +01:00

Sign in to join this conversation.