You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I switched to your plugin since intl_translation has dependency problems.
Thanks for creating this fork, because it works fine, but I was wondering if it's possible to have a commandline option to disable the generation of the "placeholders_order" element in the arb files? This wasn't part of the files generated by intl_translation, and I already have quiet a large translated file (700+ translated strings), so I either have to redo the whole translated file, or it gets cumbersome to see the actual differences if I generate new files using your plugin. An option to not generate this element would help a lot.
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for the late reply, notification were disabled for this repo. The purpose of placeholders_order is to know the order of the different placeholders. That allows package like flutter_jimtl to be able to read ARB file on the fly directly in dart, and by the same occasion allow OTA updates for ARB files.
For sure an option can be added to not generate it. But we will not have time to do it as on our side we need it. But I will gladly review and merge a PR that allows this.
Hi,
I switched to your plugin since intl_translation has dependency problems.
Thanks for creating this fork, because it works fine, but I was wondering if it's possible to have a commandline option to disable the generation of the "placeholders_order" element in the arb files? This wasn't part of the files generated by intl_translation, and I already have quiet a large translated file (700+ translated strings), so I either have to redo the whole translated file, or it gets cumbersome to see the actual differences if I generate new files using your plugin. An option to not generate this element would help a lot.
Thanks!
The text was updated successfully, but these errors were encountered: