-
Notifications
You must be signed in to change notification settings - Fork 264
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
New --config
option doesn't appear to work.
#409
Comments
@krtschmr Can you please have a look? |
@geoffharcourt Is it still applicable for the latest version? bundle exec i18n-tasks --version
1.0.5
bundle exec i18n-tasks --config what
i18n-tasks: Config file doesn't exist: what |
@davidwessman I'm not sure why, but in multiple environments we're still seeing this issue:
This happens if I run the gem (same version) from the system installation (not from bundler) we get the same behavior. |
I cannot recreate this execpt for v0.9.34 when the option did not exist.
|
Hi @davidwessman I'm still confused about what's going on. I checked and I don't have any of the pre-config option versions installed:
I confirmed I'm using the version associated with my local Ruby installation (MacOS, Ruby 3.1.2):
And I'm still getting an error when trying to use the flag:
|
What does |
Hi @glebm, sorry for not including that earlier:
|
How does your i18n-tasks.yml look? |
@davidwessman I'd hope that only the one I'm referencing matters, but here's the one that's normally in place for us (
and here's the one I'm trying to use via the flag (
|
I have the same issue. When a config file doesn't exist it shows correct error message
But when I use the real file path it shows
I was able to make it work with a simple change, see #455. |
Ah, I only tested with non-existing files... Good find! |
Thanks everyone for the help and the fix! |
@glebm yeah, sorry, i was "AFK" :-)
thanks everybody for fixing my oversight. 💪🏿 |
The
--config
option to specify an alternate location for the configuration file doesn't appear to be accepted in either 0.9.35 (where it was added) or 0.9.36.The text was updated successfully, but these errors were encountered: