Extract all pieces of local user-related state to APIAccess subcomponent
#35415
+240
−183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RFC. Soft prereq for #34494.
This is something I've asked to be done for a long time. Relevant because I've complained about
APIAccessgetting bloated with every addition of a new piece of user-local state: friends, blocks, and now favourite beatmaps.LocalUseris left mostly unchanged due to sheer number of usages, butFriends/Blocksget the full treatment.It's just so messy managing all this inside
APIAccessnext to everything else, IMO.dfa8d4f (a bug on master, albeit of little consequence) demonstrates why I want this change.