discourse/app/assets/javascripts/admin/addon/templates/plugins-show-settings.hbs

<DBreadcrumbsItem
  @path="/admin/plugins/{{@model.plugin.name}}/settings"
  @label={{i18n "admin.plugins.change_settings_short"}}
/>

<div
  class="content-body admin-plugin-config-area__settings admin-detail pull-left"
>
  <AdminPluginFilteredSiteSettings
    @initialFilter={{@model.initialFilter}}
    @plugin={{@model.plugin}}
    @settings={{@model.settings}}
    @onFilterChanged={{this.filterChanged}}
  />
</div>
DEV: A different approach to breadcrumbs (#27365) Really fully authored by Jarek, I only made the PR :) The `DBreadcrumbItem` and `DBreadcrumbContainer` components introduced in 1239178f496cba5d864adb7c118b17902b8b72dc have some limitations, mainly that the container has no awareness of its items, so nothing that requires positional knowledge can be used. This is needed to use `aria-current` on the last breadcrumb item, see https://www.w3.org/WAI/ARIA/apg/patterns/breadcrumb/examples/breadcrumb/. We change `DBreadcrumbItem` to always be a link, removing the need for `LinkTo`. Then, we introduce a service to keep track of containers and items (since all items are rendered into all containers) and make the item itself responsible for registering to the service, and introduce the needed `aria-current` behaviour. --------- Co-authored-by: Jarek Radosz <jradosz@gmail.com> 2024-06-07 09:31:46 +08:00			`<DBreadcrumbsItem`
DEV: Simplify breadcrumbs by using `path` arg (#27744) Example: ```hbs <DBreadcrumbItem @path="/admin/plugins/{{@plugin.name}}" @label={{@plugin.nameTitleized}} /> ``` Using `@path` instead of `@route`+`@model` combo makes it impossible to pass temporarily unresolvable routes. This fixes a bug with navigating from a model-based route to a parent route. 2024-07-08 23:55:03 +08:00			`@path="/admin/plugins/{{@model.plugin.name}}/settings"`
DEV: A different approach to breadcrumbs (#27365) Really fully authored by Jarek, I only made the PR :) The `DBreadcrumbItem` and `DBreadcrumbContainer` components introduced in 1239178f496cba5d864adb7c118b17902b8b72dc have some limitations, mainly that the container has no awareness of its items, so nothing that requires positional knowledge can be used. This is needed to use `aria-current` on the last breadcrumb item, see https://www.w3.org/WAI/ARIA/apg/patterns/breadcrumb/examples/breadcrumb/. We change `DBreadcrumbItem` to always be a link, removing the need for `LinkTo`. Then, we introduce a service to keep track of containers and items (since all items are rendered into all containers) and make the item itself responsible for registering to the service, and introduce the needed `aria-current` behaviour. --------- Co-authored-by: Jarek Radosz <jradosz@gmail.com> 2024-06-07 09:31:46 +08:00			`@label={{i18n "admin.plugins.change_settings_short"}}`
			`/>`
FEATURE: Introduce DBreadcrumbs components (#27049) This commit introduces the following components: * DBreadcrumbsContainer - The wrapper template-only component, which renders all DBreadcrumbsItem components on the page. * DBreadcrumbsItem - The component that registers a LinkTo for the breadcrumb trail. The breadcrumb > trail > will show based on the order these items are rendered on the page. * BreadcrumbsService - Manages the DBreadcrumbsContainer elements on the page via DBreadcrumbsContainerModifier. * DBreadcrumbsContainerModifier - Handles registering DBreadcrumbsContainer elements with the BreadcrumbsService and deregistering them. For now, we will only use these breadcrumbs in the admin section of Discourse, and this initial commit only uses them in admin/plugins. This is heavily based off of https://github.com/Bagaar/ember-breadcrumbs, but will be further modified for our needs. 2024-05-20 12:25:54 +08:00
FEATURE: Allow site settings to be edited throughout admin UI (#26154) This commit makes it so the site settings filter controls and the list of settings input editors themselves can be used elsewhere in the admin UI outside of /admin/site_settings This allows us to provide more targeted groups of settings in different UI areas where it makes sense to provide them, such as on plugin pages. You could open a single page for a plugin where you can see information about that plugin, change settings, and configure it with custom UIs in the one place. In future we will do this in "config areas" for other parts of the admin UI. 2024-03-18 06:50:39 +08:00			`<div`
			`class="content-body admin-plugin-config-area__settings admin-detail pull-left"`
			`>`
			`<AdminPluginFilteredSiteSettings`
			`@initialFilter={{@model.initialFilter}}`
			`@plugin={{@model.plugin}}`
			`@settings={{@model.settings}}`
			`@onFilterChanged={{this.filterChanged}}`
			`/>`
			`</div>`