-
Notifications
You must be signed in to change notification settings - Fork 11
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
Deprecate -f and -m flags #23
Comments
Does this mean that when validating a collection/bundle labels with different IM versions, products will be validated correctly against the version in each label? |
Correct. That will now be the default functionality, versus right now, you have to remember to use the -f flag.
|
@ @galenatjpl Is there any sample label(s) to use for the validate tool? |
Deprecated -f and -m flags and added a note to use '-x' and/or '-S' flags when it fails in default mode. |
@hhlee445 excellent! can we make sure we get a PR created for this? looks like the changes are still just in your branch. |
Done. You should see a PR.
From: Jordan Padams <notifications@github.com>
Reply-To: NASA-PDS-Incubator/validate <reply@reply.github.com>
Date: Wednesday, July 17, 2019 at 2:52 PM
To: NASA-PDS-Incubator/validate <validate@noreply.github.com>
Cc: "Lee, Hyun H (US 398G)" <hyun.lee@jpl.nasa.gov>, Mention <mention@noreply.github.com>
Subject: [EXTERNAL] Re: [NASA-PDS-Incubator/validate] Deprecate -f and -m flags (#23)
@hhlee445<https://github.com/hhlee445> excellent! can we make sure we get a PR created for this? looks like the changes are still just in your branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#23>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ALKXIZBWW42YZ5XLBF63SQLP76ICNANCNFSM4H3L2Z3Q>.
|
Keep flags for now to ensure we don't break existing pipelines, but add deprecation warning message to output report.
* issue_23 Re-deliver issue_23 due to merge conflicts * Issue #23: Add deprecation message to -f and -m flags Keep flags for now to ensure we don't break existing pipelines, but add deprecation warning message to output report. * Add deprecated warning to config usage
These flags are no longer applicable to Validate Tool. The label itself should be self-validating, and schema/schematron versions should be specified by the labels themselves, not by validate tool.
The text was updated successfully, but these errors were encountered: