Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove RoomManager, centralise listing management to lounge #31866

Open
wants to merge 21 commits into
base: master
Choose a base branch
from

Conversation

smoogipoo
Copy link
Contributor

@smoogipoo smoogipoo commented Feb 12, 2025

This is the removal of RoomManager that I hinted towards in the PR above. I would also like to remove TestRoomRequestsHandler to simplify further, but I don't think it's immediately necessary.

Of particular importance:

  • The lounge handles & stores the rooms locally (in its local RoomsContainer).
  • The playlists room subscreen updates its Room directly with its associated PlaylistsRoomUpdater.
  • RoomManager used to have a method to ignore rooms that threw an exception while updating. This is a legacy thing that I think we should no longer keep around.

smoogipoo and others added 21 commits January 17, 2025 18:12
Relevant functionality has been removed from `RoomManager` in the
process.
In particular, when the exception is:
`AggregateException { AggregateException { HubException } }`,
then the existing code will only unwrap the first aggregate exception.

The overlay's code was copied from the extension so both have been
adjusted here.
I believe once upon a time the `SelectedRoom` bindable used to be bound
to `RoomManager.JoinedRoom` or similar. But now it's effectively private
to the lounge subscreen and so a lease is unnecessary.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants