Tom Wright

Thanks for all the feedback here. I am currently reworking the encoding/decoding of all supported formats here: https://github.com/TomWright/dasel/pull/289 Once that is done I will use have a crack at implementing...

The difficulty around this is that maps in go aren't strictly sorted, meaning I'll have to largely rethink the storage layer. I've had some ideas in this area but haven't...

The idea there is correct, but dasel unmarshals into the actual data structure, i.e. a `map[string]interface{}`. I need to create a value wrapper that allows me to store things like...

See my draft PR here for information on where we're at with this request: https://github.com/TomWright/dasel/pull/289

Closing this as --format isn't supported in v2. When I implement a relatable feature there I will include this functionality.

Related to: - https://github.com/discord/discord-api-docs/issues/6763 - https://github.com/discord/discord-api-docs/issues/6609 It seems as though a numeric response for snowflake types [is intended](https://github.com/discord/discord-api-docs/issues/6609#issuecomment-1885812390). A better fix may be to have a `Snowflake` type that deals...

Related to https://github.com/discord/discord-api-docs/issues/6609.

> This will never happen with IDs that come from Discord. It's possible that discordgo is requesting this data, but as I understand it the data is coming from discord...

@lsdimagine I wish I could give you more information on that. I'm developing a bot for a discord server that I don't own and this activity exists there

This is a known limitation right now. I'll keep this issue open in the meantime while I work on a fix.