Seems like the examples are only demonstrating how to print the emojis to the console, which is super inconsequential. How do you include the elements in the actual UI of the app? Seems like the Emoji type is not a Widget type, so I can't just pass it into the tree. Any clarification would be great.

It would be great if this library coud make the app use the Unicode emoji as default emoji, like this one : https://unicode.org/emoji/charts/full-emoji-list.html#1f600

Or maybe there is already a way to use those emojis as default when we display a Text widget for instance ?

Implementation

• Reformat codes by dart-fmt
• Split code into files (emoji_const.dart, emoji_util.dart, emojis.dart)
• Fix Emoji.byShortName
• Add Emoji.emojinize, Emoji.demojinize
• Add test code
• Update example/main.dart
• Update README

Check

• flutter analyze passed
• flutter test passed

Thank you for creating this package, I am using it to find emojis by name :)

One issue I stumbled across is that if the name is invalid, then an exception will be raised.

Thus

final emoji = Emoji.byName('bla');

will raise the exception:

Bad state: No element
dart:collection                      ListMixin.firstWhere

This can be easily fixed by supplying an orElse parameter to firstWhere:

/// Returns Emoji by [name]
factory Emoji.byName(String name){
    name = name.toLowerCase(); // todo: searchable name
    return _emojis.firstWhere((Emoji emoji) => emoji.name == name, orElse: () => null);
}

You also may wish to update byChar, byShortName etc.

Seems like in each category there are some emojis that aren't displayed properly and the emoji is replaced with a rectangle. This happens for each emoji category: Is this a known issue?

I want to suggest that some of the core classes in this library be slightly restructured to more closely mimic Flutter's Icon and IconData classes.

For example, the current API looks like this:

Emoji womanBlond = Emoji.byChar(Emojis.womanBlondHair);
print(womanBlond)
// 👧

The proposed API would look like:

Emoji womanBlond = Emoji(Emojis.womanBlondHair);

This library would then have 3 core classes:

/// Houses majority of the API that developers touch. All of your existing methods would stay here
/// plus new ones like `emojize` and `demojize`.
class Emoji {}

/// Empty class but for its many constants representing all of the emojis. This would be most similar
/// to your existing `_emojis` list.
class Emojis {
  ...
  static const womanBlondHair = EmojiData('\u{1F471}\u{200D}\u{2640}\u{FE0F}', shortName: 'blond-haired_woman', emojiGroup: EmojiGroup.peopleBody, emojiSubGroup: EmojiSubGroup.person, keywords: [...])
  ...
}

/// Class to hold instance data for a specific emoji. Thousands of these would exist to populate
/// the `Emojis` container class.
class EmojiData {
  final String code;
  final String shortName;
  final EmojiGroup emojiGroup;
  final EmojiSubGroup emojiSubGroup;
  final List<String> keywords;
}

If this seems reasonable, I would be happy to put together a PR. I have lots of emoji functionality I would love to contribute to your library, but wanted to float my ideas for a refactor before diving right in and making changes.

Thanks again for creating emojis -- you have a lot of very cool functionality here!