discourse/app
Ted Johansson fdcb429145
FIX: Handle null values in category settings relative time pickers (#20552)
As reported on Meta, the relative time pickers for configuring slow-mode and auto-close durations in category settings are initially showing a "mins" option, which then disappears after you select any other timescale.

Our `RelativeTimePicker` component wasn't equipped to handle `null` values as the initial input. This caused it to go into a code path that set the selected timescale to "mins", even if that is not an allowed option.

There are two things being done here:

1. Add support for `null` input values to `RelativeTimePicker`. This fixes the auto-close setting.
2. Allow minutes for the slow-mode setting. (The user in Meta mentioned they usually set 15-30 minutes to cool down hot topics.
2023-03-07 11:05:13 +08:00
..
assets FIX: Handle null values in category settings relative time pickers (#20552) 2023-03-07 11:05:13 +08:00
controllers DEV: Experimental /filter route to filter through topics (#20494) 2023-03-03 09:46:21 +08:00
helpers DEV: Replace #pluck_first freedom patch with AR #pick in core (#19893) 2023-02-13 12:39:45 +08:00
jobs UX/DEV: Review queue redesign fixes (#20239) 2023-03-02 16:40:53 +01:00
mailers DEV: Replace #pluck_first freedom patch with AR #pick in core (#19893) 2023-02-13 12:39:45 +08:00
models FEATURE: allow external links in custom sidebar sections (#20503) 2023-03-07 11:47:18 +11:00
serializers FIX: Incorrect topic tracking state count when a new category is created (#20506) 2023-03-06 10:13:10 +08:00
services UX: Skip applying link-type watched words to user custom fields (#20465) 2023-03-01 10:43:34 +08:00
views SECURITY: Show only visible tags in metadata 2023-02-23 17:22:20 +01:00