-
Notifications
You must be signed in to change notification settings - Fork 36
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(sourceprocessor): fix templating for sourceCategoryPrefix #1350
Conversation
} | ||
valueTemplate = prefix + valueTemplate | ||
|
||
if doesUseAnnotation { |
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.
Why does it matter if we use annotations or not? Should prefix templating only work when using annotations?
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.
This is a good question to the author of the processor.
As I understand it: if we use the annotations, then we override the standard template value or the prefix, and then we can't use the preprocessed template attributes array.
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.
Let's get the questions answered before we merge this.
d9b253c
to
1908b1f
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.
LGTM
Waiting for @astencel-sumo
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.
Ideally let's fix that test, other than that 🚀
90fafcd
to
d425f78
Compare
@astencel-sumo I think that I added that test because there was no test that just checks the prefixing (I had some problems while implementing this and this test helped me). |
Fixes #1322 - please see the issue to see the reason why it was reopened.
related to #1339
It turns out that the previous fix was not enough, because the code was affected also in some other places. I also did a small refactor.