addition of guild_id property in message obj returned by get channel Message , edit Message etc

[USERSATOSHI]

Intro

I think guild_id should be present at-least in the following endpoints:

GET /channels/{channel.id}/messages
GET /channels/{channel.id}/messages/{message.id}

would be grateful if it is also added in
PATCH method too

Reason

when using these endpoints , there are 2 main params, ( channelId and messageId)

and the object that is returned on success ( taking Guild Text Channel as example ) is like this:

{
  id: Snowflake,
  type: 0,
  content: 'hello?',
  channel_id: Snowflake,
  author: [Object],
  attachments: [],
  embeds: [],
  mentions: [],
  mention_roles: [],
  pinned: false,
  mention_everyone: false,
  tts: false,
  timestamp: "ISO8601 timestamp",
  edited_timestamp: null,
  flags: 0,
  components: []
}
// message data is fetched using a test bot with `message content intent` 

Work Around

because we never used guildId when using these endpoints,
we dont know , from which guild this message is from.

there are 2 work arounds:

Method 1:

cache the channel data in a hashMap with id as key
and when using GET /channels/{channel.id}/messages/{message.id} endpoint
get the channel data from cache and manually add the guild_id

issue

caching channels will need resources (which is fine on small scale )
and this requirement will increase as more channels are added to cache , when a bot joins a guild.
and ik discord says to cache the data provided in GUILD_CREATE event
but what if my bot doesn't need channel data at all

therefore
the only reason i have to cache channel data is for getting guild_id when fetching the message

Method 2:

if we are not caching channel data
we have to get guild_id property by fetching the channel data of the channel

which I think is not ideal here cause we are fetching whole channel data from discord api ,just to get guild_id

Conclusion

hence for the conclusion of this initial message, I think, having guild_id property on these endpoints ,will prevent unnecessary request and caching

PS:

if I missed something , I would be grateful if it's pointed out.

[wasdennnoch]

This has already been denied in the past: #912

[USERSATOSHI]

ok thx