BindQuery usage with required params

[joprice]

Is there a way to get CLIMutable to treat a field as required? I currently get default values such as 0 for int, and null for string. It would be useful for validation to have that handled by the data definition without runtime errors, if possible.

[Lanayx]

Hi! Have you seen the validation documentation?. It should work for string. For int you might want use this SO answer.

[joprice]

Oh wow don't know how I overlooked that. I'm also using some "newtype" single element DU wrappers I need to test with those attributes. For now, I created a newtonsoft jobject from the query and parsed it as json using Thoth, which gives me type-based parsing control, but if I can get away with something simpler I'll switch to that.

[Lanayx]

Right, the recent validation feature was added specifically with that in mind - to give a simple instrument familiar to many .NET developer allowing quick implementations, while also not preventing to do FP-style validations further on if needed.