-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
[Feature Enhancement] Improved Emoji Support #930
Conversation
@timaschew, @jthegedus can you take a look? |
@felangel thanks for your PR. The PR looks for good for me. It would be better if you just extend |
@jingsam can you give an example of how you'd like me to structure it? |
Just add missing emoijs in
|
The approach in the PR is to use the Update: I initially tried adding missing emojis to |
I thought it would be better just use Github Emoji API https://api.github.com/emojis |
@jingsam sounds good. I've updated the PR 👍 |
LGTM @felangel thanks for your PR. Ops, it seems that I don't have the permission to merge this PR. @jthegedus How do you think about it? |
@timaschew i believe it aligns with #779 but I just added missing emoji names and left the lookup as is. It’s still using https://api.github.com/emojis to map the emoji name to the unicode url. 👍 There’s still additional work needed to automate this lookup. Edit: @timaschew thoughts? |
+1 for this |
@anikethsaha if you're okay with the changes, I think we can merge this |
I think we should wait for couple of days and we can merge this. cc @timaschew @jingsam / |
I've revisited this PR and #779. |
Summary
The existing emoji plugin is lacking support for lots of emojis. I have modified the emoji plugin to source emoji data from https://raw.githubusercontent.com/liguoqinjim/github_emoji/master/github_all/README.md instead.
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
lib
directory.