document the Discord name of a unicode emoji

[Mehgugs]

This issue has been discussed multiple times:
#671

The old stance on the names:

Our API only supports emoji in unicode characters as syntax. Colon based formatting is a client construct (clients convert colon based formatting into unicode characters) that our API doesn't understand or deal with, so it has no place in our API docs.

Guild stickers have changed this as their tags now accept a "Discord name of a unicode emoji".

If this is to kept as it is then we should really get a list of all these valid names -- especially since setting the tags to a name that doesn't exist clobbers the existing emoji -- or it could be changed to be the unicode character which would probably be a bit more consistent with other bits of the api like reactions. I'm ambivalent about whether it's changed or not, and I know now its been deployed it'll probably remain the same but just to cover all bases I thought I'd mention it.

I think a separate but related issue is the fact using "foo" as the tags (for example) sets the tag value to a value which the client wouldn't accept in the creation form (thanks for clarification advaith). It should probably return a 400 bad request?

[advaith1]

silently fails and clears the current valid tags value

this is incorrect, it successfully updates the value to foo

[Mehgugs]

How does this display?

[devsnek]

[Mehgugs]

Oh, when I tested it (setting various tag strings) it just clears the emoji off the top left corner when its not a name. How else could the tags be displayed unless it's simply not implemented yet?

[jkcailteux]

The API will accept any string up to 500 characters for the tags field. We use this to power autocomplete and suggestions. The client forces input to come from an emoji because its a set of commonly used names that a client could match on. Using unicode is not really an option here, as people do not type unicode emojis in your typical conversation in discord.

[Mehgugs]

according to night in the post I linked the colon short names are resolved to Unicode before hitting the api?

The API will accept any string up to 500 characters for the tags field.

why isn't that on the documentation page

[jkcailteux]

Ah that's right, we reduced it to 200, my mistake.