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
Please consider lettign us use this outside of arb/csv files, but instead with strings/text widgets.
for example, suppose we are using
Text('hi');
and for whatever reason we are not quite ready to use arb type localization and/or for whatever reason are not using a localization library/package that works quite the same way.
Could we please have the option to use 'hi'.psuedo() and translate to a psuedo string, perhaps with sane defaults for first pass, then configurable just like your yaml file for second pass?
thanks
The text was updated successfully, but these errors were encountered:
Hi @neiljaywarner, this is a use case I never actually thought of and haven't needed myself. In feature/call-pseudo-directly-on-strings I've put together a very quick & dirty POC.
If you dependent on flutter_pseudolocalizor as a dependency (as opposed to dev_dependency as normal) from git
As mentioned, this is very quick & dirty, nevertheless it works and can be experimented on :)
Let me know what you think. There is no EDD on when this would ship on pub: the existing api will need to be updated, however the POC branch should work just fine.
Please consider lettign us use this outside of arb/csv files, but instead with strings/text widgets.
for example, suppose we are using
Text('hi');
and for whatever reason we are not quite ready to use arb type localization and/or for whatever reason are not using a localization library/package that works quite the same way.
Could we please have the option to use 'hi'.psuedo() and translate to a psuedo string, perhaps with sane defaults for first pass, then configurable just like your yaml file for second pass?
thanks
The text was updated successfully, but these errors were encountered: