Alan Guo Xiang Tan 476d91d233 DEV: Change category type to categories type for theme object schema (#26339) ... Why this change? This is a follow-up to 86b2e3aa3e. Basically, we want to allow people to select more than 1 category as well. What does this change do? 1. Change `type: category` to `type: categories` and support `min` and `max` validations for `type: categories`. 2. Fix the `<SchemaThemeSetting::Types::Categories>` component to support the `min` and `max` validations and switch it to use the `<CategorySelector>` component instead of the `<CategoryChooser>` component which only supports selecting one category.		2024-03-27 10:54:30 +08:00
..
adapters	DEV: Allow typed objects theme settings to be saved via settings editor (#26100)	2024-03-11 08:42:12 +08:00
components	DEV: Change category type to categories type for theme object schema (#26339)	2024-03-27 10:54:30 +08:00
controllers	FEATURE: More flexible admin plugin config nav definition (#26254)	2024-03-21 13:42:06 +10:00
helpers	DEV: replace registerUnbound usage with default exports (#23802)	2023-10-19 14:28:25 +01:00
lib	DEV: Rename I18n imports to discourse-i18n (#23915)	2023-10-18 11:07:09 +01:00
mixins	DEV: Add save button to editing typed objects theme setting route (#26133)	2024-03-13 06:52:46 +08:00
models	DEV: Load theme objects typed setting metadata when routing to editor (#26354)	2024-03-26 14:02:05 +08:00
routes	DEV: Load theme objects typed setting metadata when routing to editor (#26354)	2024-03-26 14:02:05 +08:00
services	FEATURE: More flexible admin plugin config nav definition (#26254)	2024-03-21 13:42:06 +10:00
templates	FEATURE: More flexible admin plugin config nav definition (#26254)	2024-03-21 13:42:06 +10:00