discourse/plugins/poll/test/javascripts/helpers/display-poll-builder-button...

import selectKit from "helpers/select-kit-helper";

export async function displayPollBuilderButton() {
  await visit("/");
  await click("#create-topic");
  await click(".d-editor-button-bar .options");
  await selectKit(".toolbar-popup-menu-options").expand();
}
DEV: refactors select-kit helper to prevent it to leak into global state (#7708) 2019-06-06 04:47:10 -04:00			`import selectKit from "helpers/select-kit-helper";`

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 08:22:14 -05:00			`export async function displayPollBuilderButton() {`
			`await visit("/");`
			`await click("#create-topic");`
			`await click(".d-editor-button-bar .options");`
			`await selectKit(".toolbar-popup-menu-options").expand();`
FEATURE: introduces minimum trust level for polls (#5391) * FEATURE: introduces minimum trust level for polls This commit makes `poll_enabled` less misleading and introduces `poll_minimum_trust_level_to_create`. If poll are enabled they will always be cooked, and if you have the required trust level you can create polls. As a side effect, it also fixes a bug where rebaking a post created by staff member when `poll_enabled=false` would end up not cooking it. It also adds more tests to ensure settings are respected. * admins should be whitelisted * checks for admin in post validation * test for >= instead of == trust level 2017-12-04 08:47:11 -05:00			`}`