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.

Sign up for GitHub

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

Jump to bottom

Not intuitive configuration/command parameters behaviour during import #13

Open
Im0rtality opened this issue Mar 2, 2015 · 2 comments
Open

Not intuitive configuration/command parameters behaviour during import #13

Im0rtality opened this issue Mar 2, 2015 · 2 comments
Milestone
v1.0.0

Comments

@Im0rtality
Copy link

Current situation:
Running app/console ongr:translations:import Foo\\BarBundle\\FooBarBundle imports only keys (no locale translations) due to nulled locales not matching anything. See: https://www.dropbox.com/s/wussq60g5v2qgix/Screenshot%202015-03-02%2014.06.35.png?dl=0

Running app/console ongr:translations:import imports everything.

Proposal:
When specifying one filter option (bundle/domain/locale), others should remain match all, thus running app/console ongr:translations:import Foo\\BarBundle\\FooBarBundle actually imports something useful.
@linasmo
Copy link
Contributor

linasmo commented Mar 2, 2015

Please try to provide bundle namespace in quotes.

@Im0rtality
Copy link
Author

Same issue applies to running --config-only - default configuration does not match any locales/domains.

@mvar mvar added this to the v1.0.0 milestone Dec 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.0.0
Development

No branches or pull requests
3 participants
@mvar @Im0rtality @linasmo