discourse/app/assets/javascripts/admin/addon
Alan Guo Xiang Tan 0eda1c96f1
FIX: Ensure Theme#settings are instances of ThemeSettings (#26481)
Why this change?

Instead of dealing with a generic object for `Theme#settings`, we want
to always be dealing with `ThemeSettings` objects.` Previously, we
converted the generic objects to `ThemeSettings` objects in the theme's
adapter `afterFindAll` function. This is not correct because updating
or saving the theme individual reverted the `Theme#settings` back to an
array of generic object.

To fix this problem, the proper way with our REST models is to overwrite
the static `munge` method and create `ThemeSettings` instances there.
2024-04-03 13:10:47 +08:00
..
adapters FIX: Ensure Theme#settings are instances of ThemeSettings (#26481) 2024-04-03 13:10:47 +08:00
components UX: rename the word "Upgrade" to "Update" in the UI. (#26396) 2024-04-02 20:04:37 +05:30
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