Post History

Consider child tags in required tags

Currently, it is possible to set required tags for a category. For example, here on meta it lists as required tags one of: <a class="badge is-filled is-tag">bug</a>, <a class="badge is-filled is-tag">feature-request</a>, <a class="badge is-filled is-tag">discussion</a> or <a class="badge is-filled is-tag">support</a>.

For meta, this works pretty well, but this is relatively limiting for communities where one wants one aspect as a required tag, but the specific tags are many. For example, if we would consider a community related to programming languages, we may want to express that specifying _a programming language_ as a tag is required, but we don't want to specify all possible programming languages as that would be quite a long list in the UI.

I think it would make sense to allow putting the requirement on a hierarchical level and accepting child tags as well. Then in my example, <a class="badge is-filled is-tag">programming language</a> would be the required tag, and all child tags of programming language would satisfy the requirement. That way we could enforce that some programming language is selected, without listing all possible programming languages. New languages can just be added as children of the <a class="badge is-filled is-tag">programming language</a> tag to automatically be valid candidates for the required tag. An <a class="badge is-tag">unknown-language</a> tag or something could be added as fallback in case new languages are added (or directly adding the programming language tag).