FEATURE: Allow choice of category when making a PM public (#7907)

* FEATURE: Allow choice of category when making a PM public

Previously it would default to uncategorized, which was not ideal on
some forums. This gives the staff member more choice about what they'd
like to do.

* Make the optional category more explicit

* Joffrey's feedback
This commit is contained in:
Robin Ward
2019-07-19 11:52:50 -04:00
committed by GitHub
parent 9075789783
commit 8dd3cbfcb9
11 changed files with 86 additions and 10 deletions
@@ -213,6 +213,20 @@ QUnit.test("remove featured link", async assert => {
// assert.ok(!exists('.title-wrapper .topic-featured-link'), 'link is gone');
});
QUnit.test("Converting to a public topic", async assert => {
await visit("/t/test-pm/34");
assert.ok(exists(".private_message"));
await click(".toggle-admin-menu");
await click(".topic-admin-convert button");
let categoryChooser = selectKit(".convert-to-public-topic .category-chooser");
await categoryChooser.expand();
await categoryChooser.selectRowByValue(21);
await click(".convert-to-public-topic .btn-primary");
assert.ok(!exists(".private_message"));
});
QUnit.test("Unpinning unlisted topic", async assert => {
await visit("/t/internationalization-localization/280");