Fixed #

• Corrected phone number regex pattern in PhoneRule to properly validate various formats.
• Resolved issues in PhoneRule where null and empty string inputs were incorrectly validated as successful.

Added #

• Added tests for null and empty string cases in PhoneRule to ensure accurate validation behavior.

Changed #

• FormInputValueRule now requires errorMessage in its constructor.

Added #

• Top-level asyncValidator<T>(rules, {debounceDuration}) helper for async validation.
• Top-level compositeValidator<T>(syncValidators, asyncValidators) helper for combined sync/async validation.

Changed #

• validator<T>(rules) now returns a closure String? Function(T?) for implicit tear-off compatibility with Flutter FormFieldValidator.
• CompositeValidator<T> consumes sync validators as functions (String? Function(T?)), aligning with the validator helper.
• Documentation and examples updated to use validator, asyncValidator, and compositeValidator helpers.

Breaking Changes #

• Export Validator, AsyncValidator, and CompositeValidator types, but their constructors are non-public; use helpers to instantiate.
• compositeValidator uses positional parameters: compositeValidator(syncValidators, asyncValidators).

Added #

• Top-level validator([]) helper for concise validator creation.

Changed #

• Documentation examples updated to prefer validator([]) for brevity.
• Migrate date-related APIs to operate on String inputs:
  • DateRule now validates date strings (parsing with DateTime.tryParse).
  • DateRangeRule now compares start/end date strings (parsing internally).
  • Updated tests and README examples accordingly.

Deprecated #

• Direct constructor Validator([...]) in favor of validator([]).

Breaking Changes #

• Removed Validator.forString, Validator.forNumber, Validator.forBoolean, and Validator.forDate. Use the top-level validator([]) helper instead.
• Removed AsyncValidator.forString, AsyncValidator.forNumber, AsyncValidator.forBoolean, and AsyncValidator.forDate. Use the AsyncValidator<T>([rules]) constructor instead.

Changed #

• Changelog ><

Added #

• Customization options for validation error messages on specific password rules

Changed #

• Update documentation

Added #

• Introduce FormInputValueRule for validating numeric values with min and max constraints. The main difference with ValueRule is that it works with form inputs (hence accepts String? as value).

Changed #

• Update documentation

Fixed #

• Fix regex pattern for email validation to correctly handle multiple domains

Added #

• Introduce AsyncValidator class for handling asynchronous validation
• New CompositeValidator class for combining multiple validators (to offer an unified API for both sync and async validation)
• Update readme with new async validation examples

Added #

• Asynchronous validation support:
  • New AsyncValidationRule base class for creating async-specific validation rules
  • Async validation state tracking with AsyncValidationState class
  • Debouncing support for async validation to prevent excessive API calls
  • Manual async validation triggering with validateAsync() method
  • Example implementation of username availability checking
• New properties for validation state management:
  • isValidating - Indicates if async validation is in progress
  • isValid - Indicates if the last async validation was successful
  • errorMessage - Provides the current error message from either sync or async validation

Changed #

• Update documentation

Changed #

• Updated documentation

Added #

• New validation rules:
  • DateRule - Validates dates with min and max constraints
  • DateRangeRule - Validates date ranges between two fields
  • URLRule - Validates URLs with optional protocol checking
  • IPAddressRule - Validates IPv4 and IPv6 addresses
  • CreditCardRule - Validates credit card numbers with Luhn algorithm
• Updated documentation

Changed #

• Improved error message formatting
• Enhanced type inference for validation rules
• Better handling of null values
• Updated documentation with more examples

Fixed #

• Edge cases in phone number validation
• Memory leak in form validation
• Type conversion issues in numeric validators

Added #

• Initial release of Form Shield
• Core validation framework with ValidationRule abstract class and ValidationResult class
• Validator class with support for chaining multiple validation rules
• Type-specific validator factory methods: forString(), forNumber(), forBoolean(), and forDate()
• Built-in validation rules:
  • RequiredRule - Validates that a value is not null or empty
  • EmailRule - Validates email addresses with customizable regex pattern
  • PasswordRule - Validates passwords with configurable complexity requirements
  • PasswordMatchRule - Validates that passwords match
  • LengthRule - Validates string length with min and max constraints
  • MinLengthRule - Validates minimum string length
  • MaxLengthRule - Validates maximum string length
  • ValueRule - Validates numeric values with min and max constraints
  • MinValueRule - Validates minimum numeric value
  • MaxValueRule - Validates maximum numeric value
  • PhoneRule - Validates phone numbers
  • CountryPhoneRule - Validates phone numbers for specific countries
  • CustomRule - Allows custom validation logic with fixed error message
  • DynamicCustomRule - Allows custom validation logic with dynamic error messages
• Seamless integration with Flutter's form validation system
• Example login form implementation