-
Notifications
You must be signed in to change notification settings - Fork 100
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
feat: Move gtfsvalidator.cli package into new cli sub-module. #1229
feat: Move gtfsvalidator.cli package into new cli sub-module. #1229
Conversation
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! Thanks a lot @bdferris-v2
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! Thanks a lot @bdferris-v2
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 just tested the behavior locally, and it seems that the JAR file works, but there is a problem with the validators, even though all the status checks passed.
This is stdout when using the JAR file built on the master
branch:
and now the stdout with the new JAR file:
Also, comparing the reports indicates a problem. Using master
:
One problem I see here is that our acceptance tests don't detect this kind of problem. They verify that new rules don't add too many new errors, not if errors are disappearing. Perhaps we should change them to check other anomalies. I initially approved this PR because all tests were passing, so we should definitely find a way to capture problems like these. cc @isabelle-dr
…'t minimized in shadowJar computation.
…validator into issue/1188/cli
@maximearmstrong indeed that's a subtle bug. When shadowJar minimization moved from Regarding acceptance tests, maybe we can add an issue to track fixing that as well? |
All good. I tested it locally and it worked well. Thanks for this modification @bdferris-v2 Regarding acceptance tests, I've opened #1232. I think we could add a few new rules. Your thoughts are welcome :) |
Summary:
Per discussion in #1188, I'm proposing to move the
gtfsvalidator.cli
package and associated classes for the GTFS Validator command-line interface into their own Gradle sub-module. This will support future modularization and packaging of the validator in ways that don't assume a CLI.Please make sure these boxes are checked before submitting your pull request - thanks!
gradle test
to make sure you didn't break anything