github-mirror/discourse
2
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-11-30 05:36:29 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
f1701764a6
discourse/app/assets/javascripts/select-kit/addon/templates/components/single-select.hbs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
1.1 KiB
Handlebars
Raw Normal View History

FIX: select-kit components not being hidden.
2020-06-04 21:33:57 +08:00
{{#unless selectKit.isHidden}}
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
{{component selectKit.options.headerComponent
tabindex=tabindex
value=value
selectedContent=selectedContent
selectKit=selectKit
A11Y: makes aria-owns an ID and not a data attribute (#12075)
2021-02-15 19:32:09 +08:00
id=(concat selectKit.uniqueID "-header")
[WIP] select-box-kit refactoring
2017-10-20 03:51:08 +08:00
}}
A11Y: makes aria-owns an ID and not a data attribute (#12075)
2021-02-15 19:32:09 +08:00
{{#select-kit/select-kit-body selectKit=selectKit id=(concat selectKit.uniqueID "-body")}}
{{component selectKit.options.filterComponent selectKit=selectKit id=(concat selectKit.uniqueID "-filter")}}
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
DEV: enforces ember-template-lint: simple-unless (#9146)
2020-03-09 20:44:34 +08:00
{{#if selectKit.isLoading}}
<span class="is-loading">
{{#if site}}
{{loading-spinner size="small"}}
{{/if}}
</span>
{{else}}
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
{{#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}}
DEV: enforces ember-template-lint: simple-unless (#9146)
2020-03-09 20:44:34 +08:00
{{/if}}
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}}
[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
<div class="select-kit-wrapper"></div>
{{/unless}}
Reference in New Issue Copy Permalink