Releases: valit-stack/Valit
Releases · valit-stack/Valit
v2.0.0
-
All string rules has their predicates changed. Instead of
string.IsNullOrEmpty(argument)
onlynull
check is performed now. More details can be found in issue #166 . This is the reason why major version number has been bumped, since it may be a (business) breaking change for some folks. -
ValitRule
predicate does not get evealuated ifWhen()
condition is not fulfilled.
v1.0.0
v1.0.0-preview1
- Removed
IValitRulesProvider<TObject>
interface. - Both
Ensure
andEnsureFor
methods for nested objects accepts nowIValitator<TObject>
as a parameter. - Each validation rule has now a default error message
v0.2.0
- Added support for
bool
type. - Added support for validating nested objects.
- Added support for validation collections.
- Introduced
IValitRulesProvider<TObject>
interface. - Introduced
IValitator<TObject>
interface . - Added
CreateValitator()
extentension methods for bothIValitRulesProvider<TObject>
andIValitRules<TObject>
types.. - Added new overload for
WithMessage()
extension method which acceptsFunc<string>
as parameter. - Added missing
Required()
rule forstring
type.
v0.1.0
- Added validation rules for the following data types (with full support for
Nullable<T>
):
Byte
DateTime
DateTimeOffset
Decimal
Double
Float
Guid
IEnumerable<T>
Int16
Int32
Int64
SByte
String
TimeSpan
UInt16
UInt32
UInt64
-
Added support for tagging rules.
-
Added support for creating conditional rules.
-
Added support for validation strategies:
- Complete (default)
- Fail Fast
- Custom strategy
- Added support for validation errors:
- Error messages, Message providers
- Error codes