Merged
Conversation
Co-Authored-By: Piinks <[email protected]>
Co-Authored-By: Piinks <[email protected]>
Contributor
Author
|
Interface isn't updating analyze pre-submit check result. All green on cirrus, checked by @dnfield. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.

Description
This PR adds 2 code snippets for the FloatingActionButton class in the API docs. The first is a simple case, the second illustrates the use of the extended FAB constructor.
For your consideration dear reviewer...
I used the stateless widget template, and left the onPressed properties empty in these samples to focus on a simple example of constructing the FAB widget.
If changing this template to a stateful widget and implementing the popular counter example (or something similar) would be better to further exemplify this widget, share your thoughts below and I can modify it!
Related Issues
Ref: #21136
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?