Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For required tags, allow child tags to satisfy the requirement #1273

Open
cellio opened this issue Dec 17, 2023 · 0 comments
Open

For required tags, allow child tags to satisfy the requirement #1273

cellio opened this issue Dec 17, 2023 · 0 comments
Labels
area: ruby Changes to server-side code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: low type: change request New feature or request

Comments

@cellio
Copy link
Member

cellio commented Dec 17, 2023

meta:289410

A category can specify a set of required tags, such that a top-level post must use at least one tag from the set. Meta does this for discussion/feature-request/support/bug. Some communities would like to use required tags to require some child tag -- for example, a programming-language tag on Software Dev that can be satisfied with C++ or Python, or a locale tag on a hypothetical law or workplace community that's satisfied with Canada or EU or New York.

When checking a post for required tags, can we check not only the exact tags but their parents up the chain?

I'm setting the priority low for now because we don't have an active request from a community that I know of, but it's something that could be used if we had it so it's worth considering.

@cellio cellio added area: ruby Changes to server-side code type: change request New feature or request priority: low complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. labels Dec 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ruby Changes to server-side code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: low type: change request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant