-
Notifications
You must be signed in to change notification settings - Fork 8
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
Suggestion for fixing the unintentional situation that since v0.6 the… #404
Conversation
… dataconverter required a config file if it was called the classical way and in case no parameter yaml file was provided. For programmatically use of the converter the creation of an additional params file with only a few entries is unnecessary overhead especially when all cli arguments are available in the callers scope and thus the CLI call can be issues directly using the classical way dataconverter convert [INPUTFILES] options
I also removed the outdated documentation of the command line options as it is a second place where changes have to be applied constantly and the instructions for empowering people to find these are already given in the readme plus follow the typical style how to get help for command line calls |
…is passed via cli but instead have their own configurations for the respective formats they support as part of the plugin source code, hence calling these readers with kwargs config is unnecessary and incorrect, this commit fixes this bug
Tested 30ad68c of this branch solves the problems @sherjeelshabih |
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 tested with
pynxtools-xps
, both with and w/o a config filepyntools-mpes
, always uses config filepynxtools-stm
pynxtools-em
, with the example @mkuehbach send mejson_map
-> with examples inexample/json-map
@mkuehbach feel free to merge if your examples still run through (wasn't sure if you tested something else as well). Thanks for the fix!
Outdated conflicts were resolved
… dataconverter required a config file if it was called the classical way and in case no parameter yaml file was provided. For programmatically use of the converter the creation of an additional params file with only a few entries is unnecessary overhead especially when all cli arguments are available in the callers scope and thus the CLI call can be issues directly using the classical way dataconverter convert [INPUTFILES] options