-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Traceback on --search
parameter with plain string
#34
Comments
@kdeldycke, I love the thoroughness of your issues. Thank you so much for that. I have a branch and test that reproduces the issue. I think the best course of action is to refactor a bit more and decouple the formatting logic found in the I'll work on it today. |
Thanks for the feedback! And take your time, there is not rush. 🤗 BTW, if it helps to simplify things, and allows you refactor further, I guess you can now start to break backward-compatibility with |
- The `--search` and `--replace` options now completely override any other search and replace logic. Fixes #34
Can confirm this has been fixed in 0.7.1. Thanks @coordt for the quick fix! 💪 |
For the record this fix helped my replace some Perl oneliners with bump-my-version: kdeldycke/workflows@b13b6b6 |
0.7.0
3.11.4
Description
It seems a search and replace operation (without any bump), on a search string that is a constant (i.e. no reference of a version), lead to a traceback.
What I Did
Here is a minimal example to reproduce the issue with this structure:
The local
./docs.yaml
file contains:./pyproject.toml
contains:I use the latest CLI:
The configuration file is sourced correctly with the good defaults:
Now if I try to perform a simple search & replace operation on
./docs.yaml
with:I get the following traceback:
The text was updated successfully, but these errors were encountered: