discourse/app/assets/javascripts/select-kit/templates/components/topic-notifications-button.hbs

{{topic-notifications-options
  value=notificationLevel
  topic=topic
  onChange=(action "changeTopicNotificationLevel")
  options=(hash
    showFullTitle=showFullTitle
    placement=placement
  )
}}

{{#if appendReason}}
  <p class="reason">
    {{html-safe topic.details.notificationReasonText}}
  </p>
{{/if}}
Introduces select-kit * renames `select-box-kit` into `select-kit` * introduces `single-select` and `multi-select` as base components * introduces {{search-advanced-category-chooser}} as a better component for selecting category in advanced search * improves events handling in select-kit * recreates color selection inputs using {{multi-select}} and a custom {{selected-color}} component * replaces category-selector by a component using select-kit and based on multi-select * improves positioning of wrapper * removes the need for offscreen, and instead use `select-kit-header` as a base focus point for all select-kit based components * introduces a formal plugin api for select-kit based components * introduces a formal pattern for loading and updating select-kit based components: ``` computeValue() computeContent() mutateValue() ``` 2017-11-21 05:53:09 -05:00			`{{topic-notifications-options`
			`value=notificationLevel`
			`topic=topic`
DEV: select-kit 2 (#7998) This new iteration of select-kit focuses on following best principales and disallowing mutations inside select-kit components. A best effort has been made to avoid breaking changes, however if you content was a flat array, eg: ["foo", "bar"] You will need to set valueProperty=null and nameProperty=null on the component. Also almost every component should have an `onChange` handler now to decide what to do with the updated data. select-kit will not mutate your data by itself anymore 2020-02-03 08:22:14 -05:00			`onChange=(action "changeTopicNotificationLevel")`
			`options=(hash`
			`showFullTitle=showFullTitle`
FIX: muted was not working in topic timeline (#9021) 2020-02-21 15:32:58 -05:00			`placement=placement`
DEV: select-kit 2 (#7998) This new iteration of select-kit focuses on following best principales and disallowing mutations inside select-kit components. A best effort has been made to avoid breaking changes, however if you content was a flat array, eg: ["foo", "bar"] You will need to set valueProperty=null and nameProperty=null on the component. Also almost every component should have an `onChange` handler now to decide what to do with the updated data. select-kit will not mutate your data by itself anymore 2020-02-03 08:22:14 -05:00			`)`
			`}}`
FEATURE: uses select-box for topic-notifications-button component - Introduces ComponentConnector to use a component inside a widget - Use css to set size of components instead of properties - Smarted positionning - Style tweaks 2017-09-06 10:58:00 -04:00
			`{{#if appendReason}}`
			`<p class="reason">`
DEV: enforces ember-template-lint: no-triple-curlies (#9165) This pr replaces `{{{ }}}` usage by a {{html-safe}} helper. While it doesn't solve the underlying issue, it gives us a path forward without risking breaking too much existing behavior. Also introduces an htmlSafe computed macro: ``` import { htmlSafe } from "discourse/lib/computed"; htmlDescription: htmlSafe("description") ``` Overtime {{html-safe}} usage should be removed and moved to components properties or specialized components/helpers. 2020-03-11 04:23:10 -04:00			`{{html-safe topic.details.notificationReasonText}}`
FEATURE: uses select-box for topic-notifications-button component - Introduces ComponentConnector to use a component inside a widget - Use css to set size of components instead of properties - Smarted positionning - Style tweaks 2017-09-06 10:58:00 -04:00			`</p>`
			`{{/if}}`