Configuration option 'parse' is ignored when the extension is one of the following: yml, yaml, json5

[ghost]

I'm migrating from RubyOnRails to NodeJS.
And we are using transifex to manage translations.
Unfortunately all translations files were formed like:

en.yml
en:
key: some string

---

uk.yml
uk:
key: some string

---

So each file has the root element equal to locale.
I can't reupload sources to transifex and I can't change this without any specific language.
I've tried to use parse option to overcome this issue.
Unfortunately it is called only when extension of the file is unknown.

Is there any way to fix it?

[jamuhl]

Has transifex no option to download JSON format?

You might consider switching over to https://locize.com -> the translation service that comes from us...works perfect with i18next (and other i18n formats)

[ghost]

Transifex has, but it returns files in the original format....
I can't consider to switch to locize service... No way...

[ghost]

I added a pull request. Anyway, I think it will be much clear for users if parse option will provide ability to build a custom parser for any kind of file user may want to load.

[jamuhl]

That's sad...we got the work...transifex the money 🙁