-
Notifications
You must be signed in to change notification settings - Fork 7
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 petablint with individual tables #274
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #274 +/- ##
===========================================
- Coverage 76.30% 76.09% -0.22%
===========================================
Files 36 36
Lines 3224 3233 +9
Branches 783 786 +3
===========================================
Hits 2460 2460
- Misses 559 568 +9
Partials 205 205 ☔ View full report in Codecov by Sentry. |
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.
👍
dest="yaml_file_name", | ||
help="PEtab YAML problem filename", | ||
nargs="?", |
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 wonder if it's possible to say yaml_file_name_deprecated
takes 0 arguments, i.e. it's treated as just a "flag", and instead its argument then gets treated as a positional argument, and hence saved to yaml_file_name
. Anyway, not important
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.
It can be done and would slightly simplify the code, but the petablint --help
output would be more confusing, I think.
Co-authored-by: Dilan Pathirana <59329744+dilpath@users.noreply.github.com>
I think the main use case is running petablint on a full petab problem, so we don't need the option to pass individual tables. To support individual tables with the upcoming petab v2, we'd have to extend the list of files and require a version number. I don't it's worth maintaining this functionality (correct me if I am wrong), since validation of individual files is anyways rather limited.
Therefore, this adds deprecation warnings to command line arguments for individual PEtab tables and for the
-y
--yaml
flags, which are no longer required, and the removal of which will makepetablint
easier to use.Related to #271