-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix parseFloatingActionButtonLocation()
to work on desktop
#3496
Conversation
Reviewer's Guide by SourceryThis pull request refactors the File-Level Changes
Tips
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @FeodorFitsner - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟡 General issues: 3 issues found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
…v#3496) * Fix parseFloatingActionButtonLocation to work on desktop Fix flet-dev#3485 * Update changelog * make fabLocations const Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com> --------- Co-authored-by: TheEthicalBoy <[email protected]> Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Fix #3485
Summary by Sourcery
This pull request addresses a bug in the
parseFloatingActionButtonLocation()
function, ensuring it correctly maps string keys toFloatingActionButtonLocation
values, which resolves an issue with the function's compatibility on desktop platforms.parseFloatingActionButtonLocation()
to correctly map string keys toFloatingActionButtonLocation
values, ensuring compatibility on desktop platforms.