VeryGoodOpenSource / VeryGoodOpenSource/formz
Some fields do not require validation
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 487
- Forks
- 42
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 2
Description
Every time a FormZInput is defined we must add a validation error even if we never get to use it. Some fields do not require validation, but do require being inside the form to later verify if the field has changed its value.
Example:
// abstract class FormzInput<T, E>
enum StatusMemberInputError { none }
class StatusMemberInput extends FormzInput<bool, StatusMemberInputError> {
const StatusMemberInput.pure({bool value = false}) : super.pure(value);
const StatusMemberInput.dirty({bool value = false}) : super.dirty(value);
@override
StatusMemberInputError? validator(bool value) => null;
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the FormzInput definition and the code that requires a validation error for each input. Review the existing form and input tests, then make it possible for an input to participate in change tracking without requiring validation; done when the StatusMemberInput example is supported and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100