Alan Guo Xiang Tan 1cbc65ba79 DEV: Refactor GroupNotificationsButton into userPrivateMessages.group route (#21930) ... Why this change? Before this change, the `GroupNotificationsButton` is rendered in the template of `userPrivateMessages` route based on a conditional that checks if the `isGroup` property is true. However, the `isGroup` property is determined based on the child route that is rendered. However, this leads to "jankiness" in the UI because the `GroupNotificationsButton` will be rendered once the route is entered even if the model for the child route has not been resolved yet. What is the solution? In order to avoid this, we move the rendering of the `GroupNotificationsButton` into the template of the `userPrivateMessages.group` route and rely on the `in-element` helper to render it into the right spot in the template of the `userPrivateMessages` route.		2023-06-07 06:22:50 +08:00
..
assets	DEV: Refactor GroupNotificationsButton into userPrivateMessages.group route (#21930)	2023-06-07 06:22:50 +08:00
controllers	PERF: Preload user information when visiting user messages routes (#21929)	2023-06-05 19:24:22 +08:00
helpers	UX: Improve login required page (#20847)	2023-03-28 07:09:44 -05:00
jobs	FIX: consider users.created_at for inactive cleanup (#21688)	2023-05-23 13:41:23 +05:30
mailers	FIX: Likes received count in digest email (#21458)	2023-05-09 19:19:26 +02:00
models	FEATURE: Add API Scope for latest posts (#21913)	2023-06-05 09:04:34 -06:00
serializers	FIX: Hide delete button to invite as user are unable to delete anyway (#21884)	2023-06-06 12:24:19 +08:00
services	DEV: Allow plugins to hook into user preferences update process on the server (#21737)	2023-05-26 03:26:38 +03:00
views	FEATURE: Serve RTL versions of admin and plugins CSS bundles for RTL locales (#21876)	2023-06-01 05:27:11 +03:00