FIX: when category or tag is muted, update user (PR #9456)

Currently, when category or tag is muted, only after the hard refresh, these new muted categories are really muted. Without a hard refresh, you will still receive “new topic” messages.

Therefore, when tag or category is muted, we should update the user object right away.


Because this is a controller I would prefer if you used this.currentUser to get the user rather than the User singleton. Saves an import and makes testing easier due to dependency injection.

Is there a case where this wouldn’t be this? Not clear why you’d need to use the singleton here.

@eviltrout thank you for your comments, you were right, fixed :slight_smile: