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
Do you have any recommendations on implementing normalization for values, and/or might there be justification for implementing an option to support normalization during construction? Something like
Right now, I'm looking at normalizing string values via trimming (at a minimum). I can't use Validate to modify the value because my value is readonly. I'd also like to use the value via json conversion, but I don't see an obvious way to inject normalization in there.
As another potential example off the top of my head, consider something like a clamped numeric value, where numbers outside a range are accepted but clamped to the bounds of the range.
The text was updated successfully, but these errors were encountered:
Note: Support for the API is slightly different from @etinquis 's suggestion.
Since partial method does not support return values, we use the following style:
Do you have any recommendations on implementing normalization for values, and/or might there be justification for implementing an option to support normalization during construction? Something like
Right now, I'm looking at normalizing string values via trimming (at a minimum). I can't use Validate to modify the value because my value is readonly. I'd also like to use the value via json conversion, but I don't see an obvious way to inject normalization in there.
As another potential example off the top of my head, consider something like a clamped numeric value, where numbers outside a range are accepted but clamped to the bounds of the range.
The text was updated successfully, but these errors were encountered: