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
I guess you're right. Removing the check would allow users to specify a default value for required fields on partial loading, while still raising an error on non-partial loads. I don't see any obvious downside to this.
Would you like to send a PR that removes the check and adds tests?
I just realized that load_default is not used when using partial anyway.
This is not explicit in the doc and in fact I'm wondering if this was intended in the first place but it's probably hard to change now as people may be relying on it.
Yeah no need to change it in 3.x since. And based on my testing it worked the same in 2.x (ignoring load_default).
For 4.x this could be maybe interesting. But don't know what is developer expectation regarding this. You could still exclude + partial (to have possibility to use load_default or not).
Currently we are using load_default and required together for some cases where we are working with partial loading.
In this case field that is required is no longer required and should use load_default value, but it is not allowed in the code:
Would it make sense to allow it for such cases?
The text was updated successfully, but these errors were encountered: