-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2022-05-25][$1000] Non-unique keys React warning. Possibly related to RenderHTML ? #8655
Comments
Triggered auto assignment to @JmillsExpensify ( |
Wow, interesting find. Posted the upwork job here for proposals: https://www.upwork.com/jobs/~01e7b5db822c3f7489 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Triggered auto assignment to @AndrewGable ( |
Where is this happening? Which screen? |
This is what needs to be debugged and solved. |
Doubling price to $500. |
|
Sorry, those logs are internal. You should be able to see these warnings on running the app on Android. |
Doubling the price to $1000. |
I was able to reproduce this problem when chat contains a message with two (or more) code blocks with the line break between them. For example, if you paste and send the following into the composer: The problem occurs inside the renderChildren function of const key = childTnode.nodeIndex; The problem is, Proposal: const key = `${childTnode.nodeIndex}_${n}` This ensures that every child always has a unique key Before: 22-05-02-14-02-57.mp4After: 22-05-02-14-08-49.mp4 |
Good catch @eVoloshchak. @eVoloshchak did you try upgrading the lib version to see if this issue still exists? |
Yup, tried upgrading to the latest version ( |
Ok, Thanks. I am fine with @eVoloshchak 's proposal. The next steps would be:
cc: @AndrewGable 🎀 👀 🎀 C+ reviewed |
Sounds good to me! |
📣 @eVoloshchak You have been assigned to this job by @AndrewGable! |
Submitted proposal on Upwork |
@eVoloshchak Hired and offer sent. @parasharrajat I've invited you to the job as well. |
Created the issue on |
@parasharrajat, it's been a week and the issue has no response from the maintainer. Should we wait more? |
I thought you created the PR as well. #8655 (comment). Also, please change the title to `Non-unique React keys warning when using dangerouslyDisableWhitespaceCollapsing |
Ok, will do that shortly |
Also, the maintainer is very active on the repo. He must be busy with some stuff but he will take a look. Try joining the discord and mention this issue. |
I earlier posted this issue https://expensify.slack.com/archives/C01GTK53T8Q/p1644402310844119. Am I eligible for reporting bonus? |
So I've received an answer from repo maintainer
I searched and found out that |
@eVoloshchak Could you share a video showing the effect of the new change? Please use a combination of messages in any chat and scroll to show those messages in the video. Thanks. |
Sure thing Web: cinnamon-20220515-1.mp4Android 22-05-15-21-25-45.mp4 |
Ok, looking good to me. Go ahead and create the PR. |
PR is up |
Looks like the linked PR made it to production last week. I'm mainly updating the issue title to account for the regression period. Payment later this week! |
Payment issued for @eVoloshchak. @parasharrajat I'll circle back on you tomorrow, as I just sent the offer. Thanks both! |
@parasharrajat is now covered, so I'm closing this out. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Actual Result:
Workaround:
Yes. This doesn't seem to affect app performance, but may indicate a serious problem.
Platform:
Where is this issue occurring?
Version Number:
Reproducible in staging?: Pretty sure the warning is silenced there.
Reproducible in production?: Pretty sure the warning is silenced there.
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: