-
Notifications
You must be signed in to change notification settings - Fork 909
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
Unhide cookiecutter errors in kedro new
#3693
Unhide cookiecutter errors in kedro new
#3693
Conversation
Signed-off-by: Elena Khaustova <[email protected]>
Signed-off-by: Elena Khaustova <[email protected]>
Signed-off-by: Elena Khaustova <[email protected]>
22b4cc9
to
8f82253
Compare
Signed-off-by: Elena Khaustova <[email protected]>
Signed-off-by: Elena Khaustova <[email protected]>
tests/framework/cli/test_starters.py
Outdated
def test_cookiecutter_exception_if_no_verbose(self, fake_kedro_cli): | ||
"""Check if original cookiecutter exception present in the output if no verbose | ||
flag provided.""" | ||
KedroCliError.VERBOSE_EXISTS = True |
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.
Does that mean to reset the side-effect from the other test? If so I think we make sure this happen after that test so when we add new test in the future or reordering tests won't fail again.
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.
Makes sense, will move it to the end of the that test.
Signed-off-by: Elena Khaustova <[email protected]>
kedro new
Signed-off-by: Elena Khaustova <[email protected]>
🥳 |
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 left one question, but otherwise looks good! 👍
Congrats on your first PR 🥳
@@ -1,6 +1,7 @@ | |||
# Upcoming Release 0.19.4 | |||
|
|||
## Major features and improvements | |||
* Cookiecutter errors are shown in short format without the `--verbose` flag. |
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.
Are the error now shown partly for all CLI commands or just kedro new
?
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.
Now they're shown in short format for all commands but just for cookiecutter errors
. So instead of Error: Failed to generate project when running cookiecutter.
we will also get one line with a real error.
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.
🔶Congrats on your first PR🎉
This works beautifully, thanks @ElenaKhaustova ! |
Description
Close #2564
Development notes
kedro new
, so when--verbose
flag is not provided short cookiecutter error is in the output; with--verbose
flag full cookiecutter error is in the output;--verbose
flag is provided;test_run_with_invalid_config
test that was changing the behaviour of the added test by modifying the global objectKedroCliError
. The reason of it is calling_validate_config_file
that setsKedroCliError.VERBOSE_EXISTS=False
.Developer Certificate of Origin
We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a
Signed-off-by
line in the commit message. See our wiki for guidance.If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.
Checklist
RELEASE.md
file