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

[validators] Fix marker generation for validators #5008

Merged
merged 1 commit into from
Dec 20, 2021

Conversation

kriegfrj
Copy link
Contributor

Ensure that the validators are run on the model before the processor copies them into itself.

Fixes #5006

@pkriens
Copy link
Member

pkriens commented Dec 20, 2021

LGTM. Just see that the validation happens in the MarkerSupport class is a bit strange, it never creates any markers.

But I am ok

@kriegfrj
Copy link
Contributor Author

Sorry, I didn't understand your comment?

@pkriens
Copy link
Member

pkriens commented Dec 20, 2021

I looked at the code and wondered why the validation happened on the MarkerSupport class. Since it does not create markers but only errors/warnings on a processor, it is not the logical class to put this code in. I looked at this because we should not create markers inside the lock.

However, been like that forever and we don't have to fix this now.

@kriegfrj
Copy link
Contributor Author

I agree. In #5004 it was natural to move it into BndtoolsBuilder, which is now a DS component and tracks the validators as @References.

@kriegfrj kriegfrj merged commit 5135125 into bndtools:master Dec 20, 2021
@kriegfrj kriegfrj deleted the 5006-validators branch December 21, 2021 00:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[validator] Project/builder validators not generating markers
2 participants