I believe this applies to almost all update events, but it's mainly been affecting me with channels, so I'll use those as an example.
From what I have gathered, when a ChannelUpdate event is received, revolt.js doesn't apply the key mappings. For example, when a channel's permissions are updated, the new Channel object looks like this:
rolePermissions here is the old data, role_permissions is the new data.
The result is that all data that revolt.js provides under a different key than what the API returns will not be updated and keep its initial value until the client reconnects.
What happened?
I believe this applies to almost all update events, but it's mainly been affecting me with channels, so I'll use those as an example.
From what I have gathered, when a ChannelUpdate event is received, revolt.js doesn't apply the key mappings. For example, when a channel's permissions are updated, the new Channel object looks like this:
rolePermissionshere is the old data,role_permissionsis the new data.The result is that all data that revolt.js provides under a different key than what the API returns will not be updated and keep its initial value until the client reconnects.