Or maybe document it as dict on the doc string and type annotate it as MessagePayload

Or maybe document it as dict on the doc string and type annotate it as MessagePayload

MessagePayload is not documented and shouldn't be used as a type hint for a public attribute.

MessagePayload is not documented and shouldn't be used as a type hint for a public attribute.

It's done this way for interaction.data. If I should add MessagePayload to the docs, please tell me where to add it.

Do we really need to store the raw message data publicly? Interaction.data exists mainly because it's documented.

Do we really need to store the raw message data publicly? Interaction.data exists mainly because it's documented.

Are you suggesting something like message._data or message.__data?

I'm skeptical about the necessity of this attribute

This attribute is useful for handling transcripts and other cases where messages need to be stored. It doesn't matter to me if it's public or private, but I strongly recommend adding it. Users should be able to use it freely if they need to.

I see how having Message.data might be incorrect since data is not an attribute of the discord object. Maybe something like Message.payload or Message._payload or Message.raw_data might make more sense? Idk

I can see value to adding it, but only as undocumented private field.

In the on_message_edit(before, after) event, I’ve noticed that after._raw_data seems to retain outdated information. Specifically, it still shows the original content even after the message has been edited — similar to what’s available in on_message().

For example:

print(before._raw_data["content"])
print(after._raw_data["content"])

Both lines output the original message content, not the updated one.

However, if I manually fetch the message using after = await after.channel.fetch_message(after.id), then after._raw_data reflects the updated content correctly.

This suggests the issue may be related to caching. Can you confirm if you’re seeing the same behavior on your end, and whether _raw_data only updates in on_message_edit() when the message is explicitly fetched?

In the on_message_edit(before, after) event, I’ve noticed that after._raw_data seems to retain outdated information. Specifically, it still shows the original content even after the message has been edited — similar to what’s available in on_message().

For example:

print(before._raw_data["content"])

print(after._raw_data["content"])

Both lines output the original message content, not the updated one.

However, if I manually fetch the message using after = await after.channel.fetch_message(after.id), then after._raw_data reflects the updated content correctly.

This suggests the issue may be related to caching. Can you confirm if you’re seeing the same behavior on your end, and whether _raw_data only updates in on_message_edit() when the message is explicitly fetched?

This is because _raw_data is simply an attribute that is set in the __init__ of Message. This also explains why fetch does return the new data since that's never from cache.

The before and after parameter are Message objects from cache, except after is updated using the _update method. I guess the lib should also update the data in the mentioned method.

Please open a new issue if you're having problems.

Please open a new issue if you're having problems.

Sure