mirror of
https://github.com/discourse/discourse.git
synced 2024-12-02 02:03:40 +08:00
0431942f3d
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**
34 lines
879 B
JavaScript
34 lines
879 B
JavaScript
import selectKit from "helpers/select-kit-helper";
|
|
import { acceptance } from "helpers/qunit-helpers";
|
|
|
|
acceptance("Topic Notifications button", {
|
|
loggedIn: true,
|
|
pretend(server, helper) {
|
|
server.post("/t/280/notifications", () => {
|
|
return helper.response({});
|
|
});
|
|
}
|
|
});
|
|
|
|
QUnit.test("Updating topic notification level", async assert => {
|
|
const notificationOptions = selectKit(
|
|
"#topic-footer-buttons .topic-notifications-options"
|
|
);
|
|
|
|
await visit("/t/internationalization-localization/280");
|
|
|
|
assert.ok(
|
|
notificationOptions.exists(),
|
|
"it should display the notification options button in the topic's footer"
|
|
);
|
|
|
|
await notificationOptions.expand();
|
|
await notificationOptions.selectRowByValue("3");
|
|
|
|
assert.equal(
|
|
notificationOptions.header().label(),
|
|
"Watching",
|
|
"it should display the right notification level"
|
|
);
|
|
});
|