Package selection guidance compiled from public package information, community data, and project usage.
Formdator is a Dart package offering a flexible collection of form field validators designed to be composed together using the Decorator Pattern. It enables developers to combine multiple validation rules seamlessly, allowing for reusable and modular validation logic across forms. Ideal for applications requiring dynamic or complex input validation, it supports various platforms including mobile, web, and desktop. The package emphasizes clean, composable code and integrates easily with Flutter's form ecosystem.
Use cases
Dynamic form validation
Complex input rules
Reusable validation components
Cross-platform forms
Custom validation chains
Real-time feedback
Key features
Composable validators
Decorator Pattern implementation
Platform-agnostic
Easy integration with Flutter forms
Modular design
Extensible validation logic
Suitable for
Developers building complex forms
Teams needing maintainable validation code
Apps requiring multi-rule validation
Flutter projects with cross-platform needs
Projects emphasizing code reusability
Considerations
Requires understanding of decorator pattern
May increase complexity for simple forms
Limited documentation beyond basic examples
Depends on proper setup in form widgets
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Formdator is a fully object-oriented package for validating Flutter form fields.
Its main benefits, compared to all other similar packages, include:
Dependency-free: there is only pure Dart code.
Object-oriented mindset: the elements for validation are immutable
objects that can be combined in various configurations.
Classes with short — yet meaningful — names like Req for required fields;
ReqEmail for non-empty, well-formed emails; Len for length constraints;
Int for integer-only values; and so on.
Easy-to-compose validators: e.g., the command Trim(Email()) produces a
validator that trims an email value before validating it.
Multiple validation at once: you can apply multiple validation rules at once
by using the Pair or Rules classes.
Built-in set of compound validators: e.g., to validate an email and limit its
length to a maximum of 50 characters, simply use an instance of
Email.len(50) — write less; do more!
For easier integration with Flutter form fields, every validator implements the
call() method. As a result, any validator object can be called as a function —
Callable Classes.
Getting Started
The following code snippet demonstrates how you can easily group the Rules,
Req, Len and Email classes together to create a kind of
'email-max-50-characters' constraint.
@overrideWidgetbuild(BuildContext context) {
returnTextFormField(
validator: Rules<String>([ // The "Rules" class performs multiple validations at once.Req(blank: 'Please enter the email'), // "blank" is the error message in case of field left blank.Len.max(50, long: 'Email length cannot exceed 50 characters'), // "long" is the error message if an input value is too long.Email(mal: 'Malformed email'), // "mal" is the error message in case of malformed email.
]),
);
}
Or — even better — use the compound validator ReqEmail to perform the same
task.
logic
— validation logic and unit testing (Equal, Ok, Nok, ValueBack).
net —
internet (Email, Ipv4, Ipv6, MacAddr, Url, etc.).
numeric
— validators related to numbers or digits (Digit, Hex, Int, Num, etc.).
Demo application
The demo application provides a fully working example, focused on demonstrating
exactly four validators in action — Pair, ReqLen, ReqEmail, and Equal.
You can take the code in this demo and experiment with it.
To run the demo application:
git clone https://github.com/dartoos-dev/formdator.git
cd formdator/example/
flutter run -d chrome
This should launch the demo application on Chrome in debug mode.
Contribute
Contributors are welcome!
Open an issue regarding an improvement, a bug you noticed, or ask to be
assigned to an existing one.
If the issue is confirmed, fork the repository, do the changes on a separate
branch and make a Pull Request.
After review and acceptance, the Pull Request is merged and closed.
Make sure the command below passes before making a Pull Request.