-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
feat: Better support RTL languages #4310
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #4310 +/- ##
===========================================
- Coverage 10.80% 10.80% -0.01%
===========================================
Files 287 287
Lines 14202 14203 +1
===========================================
Hits 1534 1534
- Misses 12668 12669 +1
... and 2 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
final double topPadding; | ||
if (padding is EdgeInsetsDirectional) { | ||
topPadding = padding.bottom; | ||
} else if (padding is EdgeInsets) { | ||
topPadding = padding.bottom; | ||
} else { | ||
topPadding = 0.0; | ||
} |
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.
Cannot the point of this: there's only one place this method is called, and with a fat chance we need padding.bottom
anyway.
Maybe I'm missing something here.
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.
I would like to force EdgeInsetsDirectional
everywhere, but here indeed we have still strange behavior.
Before reverting this part, what do you think about forcing all EdgeInsets
to be EdgeInsetsDirectional
and enforcing this with a Lint rule?
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.
For the moment just make padding
an EdgeInsetsDirectional
, which will give you access to .bottom
and enable you to remove your tests.
Before reverting this part, what do you think about forcing all EdgeInsets to be EdgeInsetsDirectional and enforcing this with a Lint rule?
If it's easy to you to code and easy for us to maintain, why not.
But it's not a priority.
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.
I don't know why I've overengineered this part.
That should be better now.
For the Lint part, yes indeed, not a priority
You can test this PR on: https://app.waldo.com/applications/app-19d476740ba1bb36/sessions |
Hi everyone,
We often use left/right values, where we should instead pass start/end.
This PR is a simple find/replace.
Nothing interesting