Description

Reduced the amount of information sent when a participant either changes his appearance or status on a board – as mention in #4217.

Before a PARTICIPANT_UPDATED event was published containing all information (account and board session). This is now split into two:

• Account (ID, name, avatar, account type) – for now remained PARTICIPANT_UPDATED
• Board Session (connected, banned, etc.) – named PARTICIPANT_SESSION_UPDATED

Changelog

• Simplified DB call, since we just need the session IDs and not all data per entry
• Updated the UpdatedUser function to publish only a dto.User to realtime
• Updated the dto.BoardSession – removing the whole account data and just leaving the id for identification
• Simplified the UpdatedSession function, since we only need to publish a dto.BoardSession to realtime for one board going foreward
• Adapted tests to use new dto.BoardSession

Next Steps

Since this is a breaking change, we need to modify the frontend to accommodate the backend changes. From my perspective either use this branch directly to make changes to the frontend or create a branch based on this one.

After the frontend changes are done, all tests should work again. For now, since I did not change the frontend, those tests obviously fail.

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• The light- and dark-theme are both supported and tested
• The design was implemented and is responsive for all devices and screen sizes
• The application was tested in the most commonly used browsers (e.g. Chrome, Firefox, Safari)