You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
about: You want to report something that is wrong or missing from the documentation.
4
+
labels: documentation
5
+
6
+
---
7
+
8
+
### Describe the change you would like to see
9
+
<!-- A clear and concise description of the bug or documentation you feel is missing.
10
+
For example: The Technical Reference does not include information about the FormBuilderFilterChip widget. -->
11
+
12
+
### How would the suggested change make the documentation more useful?
13
+
<!-- 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.
14
+
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). -->
15
+
16
+
### Additional context
17
+
<!-- Add any other context about your feedback here.
18
+
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. -->
<!-- Required: this reference (one or many) will be closed upon merge. Ideally it has the acceptance criteria and designs for features or fixes related to the work in this Pull Request -->
6
+
7
+
Connected to #???
8
+
9
+
<!-- Optional: other issues or pull requests related to this, but merging should not close it -->
10
+
11
+
## Testing and Review Notes
12
+
13
+
<!-- Required: steps to take to confirm this works as expected or other guidance for code, UX, and any other reviewers -->
14
+
15
+
## Screenshots or Videos
16
+
17
+
<!-- Optional: to clearly demonstrate the feature or fix to help with testing and reviews -->
18
+
19
+
## To Do
20
+
21
+
<!-- Add “WIP” to the PR title if pushing up but not complete nor ready for review -->
22
+
-[ ] double check the original issue to confirm it is fully satisfied
23
+
-[ ] add testing notes and screenshots in PR description to help guide reviewers
24
+
-[ ] request the "UX" team perform a design review (if/when applicable)
0 commit comments