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
..
images
javascripts	DEV: Refactor GroupNotificationsButton into userPrivateMessages.group route (#21930)	2023-06-07 06:22:50 +08:00
stylesheets	DEV: Refactor GroupNotificationsButton into userPrivateMessages.group route (#21930)	2023-06-07 06:22:50 +08:00