discourse/app/assets/javascripts/admin/addon/templates/customize-themes-show-schema.hbs

<div class="customize-themes-show-schema__header row">
  <LinkTo
    @route="adminCustomizeThemes.show"
    @model={{@model.theme.id}}
    class="btn-transparent customize-themes-show-schema__back"
  >
    {{d-icon "arrow-left"}}{{@model.theme.name}}
  </LinkTo>
  <h2>
    {{i18n
      "admin.customize.theme.schema.title"
      (hash name=@model.setting.setting)
    }}
  </h2>
</div>

<SchemaThemeSetting::Editor
  @themeId={{@model.theme.id}}
  @setting={{@model.setting}}
/>
UX: First pass styling experimental objects typed setting editor (#26194) Why this change? This is a first pass at styling the editor for creating/editing/updating an objects typed theme setting. Only the desktop view is being considered at the current moment. The objects typed theme setting is still behind a feature flag at this moment so there is no need for us to get the styling perfect. The purpose of this PR is to get us to a state which we can quickly iterate with a designer on. 2024-03-18 10:03:30 +08:00			`<div class="customize-themes-show-schema__header row">`
UX: adjust objects editor styles for full page layout (#26265) 2024-03-20 15:55:52 -04:00			`<LinkTo`
			`@route="adminCustomizeThemes.show"`
			`@model={{@model.theme.id}}`
			`class="btn-transparent customize-themes-show-schema__back"`
			`>`
			`{{d-icon "arrow-left"}}{{@model.theme.name}}`
			`</LinkTo>`
UX: First pass styling experimental objects typed setting editor (#26194) Why this change? This is a first pass at styling the editor for creating/editing/updating an objects typed theme setting. Only the desktop view is being considered at the current moment. The objects typed theme setting is still behind a feature flag at this moment so there is no need for us to get the styling perfect. The purpose of this PR is to get us to a state which we can quickly iterate with a designer on. 2024-03-18 10:03:30 +08:00			`<h2>`
			`{{i18n`
			`"admin.customize.theme.schema.title"`
			`(hash name=@model.setting.setting)`
			`}}`
			`</h2>`
			`</div>`

DEV: Open theme settings objects editor from admin customize theme page (#26006) Why this change? The `/admin/customize/themes/:id/schema/name` route is a work in progress but we want to be able to start navigating to it from the `/admin/customize/themes/:id` route. What does this change do? 1. Move `adminCustomizeThemes.schema` to a child route of `adminCustomizeThemes.show`. This is because we need the model from the parent route and if it isn't a child route we end up having to load the theme model again from the server. 1. Add the `objects_schema` attribute to `ThemeSettingsSerializer` 1. Refactor `SiteSettingComponent` to be able to render a button so that we don't have to hardcode the button rendering into the `SiteSettings::String` component 2024-03-06 08:24:29 +08:00			`<SchemaThemeSetting::Editor`
DEV: Add save button to editing typed objects theme setting route (#26133) Why this change? This is still a work in progress but allows objects type theme setting to be saved. 2024-03-13 06:52:46 +08:00			`@themeId={{@model.theme.id}}`
			`@setting={{@model.setting}}`
DEV: Open theme settings objects editor from admin customize theme page (#26006) Why this change? The `/admin/customize/themes/:id/schema/name` route is a work in progress but we want to be able to start navigating to it from the `/admin/customize/themes/:id` route. What does this change do? 1. Move `adminCustomizeThemes.schema` to a child route of `adminCustomizeThemes.show`. This is because we need the model from the parent route and if it isn't a child route we end up having to load the theme model again from the server. 1. Add the `objects_schema` attribute to `ThemeSettingsSerializer` 1. Refactor `SiteSettingComponent` to be able to render a button so that we don't have to hardcode the button rendering into the `SiteSettings::String` component 2024-03-06 08:24:29 +08:00			`/>`