-
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
Migrate emoji skin tone list #19741
Merged
deetergp
merged 4 commits into
Expensify:main
from
szebniok:migrate-emoji-skin-tone-list
May 30, 2023
Merged
Migrate emoji skin tone list #19741
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 didn't replicate the
componentDidMount
/componentDidUpdate
functions, as I do not see the point of updating thehighlightedIndex
. We are later computing theisHiglighted
prop as logical "or", which already checks if the index matches the value ofprops.preferredSkinTone
.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.
@szebniok
componentDidUpdate
was introduced to solve this issue. I cannot find the exact reason whycomponentDidMount
was added but it might be required as well.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.
@sobitneupane I see. I cannot reproduce this issue on my PR, but I can do it on the original code with
componentDidMount
commented out.I don't know the original reasoning behind it, but the original code used the
props.preferredSkinTone
in two places—as an initial value ofstate.highlightedIndex
and inside therender
function. That's way it wasn't synced properly: when the skin tone was updated in another app, theprops.preferredSkinTone
changed and this line of codewas higlighting two items (with the updated
props.preferredSkinTone
and stalestate.highlightedIndex
. That's way thecomponentDidUpdate
was added to sync the changingprops.preferredSkinTone
.I don't see a reason to track the value of the
props.preferredSkinTone
inside our state, and choose to initially set thehighlightedIndex
tonull
.Thanks to your comment I found one minor bug introduced by my initial solution that I fixed in today's commit.
highlightedIndex
to theprops.preferredSkinTone
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.
Thanks for the detailed explanation @szebniok