github-mirror/discourse
2
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-12-01 19:35:09 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
dd85d44dda
discourse/app/assets/javascripts/select-kit/addon/components/topic-notifications-options.js

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

22 lines
658 B
JavaScript
Raw Normal View History

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
import NotificationsButtonComponent from "select-kit/components/notifications-button";
[WIP] select-box-kit refactoring
2017-10-20 03:51:08 +08:00
import { topicLevels } from "discourse/lib/notification-levels";
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
import { computed } from "@ember/object";
[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
export default NotificationsButtonComponent.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-notifications-options"],
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-notifications-options"],
[WIP] select-box-kit refactoring
2017-10-20 03:51:08 +08:00
content: topicLevels,
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: {
i18nPrefix: "i18nPrefix",
UX: show caret only in topic footer buttons dropdown select boxes (#9816)
2020-05-18 20:07:40 +08:00
i18nPostfix: "i18nPostfix",
showCaret: true
FIX: use the correct notification levels descriptions for PMs
2018-06-11 17:35:13 +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
i18nPrefix: "topic.notifications",
Upgrade to Ember 3.7.0
2019-03-20 19:50:13 +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
i18nPostfix: computed("topic.archetype", function() {
return this.topic.archetype === "private_message" ? "_pm" : "";
FIX: ensures shortcuts work correctly with topic-notifications-button (#8956)
2020-02-13 17:01:28 +08:00
})
[WIP] select-box-kit refactoring
2017-10-20 03:51:08 +08:00
});
Reference in New Issue Copy Permalink