-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix typo in import control #9500
Conversation
Signed-off-by: Federico Valeri <[email protected]>
927759b
to
a365c30
Compare
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 guess the rule is not needed if everything worked despite the typo?
Unlike |
Sorry, I don't follow what you mean by this. If the rule refers to a wrong class and nothing is failing, it seems that either the import control does not work properly or the rule is not needed at all. |
We have two similar rules for operator-common: <import-control pkg="io.strimzi" strategyOnMismatch="allowed">
<subpackage name="operator.common.model" strategyOnMismatch="disallowed">
...
<allow class="io.strimzi.api.ResourceLabels" /> <!-- rule 1 -->
<allow class="io.strimzi.api.ResourceAnnotations" /> <!-- rule 2 --> These rules are supposed to be used by the following classes: io.strimzi.operator.common.model.Labels // extends io.strimzi.api.ResourceLabels
io.strimzi.operator.common.Annotations // extends io.strimzi.api.ResourceAnnotations Nothing is failing because Now, there are two paths here:
|
I would probably remove the rule. |
Signed-off-by: Federico Valeri <[email protected]>
This change fixes a typo in the import-control configuration file.