Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solution description
In most cases, the type is inferred when
FormBuilderState.fields
is assigned to a variable. An example:However, when the dev needs to pass the reference of fields to a function, closure definition, constructor etc., they have to explicitly define its type. Currently, the type for
FormBuilderState.fields
isMap<String, FormBuilderFieldState<FormBuilderField<dynamic>, dynamic>>
. So, consider the simple function (which might also be taken as an event definition in BLoC) which needs to take fields as input:So, instead of having this long type definition, we can use
typedef
to create an alias, which is the primary purpose of this PR. So, newlogIn
function would be:Pros:
Cons (that I can think of):
FormBuilderField
in the library, might lead to confusion or misuse.To Do