kilikfr / translationbundle Goto Github PK

Since CI is enabled (with travis), add phpcsfixer to chack coding standard.

Since branch 0.2, we could add tests.

ExportCommand.php needs tests.

Hi, great bundle! - I found it very useful.

Our translation files were in the app/Resources/translations directory (so none were found)

I just copied them to the Resources/translations/ directory inside our named bundle to find them and all worked as expected. Maybe worth updating the readme just to mention this.

From the docs:

Translation Resource/File Names and Locations¶

Symfony looks for message files (i.e. translations) in the following default locations:

the app/Resources/translations directory;
the app/Resources/<bundle name>/translations directory;
the Resources/translations/ directory inside of any bundle.

When I export a translation like this:

key: "foo\n\nbar"

and then import it again, it is transformed to this (using single quotes):

key: 'foo\n\nbar'

The latter means that \n is interpreted not as a newline but as a literal slash character followed by the letter n.
This makes importing painful because we need to edit the Yaml files after importing to fix it.
Can you fix this?

Hi, i'm triying to install with composer in Symfoy 4.4, but says thet version 1.0 requires Symfony/yaml 5.4+, but all dependencies of projects are 4.4.

On Symfony 4 projects, Command lines need to be declared like services, with tags.

Since branch 0.2, we could add tests.

ImportCommand.php needs tests.