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

import SingleSelectComponent from "select-kit/components/single-select";

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

  selectKitOptions: {
    autoFilterable: false,
    filterable: false,
    showFullTitle: true,
    headerComponent: "dropdown-select-box/dropdown-select-box-header",
    caretUpIcon: "caret-up",
    caretDownIcon: "caret-down",
    showCaret: false,
  },

  modifyComponentForRow() {
    return "dropdown-select-box/dropdown-select-box-row";
  },
});
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 18:53:09 +08:00			`import SingleSelectComponent from "select-kit/components/single-select";`

			`export default SingleSelectComponent.extend({`
			`pluginApiIdentifiers: ["dropdown-select-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 21:22:14 +08:00			`classNames: ["dropdown-select-box"],`
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 18:53:09 +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			`selectKitOptions: {`
			`autoFilterable: false,`
			`filterable: false,`
			`showFullTitle: true,`
UX: allows dropdown-select-box to display a caret (#9803) ``` selectKitOptions: { showCaret: true // default false } ``` 2020-05-18 16:50:33 +08:00			`headerComponent: "dropdown-select-box/dropdown-select-box-header",`
			`caretUpIcon: "caret-up",`
			`caretDownIcon: "caret-down",`
			`showCaret: false,`
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 18:53:09 +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			`modifyComponentForRow() {`
			`return "dropdown-select-box/dropdown-select-box-row";`
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 18:53:09 +08:00			`},`
			`});`