discourse/app
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
..
assets UX: Allow a default value to be specified for enum properties (#26529) 2024-04-05 11:44:39 +08:00
controllers DEV: early hints around_action -> after_action (#26423) 2024-04-04 14:37:44 +01:00
helpers DEV: Move chat service objects into core (#26506) 2024-04-04 10:57:41 -03:00
jobs DEV: Add skip_email_bulk_invites hidden site setting (#26430) 2024-03-29 13:22:00 -04:00
mailers FIX: Add higher read & open timeouts for group SMTP emails (#24593) 2023-11-28 15:32:59 +10:00
models DEV: Correctly pluralize error messages (#26469) 2024-04-04 15:02:09 +02:00
serializers FEATURE: Redesigned bookmark modal and menu (#23071) 2024-04-05 09:25:30 +10:00
services DEV: Move chat service objects into core (#26506) 2024-04-04 10:57:41 -03:00
views DEV: allow themes to render their own custom homepage (#26291) 2024-04-02 11:05:08 -04:00