discourse/app/assets/javascripts/select-kit/components/topic-footer-mobile-dropdown.js.es6

import ComboBoxComponent from "select-kit/components/combo-box";

export default ComboBoxComponent.extend({
  pluginApiIdentifiers: ["topic-footer-mobile-dropdown"],
  classNames: ["topic-footer-mobile-dropdown"],

  selectKitOptions: {
    none: "topic.controls",
    filterable: false,
    autoFilterable: false
  },

  actions: {
    onChange(value, item) {
      item.action && item.action();
    }
  }
});
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 ComboBoxComponent from "select-kit/components/combo-box";`
[WIP] select-box-kit refactoring 2017-10-20 03:51:08 +08:00
			`export default ComboBoxComponent.extend({`
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			`pluginApiIdentifiers: ["topic-footer-mobile-dropdown"],`
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: ["topic-footer-mobile-dropdown"],`
[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			`selectKitOptions: {`
			`none: "topic.controls",`
			`filterable: false,`
			`autoFilterable: false`
[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			`actions: {`
			`onChange(value, item) {`
			`item.action && item.action();`
			`}`
[WIP] select-box-kit refactoring 2017-10-20 03:51:08 +08:00			`}`
			`});`