react-native-live-markdown
react-native-live-markdown copied to clipboard
[iOS & Android] Enable borderRadius in all mention types
Details
This PR adds support for borderRadius prop in mentions styles on iOS & Android
Related Issues
https://github.com/Expensify/App/issues/19299
Manual Tests
iOS & Android:
- Verify if singleline mentions have rounded edges
- Verify if multiline mentions have rounded edges only at the beginning and the end
- Verify mentions work correctly in blockquotes
Linked PRs
I fixed last known iOS issue in this commit - https://github.com/Expensify/react-native-live-markdown/pull/720/commits/28b6a13e75c87782d3fc54824d47329db9599fae
Before
After
Very much a nitpick, but when having a multiline mention starting bottom border radius and finish top, should not apply. Same issue for web
Na ios dzieją się rzeczy niestworzone :( Ale to też single - line
to jest 17.5, nie wiem czy to ma znaczenie
https://github.com/user-attachments/assets/2fc0da71-3841-4968-82b3-cbb8e1a62b8d
Very much a nitpick, but when having a multiline mention starting bottom border radius and finish top, should not apply. Same issue for web
We can try to fix it in a separate PR but I think we need to consult with the design team. I'll leave it as an open idea because it's not in the scope of this PR
Thanks for noticing!
- android, switching to single line breaks highlights :(
@jmusial should be fixed with the latest commit 🎉 https://github.com/Expensify/react-native-live-markdown/pull/720/commits/98dafdaaf9f2d9bd92df4dcd3e0c88222d481469
- android, Cursor not visible when within codeblock or mention
this is expected behaviour. We discussed it with the design team and there is no plan to support it in the near future
- android, Cursor not visible when within codeblock or mention
For the context, this was discussed on Slack: https://swmansion.slack.com/archives/C01GTK53T8Q/p1755699466781499
@tomekzaw @parasharrajat @Skalakid PR's ready for review 🎉
Please review it carefully and ask me any questions because the solution is quite complicated in a few places. If you think adding comments would be valuable let me know!
@parasharrajat kind bump :)
@parasharrajat can we get a final ✅? All comments have been answered!
BUG: Android: Cursor shows behind the background.
https://github.com/user-attachments/assets/8a8b9713-1d3f-4925-8c14-3424ef687a82
How do I build iOS build locally?
"@expensify/react-native-live-markdown": "git://github.com/Expensify/react-native-live-markdown#eb521b53582165d532918ca64b859210dc92bf09",
I installed the latest commit for this package on NewDot repo, and it worked for Android. But for iOS, the app is downloading the app from the remote cache.
We know about the issue and already reported it. It was put on hold at the time but we could revisit this idea in another issue/thread. Marking as unrelated for now!
But for iOS, the app is downloading the app from the remote cache.
@parasharrajat I'd probably remove the GITHUB_TOKEN entry from my .env to achieve that. This should be the easiest way to disable remote builds
~Nice idea. I will try that.~ Won't work
Now the builds are coming from S3.
Ok, so another quick one - I'd add a dummy log to some ~android~ iOS file to change the fingerprint. That should work
iOS looks good.
@war-in So we are not targeting this https://github.com/Expensify/react-native-live-markdown/pull/720#issuecomment-3602206125 here in this PR. Do we have approval for this from internal team?
@puneetlath What do you say?
Screenshots
:black_square_button: iOS / native
https://github.com/user-attachments/assets/2069491a-8ce7-493d-a1c8-5c1c528fbd0f
:black_square_button: MacOS / Chrome
:black_square_button: Android / native
https://github.com/user-attachments/assets/e4949c67-55f7-4a58-ba87-93ecd2891d67
@war-in So we are not targeting this https://github.com/Expensify/react-native-live-markdown/pull/720#issuecomment-3602206125 here in this PR. Do we have approval for this from internal team?
Do we have approval for this
@parasharrajat which this are you referring to here? approval for not including the fix in this PR or approval for handling this in another issue?
approval for not including the fix in this PR or approval for handling this in another issue?
Both are the same. We will have to fix that. The question is where. This Pr or another issue.
So we need to clarify that first before moving forward.
Sorry, the Slack link above doesn't work for me. Is that a bug this PR introduces? Or it already exists?
introduced by this.
@parasharrajat No, it's not. I downloaded the prod version from google play and this is how it behaves right now (see not-rounded corners) So this behaviour is not introduced by this PR
https://github.com/user-attachments/assets/7e9e80b7-c2f4-4b7f-84c9-eea2f8173c30
cc @puneetlath (you can enter the slack link by copying it and pasting in a slack conversation e.g. self dm)
Ah, I see. Thanks for correcting me. Then we are fine with this PR.