discourse/app/assets/javascripts/select-kit/components/combo-box.js

import SingleSelectComponent from "select-kit/components/single-select";
import { computed } from "@ember/object";

export default SingleSelectComponent.extend({
  pluginApiIdentifiers: ["combo-box"],
  classNames: ["combobox", "combo-box"],

  selectKitOptions: {
    caretUpIcon: "caret-up",
    caretDownIcon: "caret-down",
    autoFilterable: "autoFilterable",
    clearable: false,
    headerComponent: "combo-box/combo-box-header"
  },

  autoFilterable: computed.gte("content.length", 10)
});
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 11:53:09 +01:00			`import SingleSelectComponent from "select-kit/components/single-select";`
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 14:22:14 +01:00			`import { computed } from "@ember/object";`
[WIP] select-box-kit refactoring 2017-10-19 12:51:08 -07:00
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 11:53:09 +01:00			`export default SingleSelectComponent.extend({`
			`pluginApiIdentifiers: ["combo-box"],`
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 14:22:14 +01:00			`classNames: ["combobox", "combo-box"],`
[WIP] select-box-kit refactoring 2017-10-19 12:51:08 -07: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 14:22:14 +01:00			`selectKitOptions: {`
			`caretUpIcon: "caret-up",`
			`caretDownIcon: "caret-down",`
			`autoFilterable: "autoFilterable",`
			`clearable: false,`
			`headerComponent: "combo-box/combo-box-header"`
FIX: select-kit refactoring - improve mini-tag-chooser keyboard behavior - all multil select now respond to select all and left/right arrows - improve events handling - many minor tweaks 2018-03-22 11:29:55 +01:00			`},`

DEV: Autofilter combo boxes on 10+ dropdown items by default 2020-02-04 11:23:15 -05:00			`autoFilterable: computed.gte("content.length", 10)`
[WIP] select-box-kit refactoring 2017-10-19 12:51:08 -07:00			`});`