Martin Brennan 38742bc208
FIX: Wrong scope used for notification levels user serializer (#13039)
This is a recent regression introduced by https://github.com/discourse/discourse/pull/12937 which makes it so that when looking at a user profile that is not your own, specifically the category and tag notification settings, you would see your own settings instead of the target user. This is only a problem for admins because regular users cannot see these details for other users.

The issue was that we were using `scope` in the serializer, which refers to the current user, rather than using a scope for the target user via `Guardian.new(user)`.

However, on further inspection the `notification_levels_for` method for `TagUser` and `CategoryUser` did not actually need to be accepting an instance of Guardian, all that it was using it for was to check guardian.anonymous? which is just a fancy way of saying user.blank?. Changed this method to just accept a user instead and send the user in from the serializer.
2021-05-14 09:45:14 +10:00
..
2020-04-28 15:59:39 +05:30
2019-11-29 15:49:08 +00:00
2020-08-21 11:36:53 +08:00
2020-10-27 23:42:33 +05:30
2019-10-21 12:08:20 +01:00
2019-05-13 15:24:24 +01:00
2020-05-05 13:46:57 +10:00
2021-04-14 10:27:07 +03:00
2020-10-27 23:42:33 +05:30
2020-10-27 23:42:33 +05:30
2020-04-28 15:59:39 +05:30
2020-10-27 23:42:33 +05:30
2019-10-17 16:58:22 +11:00
2020-10-27 23:42:33 +05:30