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 understand that it's because this library is older than the inclusion of the Result type in FSharp.Core. But maybe it would be worth adding a separate Result-based validation module? Maybe even ultimately obsoleting the current Choice-based one.
The text was updated successfully, but these errors were encountered:
I totally agree with that! Let's add a Result-based validation module and deprecated the Choice. In the next major version we can obsolete it. Should I do it or leave it for you?
I'm not sure what the new module should be called though. Validate? Validator? Or maybe still Validation but located in a sub-namespace to avoid collision?
I like the idea of Validation located in a sub-namespace. With such approach I would be able to simply switch to new implementation by change the open in my code and fixing compiler errors.
I understand that it's because this library is older than the inclusion of the
Result
type in FSharp.Core. But maybe it would be worth adding a separateResult
-based validation module? Maybe even ultimately obsoleting the currentChoice
-based one.The text was updated successfully, but these errors were encountered: