[3.7.8] Working directory breaking change
See original GitHub issueDescribe the bug
Till version 3.7.7 the CLI tool downloads files into the working directory. Since 3.7.8 it ignores the working directory and force the use of the directory where the crowdin.yaml
is located.
To Reproduce
mkdir ~/project/src
- Create
~/project/crowdin.yml
with
"base_path": "./src"
"preserve_hierarchy": true
mkdir /tmp/crowdin-test/src
cd /tmp/crowdin-test
crowdin download -c ~/project/crowdin.yml
Files are located in ~/project/src
since 3.7.8.
Expected behavior
Files are located in /tmp/crowdin-test/src
which was the default behavior till 3.7.7.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
What's New In Python 3.8 — Python 3.11.1 documentation
... name to be changed in the future without risk of breaking client code. ... Specifically, PATH and the current working directory are...
Read more >Ccache news
Ccache 3.7.8 ... The default location of the cache directory on Windows has been changed from ... The old spelling will still work...
Read more >Documentation - Doom Emacs v21.12 documentation
3.7.8. TODO Code formatting; 3.7.9. TODO User interface. 3.7.9.1. ... remove X functionality BREAKING CHANGE: Without X, A and B will not work....
Read more >PowerDNS Authoritative Server Documentation
23.1.5 I have a working Autoprimary/Autosecondary setup but when I remove Zones ... reflect this change and systemd will automatically create the directory...
Read more >Run Python Versions in Docker: How to Try the Latest Python ...
You can then copy headlines.py to that working directory inside the container, and change the default command to run headlines.py with python ....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@andrii-bodnar thanks for the update. This is a breaking change for me, will try to use the command cli base path
@Wohllebe-dotSource happy to hear that using the command parameter works in your case.
Sorry for the inconvenience. This is our fault, we did not anticipate and underestimated this change. We definitely should have released a minor version.
We will add details to the release notes for this update.