Closed adammscisz closed 1 year ago
That would work for all validation artefacts but may require a date for selection, in case a validation artefact is published and included before it is in effect.
I was just wondering how to always test the latest rules. I hope you'll be able to add it :)
Hello phax. Do you a date in mind to add this feature ? :) Thank you for your work!
Yes, I have that in the back of my head. Like a lot of other things... sorry 🤷🏼
Hello Philip,
Do you think you'll add that feature in coming month ? it could be really useful for us :) I know it's not a top priority and I'm sorry to bother you with that.
Thank you Philip for the work you do in the API. Have a nice day.
Fabrice.
@fabmoll yes, noted :)
Finally the pseudo version latest
can be used to resolve the latest version via ValidationExecutorSetRegistry.getByID
. Alternatively ValidationExecutorSetRegistry.getLatestVersion
can be used to manually determine the latest version.
This is part of the 8.0.1 release.
Currently when new rules appear, one needs to change both: update *-rules dependency and and pass specific VESID ruleset to Registry.
It would be nice to have an option to use latest ruleset by default so that pom update is enough to be up to date with changes.