Improve package approach to accomplish new use cases #1466
Replies: 1 comment 1 reply
-
|
I’ve been using the flutter_form_builder ecosystem for about three years across multiple projects involving highly complex multi-step forms, where fields often depend on one another. The biggest challenge I’ve encountered so far is managing scenarios where a field’s visibility and validation dynamically depend on the value of another field. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I glad to know that flutter_form_builder is useful for your projects! About the challenge, I agree that conditional validation and built forms is difficult on current package version. Some of this issue related this too:
If do you want share some examples here or even open new issues about this topic, we are open to discuss better solution about them |
Beta Was this translation helpful? Give feedback.
-
This package was created in 2018, when Flutter started the journey like multiplatform alternative.
From since until today, Flutter changed a lot. Has more packages, support, approach, documentation and apps in production. Currently, is one of most used multiplatform ecosystem.
FlutterFormBuilder try to follow the changes of Flutter improving the package, with whole ecosystem created or null safety migration.
Even so, because of the way the package has been built and the way the functionalities have been implemented, some use cases are still difficult or impossible to apply. In this list, we can see some cases:
Comparing with other packages that have been created later, we can see how there are other approaches to implement forms.
To encourage the sharing ideas and discuss solutions, I create this discussion in which everyone can participate to make the Flutter Form Builder Ecosystem better. By and for the Flutter community
Beta Was this translation helpful? Give feedback.
All reactions