docs: Fix broken code example for ColorEffect #3382
Merged
Conversation
This file contains 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
ColorEffect in the docs is using an positional parameter for opacityFrom, but its actually a named parameter.
1 task
spydon
approved these changes
Dec 12, 2024
|
We're currently fixing the pipeline which broke when the new Flutter version was released, so this will be merged as soon as that is done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ColorEffect in the docs is using an positional parameter for opacityFrom, but its actually a named parameter.
Description
The docs example for ColorEffect is using a positional parameter instead of a named parameter, where the definition is using a named parameter.
Closes: #3383
Checklist
docsand added dartdoc comments with///.examplesordocs.Breaking Change?
Related Issues