Welcome Channel Emoji data should include "emoji_animated"

[almostSouji]

Description

Currently, the welcome screen data returns a flattened emoji structure with emoji_name and emoji_id. I suggest the addition of the (currently missing) emoji_animated property.

Why This is Needed

On the library level, we would like to construct a valid emoji instance with its corresponding methods from API data whenever possible. This data currently forces us to introduce a breaking change for our emoji structure(s) making the animated property nullable, if it arrives via welcome channel data.

Alternatives Considered

Not providing the animated data and causing me a headache and a breaking change in our library

Additional Details

I am aware that missing boolean can be interpreted as false, however tested this with a clearly animated emoji in our welcome screen, when retrieving data. No indicator as to if this emoji is animated or not was provided.

[FasterSpeeding]

On the library level, we would like to construct a valid emoji instance with its corresponding methods from API data whenever possible. This data currently forces us to introduce a breaking change for our emoji structure(s) making the animated property nullable, if it arrives via welcome channel data.

Are you not already handling the fact that "animated" is never included in the partial emoji object attached to MESSAGE_REACTION_REMOVE and MESSAGE_REACTION_REMOVE_EMOJI events in your emoji structure?

[almostSouji]

we retrieve the emoji (and with it the "animated" attribute) from the message payload associated with the reaction (in case of partial data for uncached messages we fetch the data to complete the partial structure before considering it valid)

unless I'm missing something there is no way to derive this in a similar fashion from an invite payload