@alexzeitler@mastodon.social I have memory glimp...
@alexzeitler@mastodon.social I have memory glimpses of this in the other site =, someone from the team mentioned that binding was not the same as validation and rather than throwing exceptions there which could be costly (if aspnet did it so they left it to userland) it would just not bind that was more-less the reasoning.
pick that with a grain of salt as I can'f find the tweets
@angelmunoz@misskey.cloud I was expecting something like this but it doesn't make sense to me because this makes building robust APIs unnecessarily hard. That way you can't send the client a useful error. They didn't have to throw an exception, they could just have null-ed the property in question. Having a null property could point the client towards the right direct while an null object leaves everybody in the dark.