-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Category tags #74
Category tags #74
Conversation
Your description sounds good to me. I've been trying to think of a better way to talk about required tags (to users), because it's really that you must include one member of this set. Any individual tag in that set isn't required; it's that you have to choose one from the group. If I could come up with better language I'd want to use that in the UI (defining them, instructions to include one, error if you don't). If anyone has any ideas please share. If not we can go with this; I just have this nagging feeling... Can we set this up on the dev server to poke at? |
Done. Dev server should be ready to poke. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems okay, but CI is failing. :)
That's rubocop - I'm going to ignore it for now and fix it later on develop. |
In this PR: