Not sure if this is project goal or not. But I think a string parser that takes a string (for example I am cool :sunglasses: ) and returns a string that has :sunglasses: replaced with the actual emoji character would be really useful.

Most uses cases I can think of would not involve manipulating specific emojis in code. Even if it did, defining specific emoji characters required by the project as constants in the project instead of introducing a dependency would be simpler and easier. In that sense, above feature can add great value to this project I think .

If you think this would be useful, I can send a PR.

i write the code:

package 

import (
    "fmt"

    "github.com/enescakir/emoji"
)

func main() {
	fmt.Printf("Hello %v\n", emoji.WavingHand)
	fmt.Printf("I am %v from %v\n",
		emoji.ManTechnologist,
		emoji.FlagForTurkey,
	)
	fmt.Printf("Different skin tones.\n  default: %v light: %v dark: %v\n",
		emoji.ThumbsUp,
		emoji.OkHand.Tone(emoji.Light),
		emoji.CallMeHand.Tone(emoji.Dark),
	)
	fmt.Printf("Emojis with multiple skin tones.\n  both medium: %v light and dark: %v\n",
		emoji.PeopleHoldingHands.Tone(emoji.Medium),
		emoji.PeopleHoldingHands.Tone(emoji.Light, emoji.Dark),
	)
	fmt.Println(emoji.Parse("Emoji aliases are :sunglasses:"))
	emoji.Println("Use fmt wrappers :+1: with emoji support :tada:")
}

but the result is bad and i cant see the emoji's:

Hello 
I am  from 
Different skin tones.
 default:  light:  dark: 
Emojis with multiple skin tones.
 both medium:  light and dark: 
Emoji aliases are 
Use fmt wrappers  with emoji support

What should I do ?

I have Arch Linux Distro and i use zsh shell

• [x] add parser
• [x] generate emoji map with generator
• [x] add fmt methods
• [x] add unit tests to parser
• [x] add unit tests to fmt
• [x] add new feature to README

A set of optimisations related to allocations

Original
BenchmarkParse
BenchmarkParse-12    	 1446430	       799.4 ns/op	     288 B/op	      14 allocs/op

Remove redundant allocation
BenchmarkParse
BenchmarkParse-12    	 1482784	       719.3 ns/op	     256 B/op	      12 allocs/op

Use bytes.Buffer for matched
BenchmarkParse
BenchmarkParse-12    	 1745038	       638.7 ns/op	     184 B/op	       5 allocs/op

Preallocate required space
BenchmarkParse/static
BenchmarkParse/static-12         	 2146411	       536.6 ns/op	     144 B/op	       2 allocs/op

Reusable parser
BenchmarkParse/reusable
BenchmarkParse/reusable-12       	 2438487	       494.8 ns/op	      80 B/op	       1 allocs/op

Awesome package, thanks.

What do you think about adding a func Contains(input string) bool or func FindAll(input string) []string functions? Exposing how Parse finds aliases.

This would allow the caller to check for existence, or find all the aliases in a given input string.

Hi there, I found this module is quite interesting and easy to catch up.

Currently, I got into situation where I need to implement some kind of searching, but the search engine is not fully support utf8. So, it's may good for user to be able to convert ❤️ => :heart: and back, :heart: => ❤️

I'm also done a prototype for these implementation. My repo: https://github.com/liemle3893/emoji/commit/985fe954b73baf6614a2fd99d03779e49e07212d

It's cool if we can add this feature.

Regards.

I love this library but.... Unicode emoji 13.1 is released which made this library kinda out of date. Full list of newly added emojis can be found at https://www.unicode.org/emoji/charts-13.1/emoji-released.html or the new full list at here https://unicode.org/Public/emoji/13.1/emoji-test.txt