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

{{#unless isHidden}}
  {{component selectKit.options.headerComponent
    tabindex=tabindex
    value=value
    selectedContent=selectedContent
    selectKit=selectKit
  }}

  {{#select-kit/select-kit-body selectKit=selectKit}}
    {{#unless selectKit.isLoading}}
      {{#if selectKit.filter}}
      {{#if selectKit.hasNoContent}}
        <span class="no-content">
          {{i18n "select_kit.no_content"}}
        </span>
      {{/if}}
      {{/if}}

      {{#each collections as |collection|}}
        {{component (component-for-collection collection.identifier selectKit)
          collection=collection
          selectKit=selectKit
          value=value
        }}
      {{/each}}
    {{else}}
      <span class="is-loading">
        {{loading-spinner size="small"}}
      </span>
    {{/unless}}
  {{/select-kit/select-kit-body}}

  <div class="select-kit-wrapper"></div>
{{/unless}}
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 21:22:14 +08:00			`{{#unless isHidden}}`
			`{{component selectKit.options.headerComponent`
			`tabindex=tabindex`
			`value=value`
			`selectedContent=selectedContent`
			`selectKit=selectKit`
[WIP] select-box-kit refactoring 2017-10-20 03:51:08 +08:00			`}}`

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 21:22:14 +08:00			`{{#select-kit/select-kit-body selectKit=selectKit}}`
			`{{#unless selectKit.isLoading}}`
			`{{#if selectKit.filter}}`
			`{{#if selectKit.hasNoContent}}`
			`<span class="no-content">`
			`{{i18n "select_kit.no_content"}}`
			`</span>`
			`{{/if}}`
			`{{/if}}`
[WIP] select-box-kit refactoring 2017-10-20 03:51:08 +08:00
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 21:22:14 +08:00			`{{#each collections as \|collection\|}}`
			`{{component (component-for-collection collection.identifier selectKit)`
			`collection=collection`
			`selectKit=selectKit`
			`value=value`
			`}}`
			`{{/each}}`
			`{{else}}`
			`<span class="is-loading">`
			`{{loading-spinner size="small"}}`
			`</span>`
			`{{/unless}}`
			`{{/select-kit/select-kit-body}}`

			`<div class="select-kit-wrapper"></div>`
			`{{/unless}}`