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
But it could be convenient to also use the field alias instead. For example, if object serialization is built dynamically from aliases passed in request parameters, it would avoid having to do the reverse mapping.
On the other hand, reverse mapping would be quite easy, so it's not really an issue (things gets more complicated when it comes to serialized methods). Also, allowing field names and aliases at the same could bring some edge cases with both overlapping, but IMO this kind of thing should not happen in real life.
The text was updated successfully, but these errors were encountered:
Several features of apischema requires an object field to be passed, e.g. field ordering, field validator, or object serialization.
Fields can be either:
ObjectField
Field
But it could be convenient to also use the field alias instead. For example, if object serialization is built dynamically from aliases passed in request parameters, it would avoid having to do the reverse mapping.
On the other hand, reverse mapping would be quite easy, so it's not really an issue (things gets more complicated when it comes to serialized methods). Also, allowing field names and aliases at the same could bring some edge cases with both overlapping, but IMO this kind of thing should not happen in real life.
The text was updated successfully, but these errors were encountered: