Last 12 weeks ยท 0 commits
4 of 6 standards met
(Tried making a PR, but didn't have rights to push the branch) Overview The issue is that the victory-hand emoji default skin tone when used directly (โ๏ธ) does not match with the result from applying the skin tone to the victory-hand of another skin tone. Steps to reproduce Two ways of testing this: 1. The following test added to the code base will fail: (outside of code block render): t.is(skinTone('โ๐ป', 'none'), 'โ๏ธ'); 2. The following code (remember to init an npm project, and have : The result of step 2 is: Expected result The victory-hand default skin tone when pasted should be matched successfully against the 'none' applied skin tone. The ok-hand successfully matches using the same manner, where the victory-hand fails.
Repository: sindresorhus/skin-tone. Description: Change the skin tone of an emoji Stars: 62, Forks: 9. Primary language: JavaScript. Languages: JavaScript (88.8%), TypeScript (11.2%). License: MIT. Latest release: v4.0.0 (2y ago). Open PRs: 0, open issues: 0. Last activity: 5mo ago. Community health: 85%. Top contributors: sindresorhus, darkmark1991, BendingBender, markogresak, Richienb.
fixes #5 + adds support for multi component emojis (couples, detective, etc.) Changes 1. Update the check to see if emoji is skin tone compatible. This means that emoji has less than 3 modifiable components (3+ are families, there is no plans to support skin tone for those at this stage https://www.unicode.org/L2/L2020/20114-family-emoji-explor.pdf) For the several two-person family emojis additional check was added 2. Exclude character as it interferes with skin tone application https://unicode.org/reports/tr51/#composing_zwj_seq 3. Apply skin tone to the right of every modifiable character (couples, etc.) 4. Fix skin tone removal to remove from all modifiable characters (couples, etc.)