This is a follow-up to:

• Use new API for determining which user reacted #4072
• api: Stop assuming fetched messages' reactions have deprecated user field #5773

In that round we switched how we process the reactions that come inside message objects. But in the server API, a similar transition also happened in reaction events. We should follow the transition there too.

This is a change it's useful to go ahead and make in this legacy app, because that will hasten the day when we can drop the user objects from reactions on the server, and because it should be a small change to make.

References

• #api design thread
• Use new API for determining which user reacted #4072
• api: Stop assuming fetched messages' reactions have deprecated user field #5773