Joan Pablo

I'm also working right now on a Global Settings for ReactiveForm in which you can define ValidationMessages for all Reactive Widgets globally, at **ReactiveForm** level but also at **MainApplication** level....

> > But what if the developer makes a mistake and is setting the error message to **null** by accident and not intentionally? The program will run successfully but the...

Hi @taskindrp, Here is a simple code example: ```dart import 'package:flutter/material.dart'; import 'package:reactive_forms/reactive_forms.dart'; class RadioSample extends StatelessWidget { const RadioSample({Key? key}) : super(key: key); static const questionField = 'question'; FormGroup...

Hi, @taskindrp any update on this issue? Was it useful the code above? Do you still want to use checkboxes or the radio buttons is enough for you?

> also tried your implementation @joanpablo but still could check both radio buttons. Hi @taskindrp, I'm glad that you have solved the issue using reactive_forms_lbc, but I want to say...

Another question that I have for you: What exactly is your expected result: 1- One answer to all questions, something like: `{ answer: 'Option1' }` 2- Or do you want...

Hi @taskindrp sorry the delay. This is a fully functional version:  ```dart import 'package:flutter/material.dart'; import 'package:flutter_bloc/flutter_bloc.dart'; import 'package:reactive_forms/reactive_forms.dart'; class Question { final String label; const Question({ required this.label, });...

The previous example was implemented with the following dependencies: ```dart bloc: ^8.0.0 flutter_bloc: ^8.0.0 reactive_forms: ^14.1.0 ```

Hi @vasilich6107 Do you have an example of how this new implementation is better than the current implementation? I would like to have a use case implemented with both variants,...

Hi @vasilich6107, It is normal that the example you presented above fails, because you are blending the declarative programming of Flutter (when creating widgets) with the imperative nature of the...