discourse/app/assets/javascripts/admin/addon
Alan Guo Xiang Tan de5ca63eb5
UX: Allow a default value to be specified for enum properties (#26529)
Why this change?

For a `typed: objects` theme setting with an enum property, we are
adding a `default` key for `type: enum` fields which will be used
as the default value on the client side.

```
some_objects_setting:
  type: objects
  schema:
    name: field
    properties:
      enum_field:
        type: enum
        default: awesome
        choices:
          - nice
          - cool
          - awesome
```
2024-04-05 11:44:39 +08:00
..
adapters FIX: Ensure Theme#settings are instances of ThemeSettings (#26481) 2024-04-03 13:10:47 +08:00
components UX: Allow a default value to be specified for enum properties (#26529) 2024-04-05 11:44:39 +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 FIX: Ensure Theme#settings are instances of ThemeSettings (#26481) 2024-04-03 13:10:47 +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