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
Fixes #9734: Store tags on Directives/Rules #1410
Fixes #9734: Store tags on Directives/Rules #1410
Conversation
Commit modified |
0e2901d
to
548f168
Compare
Commit modified |
548f168
to
bc23eda
Compare
/** | ||
* We can have multiple Tags with same name - unicity is really on TagName + TagValue | ||
*/ | ||
final case class Tags( |
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.
Do we need that class ? what is the advantage of having a 'Tags' instead of a 'Set[Tags]' directly in our objects ?
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.
I don't know what would be the advantage. It is more verbose, and the only possible advantage might be that one day Tags would be different, and so it wouild encapsulate change; but this is dubious
Should I drop it ?
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.
I would have removed it yes!
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.
Actually, having the Tags class let me define in one location only the rules on unicities - so if we want to change in the future the rules on tags, it'll be easier
so i favour keeping the Tags class
Apart the question on the Tags type, that can be merged ! |
OK, merging this PR |
OK, merging this PR |
No description provided.