discourse/app/assets/javascripts/select-kit/templates/components/multi-select/multi-select-header.hbs

<div class="choices">
  {{#each selectedContent as |item|}}
    {{component selectKit.options.selectedNameComponent
      tabindex=tabindex
      item=item
      selectKit=selectKit
    }}
  {{/each}}

  <div class="choice input-wrapper">
    {{component selectKit.options.filterComponent
      selectKit=selectKit
    }}
  </div>
</div>
FIX: various sizing issues on select-kit 2017-11-26 11:21:39 -05:00			`<div class="choices">`
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			`{{#each selectedContent as \|item\|}}`
			`{{component selectKit.options.selectedNameComponent`
			`tabindex=tabindex`
			`item=item`
			`selectKit=selectKit`
			`}}`
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			`{{/each}}`
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
			`<div class="choice input-wrapper">`
			`{{component selectKit.options.filterComponent`
			`selectKit=selectKit`
			`}}`
			`</div>`
FIX: various sizing issues on select-kit 2017-11-26 11:21:39 -05:00			`</div>`