mirror of
https://github.com/discourse/discourse.git
synced 2025-05-29 11:48:08 +08:00
FIX: Change rootNone behavior in category-chooser (#8692)
This breaking change was originally a deprecation fix for overriding a computed property `none`. There are 4 uses of `rootNone` in core and "all-the-plugins": 1. in discourse-chat-integration, admin-plugins-chat-edit-rule.hbs - changed behavior, that I'd consider a fix - `rootNoneLabel` is now used regardless of `siteSettings.allow_uncategorized_topics` value, which I believe was an originally intended behavior (i.e. it most likely hasn't been tested with disabled uncategorized topics) 2. in discourse-slack-official, plugins-slack.hbs - the same as 1. 3. in core, edit-category-general.hbs (in this PR) - no change in behavior 4. in discourse-googlebooks, edit-category-general.hbs - no change in behavior (since `allowUncategorized="true"` is also passed as an argument)
This commit is contained in:
@ -73,7 +73,7 @@ componentTest("with allowUncategorized=null rootNone=true", {
|
||||
|
||||
test(assert) {
|
||||
assert.equal(this.subject.header().value(), null);
|
||||
assert.equal(this.subject.header().title(), "category");
|
||||
assert.equal(this.subject.header().title(), "(no category)");
|
||||
}
|
||||
});
|
||||
|
||||
@ -88,7 +88,7 @@ componentTest("with disallowed uncategorized, rootNone and rootNoneLabel", {
|
||||
|
||||
test(assert) {
|
||||
assert.equal(this.subject.header().value(), null);
|
||||
assert.equal(this.subject.header().title(), "category");
|
||||
assert.equal(this.subject.header().title(), "root none label");
|
||||
}
|
||||
});
|
||||
|
||||
|
Reference in New Issue
Block a user