-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Android/iOS - Code blocks are overflowing the app border #4733
Comments
Triggered auto assignment to @iwiznia ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
@iwiznia even reverting #4624 PR does not fix this issue. This issue is caused by upgrading the react-native-render-html. And I am tracking multiple issues caused by that here meliorence/react-native-render-html#514. |
I am investigating it. |
Wait, I am confused, that PR was deployed a while ago, was this broken before and we did not notice? |
Yes. this is the list of issues that were caused by that upgrade.
It is just due to one reason that a wrapper node was removed in the new lib version for optimizations which I think should be reverted. |
Update, I have discussed this issue with the Lib owner and we are going to revert this change behind the flag which should fix the issue. It should be done by weekend. |
@johnmlee101 @parasharrajat Should this issue still be considered a deploy blocker? Update: Just as a double check, I just retested this and it's still happening |
I think is happening on prod as well. so No deploy blocker. Update:
|
Confirmed this is also happening in prod too in iOS. Removing the deploy blocker label. |
Update: Planned: I will revert the code to the old version before the upgrade of RNRH and try to observe why it was working. Hoping this will help. |
Did you have a revert PR to link @parasharrajat ? Or any update here? |
Sure, going to push this forward. |
IMO, POC looks good but it comes down to the RN team, what if they disapprove of the approach? Meanwhile, I am discussing this internally https://expensify.slack.com/archives/C02NK2DQWUX/p1693327604262399 . You also have access to that so feel free to participate. |
hey @azimgd - in response to this question: Am I eligible for a compensation here? |
https://www.upwork.com/jobs/~0168597a8302cbc823 - job post here @azimgd |
Thanks Zanny, I won't accept the "offer for a fair amount" given the requirements change and will continue working on this. Thanks. |
After we spoke in DM @azimgd did agree to the payment offered. We have discussed this issue internally As this job has been open and unresolved for a really long time, we're exploring new ways to solve this. We really appreciate all the work on it so far but because this is really old and convoluted, we're going to open a new job as a clean slate. |
Payment summary
|
I would be happy to be assigned to the new job till this issue is fixed. I don't expect any payment ad V+ until this is resolved. |
Thank you @parasharrajat. As discussed in DM with @azimgd - he will be paid for his effort via ND. @JmillsExpensify I have sent you Azim's email, please can you confirm the payment has happened? I am then going to close this issue as we will tackle this in a new issue as the current issue is very old and convoluted. Thank you. |
Closing this out in this issue and working on this in another issue to move ahead here. @azimgd we discussed this and your payment in DM. If you're having any problems with the ND payment, please can you ping @JmillsExpensify who owns the payment of these in NewDot, please! Thank you. |
$8,000 payment approved for @azimgd based on BZ summary. |
I've been involved in this project for some time, reviewing several iterations and participating in many pull requests. While we haven't reached a final solution yet, my efforts have helped along the way. Looks like the latest project went stale and it may not be a top priority at the moment. However, given the time and effort I've invested, I believe this is the appropriate time to request the C+ payment. I will continue reviewing the new task #27913 @zanyrenney Could you please finalize the C+ payment and update the payment summary? |
@zanyrenney , 👀 above plz |
@mallenexpensify @zanyrenney Thanks for the input. But there is no uncertainty about my contributions on this issue. I have been active C+ on this issue since the start and reviewed each PR linked to this issue. I believe that I don't have to suggest compensation here, it should same as the contributor as per the policy. #4733 (comment) Here I requested to hold the payment as I wanted to continue reviewing the planned work by cubuspl42. Those PRs also have been reviewed so we are way past those steps now. Then I followed the new issue #27913 and also reviewed all things related to it. I am still active on this issue. But it has stalled now and I don't see any plan ahead. Thus I am requesting the payment now. If you can help push forward the new issue and help us draw a timeline, I'm happy to wait for a couple of months. |
Fair. Discussing internally. |
Hey @parasharrajat as you're working on the issue this morphed into here -- #27913 the compensation would come once that is wrapped up: Can you pleas to revisit once the linked/associated issue gets fixed? Thanks! |
@zanyrenney Can you please update the payment summary here? |
payment summary$8,000 due to @parasharrajat paid via ND requests |
payment requested as per #4733 (comment) |
$8,000 approved for @parasharrajat |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Issue is failing #4624 (CC @parasharrajat)
Action Performed:
Expected Result:
Code block should be displayed in the area of the conversation.
Actual Result:
Code block is partially visible because is overflowing the app border.
Platform:
Where is this issue occurring?
Version Number: 1.0.86-2
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: