Vinícius Hoyer

I'm very pro this idea, in fact, if we are gonna support the json format, maybe the template can come in array format? ```json { "template": [ "{{emoji}} {{#if scope.length}}[{{scope}}]{{/if}}...

 also, you see this area I highlighed in red? This area has a space of `0.5rem`, if we are adding another area to the card, I think it is...

I also don't have access to comment or see comments on the vercel preview

> 2\. Should we persist pins somewhere? What's the utility of pinning things if they get lost after a page reload? Oh, are we not persisting this, it totally passed...

I thought about only showing the icon on hover, but that also is bad UX because it provide no affordance to this action, that's why I suggested that we muted...

yeah, well, the codepoint in emojipedia is shorter, so I guess it's wise that we'd prefer this one, I vote we change, but I'm also not completely aware of what...

IMHO, backwards compatibility (bwc) should be included in the original commit that added the new syntax, but I can kinda see why one would want to have this if something...

you have a good point @tristan-cottam, whenever I have to use the :boom: I usually drop any other "intention emojis", as I see the fact that something is a breaking...

Yeah, I think that business logic is very much the same use case, specially when you consider the discussion around adding the business logic emoji and also that the "business"...

there already is an issue for improving the searchability of emojis by using this method of "related emojis", https://github.com/carloscuesta/gitmoji/issues/924 I think it would be great to have your contribution there...