Merge branch 'develop' into feature/198

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,53 @@
+---
+name: "\U0001F41B Bug"
+about: Something is crashing or not working as intended
+labels: bug
+
+---
+
+## Environment
+
+**Package version:**  
+
+<details>
+  <summary>Flutter doctor</summary>
+
+<!-- Paste the output of running `flutter doctor -v` below inside ``` and ``` -->
+```
+```
+
+</details>
+
+<details>
+  <summary>Code sample</summary>
+
+<!--
+      Please create a minimal reproducible sample that shows the problem
+      and attach it below between the lines with the backticks.
+
+      You can use a example code or Flutter sample app
+
+      Without this we will unlikely be able to progress on the issue, and because of that
+      we regretfully will have to close it.
+-->
+
+```dart
+```
+
+</details>
+
+## Description
+
+**Expected behavior:**
+
+**Current behavior:**
+
+## Steps to reproduce
+
+1. This
+2. Than that
+3. Then
+
+## Images <!-- if available, else delete -->  
+
+## Stacktrace/Logcat <!-- if available, else delete -->  

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,18 @@
+---
+name: "\U0001F4C3 Documentation Bug"
+about: You want to report something that is wrong or missing from the documentation.
+labels: documentation
+
+---
+
+### Describe the change you would like to see
+<!-- A clear and concise description of the bug or documentation you feel is missing.
+For example: The Technical Reference does not include information about the FormBuilderFilterChip widget. -->
+
+### How would the suggested change make the documentation more useful?
+<!-- Provide context for how the requested change would make the docs easier to use and improve your ability to develop successful applications with this packages.
+For example: It's hard to know a method exists or understand its use when you have to search through the code base to learn about it. Properly documenting it in the Technical Reference makes it easier for me to know what the flutter_fom_builder is (and is not capable of).  -->
+
+### Additional context
+<!-- Add any other context about your feedback here. 
+For example: I am reading the docs directly from GitHub, so it's harder for me to find information on a particular method if it's not included in the documentation. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,18 @@
+---
+name: "\U0001F680 Feature request"
+about: Suggest new feature or request for this project
+labels: enhancement
+
+---
+
+## Environment
+
+**Package version:**
+
+## Description
+
+**What you'd like to happen:**
+
+**Alternatives you've considered:** <!-- if available, else delete -->  
+
+**Images:** <!-- if available, else delete -->  

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,14 @@
+---
+name: "\U0001F914 Questions and Help"
+about: You have a quetion or need help using this packages
+labels: question
+
+---
+
+## Environment
+
+**Package version:**
+
+## Describe your question
+<!-- A clear and concise description of your question or help wanted.
+For example: How can I add a datetime field? -->

.github/PULL_REQUEST_TEMPLATE.MD

@@ -0,0 +1,20 @@
+## Connection with issue(s)
+
+<!-- If this pull request close some issue, use this reference to close it automatically -->
+Close #???
+
+<!-- Optional: other issues or pull requests related to this, but merging should not close it -->
+Connected to #???
+
+## Solution description
+
+## Screenshots or Videos
+
+<!-- Optional: to clearly demonstrate the feature or fix to help with testing and reviews -->
+
+## To Do
+
+- [ ] Check the original issue to confirm it is fully satisfied
+- [ ] Add solution description to help guide reviewers
+- [ ] Add unit test to verify new or fixed behaviour
+- [ ] If apply, add documentation to code properties and package readme

.github/workflows/reactive_forms.yaml

@@ -21,7 +21,7 @@ jobs:
       - uses: actions/checkout@v3
       - uses: subosito/flutter-action@v2
         with:
-          flutter-version: "3.0.0"
+          flutter-version: "3.16.0"
           channel: "stable"
       - run: flutter pub get
       - run: flutter test --no-pub --coverage
@@ -34,7 +34,7 @@ jobs:
       - uses: actions/checkout@v3
       - uses: subosito/flutter-action@v2
         with:
-          flutter-version: "3.0.0"
+          flutter-version: "3.16.0"
           channel: "stable"
       - run: flutter pub get
       - name: Analyze lib
@@ -49,13 +49,13 @@ jobs:
       - uses: actions/checkout@v3
       - uses: subosito/flutter-action@v2
         with:
-          flutter-version: "3.0.0"
+          flutter-version: "3.16.0"
           channel: "stable"
       - run: flutter pub get
       - name: Format lib
-        run: flutter format lib --set-exit-if-changed
+        run: dart format lib --set-exit-if-changed
       - name: Format test
-        run: flutter format test --set-exit-if-changed
+        run: dart format test --set-exit-if-changed
 
   publish-warnings:
     name: Publish warnings

CHANGELOG.md

@@ -1,3 +1,100 @@
+# 17.0.0
+
+## Breaking changes
+
+- Removed deprecated `onWillPop` from `ReactiveForm` and `ReactiveFormBuilder` widgets. 
+It was replaced with the `PopScope` widget.
+- `Validators.number` allows now to define negative numbers and decimal numbers with the addition
+of two optional arguments `allowNegatives` and `allowedDecimals`.
+
+## Features
+
+- Add `canPop` and `onPopInvoked` to `ReactiveForm` and `ReactiveFormBuilder` widgets.
+
+# 16.1.1
+
+## Fixes
+
+- Add default Context Menu to `ReactiveTextField`. 
+
+# 16.1.0
+
+## Features
+
+- Add `markAsPending()` method to `AbstractControl` to allow set the status
+to PENDING by demand.
+
+# 16.0.4
+
+## Fixes
+
+- Add missing properties to `ReactiveSwitchListTile.adaptative()` widget.
+- Add `showError()` to `ReactiveCheckbox` and `ReactiveCheckboxListTile` widgets. This does not
+display any error messages but it is now compatible with the Flutter builtin behavior of Checkboxes
+when Material 3 is enabled (`ThemeData(useMaterial3: true)`) in the active App Theme.
+
+## Enhances
+
+- Update `Readme.md` file with testing examples in the section 
+`ReactiveForm vs ReactiveFormBuilder which one?`
+
+# 16.0.3
+
+## Fixes
+
+- Fix an issue with `FormGroup` and `FormArray` were recursive `Raw Value` was not working properly.
+
+# 16.0.2
+
+## Fixes
+
+- Fix an issue with `FormBuilder` when trying to build a control with a nullable '?' data type.
+- Fix an issue with `FormGroup` that was not triggering the event `collectionChanges` when a control
+is removed.
+- Fix an issue with `FormGroup` and `FormArray` when trying to find a control with a nullable '?'
+data type.
+
+# 16.0.1
+
+## Fixes
+
+- Update the intl dependency version, because in flutter 3.10, 
+`flutter_localizations` depends on intl 0.18.0.
+
+# 16.0.0
+
+## Breaking Changes
+
+- Flutter >= 3.10 required for this version.
+
+## Fixes
+
+- Updated some documentation.
+- Expose validator classes to allow direct instantiation. 
+
+# 15.0.0
+
+## Breaking Changes
+
+- All validators have been changed to classes with `const` constructors.
+- The Asynchronous Validator is now a class from where any custom async validator can inherit.
+
+## Features
+
+- A new validator `Validators.delegate(...)` has been introduced to be used with a custom
+  validation function.
+- A new validator `Validators.delegateAsync(...)` has been introduced to be used with a custom
+  async validation functions.
+
+# 14.3.0
+
+- Fix the inkwell ripple effect in the **ReactiveDropdownField**.
+- Add some other minor fixes.
+
+# 14.2.0
+
+- Update intl to latest version 0.18.0.
+
 # 14.1.0
 
 ## Enhances