Skip to content
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

[BUG] .mlvtools configuration file should be validated lazily #53

Open
SdgJlbl opened this issue Nov 19, 2019 · 0 comments
Open

[BUG] .mlvtools configuration file should be validated lazily #53

SdgJlbl opened this issue Nov 19, 2019 · 0 comments

Comments

@SdgJlbl
Copy link
Collaborator

SdgJlbl commented Nov 19, 2019

If a .mlvtools configuration file is present, the current behaviour is that any command will first check that the configuration file is correctly formatted and validate that all the paths exist, even if some part of the configuration will never be used by the command (eg the file for dvc commands when you only use ipynb_to_python, or if you provide explicitly an output path to the command).
It would be best to validate the paths lazily when there are used, and to allow for incomplete configuration files if one does not wish to use all MLV-tools commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant