Closed KyleKun closed 3 years ago
Merging this now, lemme know whats the issue with translations.
Several places where trying to access .name the linter complains and it won't build... I replaced it by .language and .country but then the first RegExp would fail the first time in a null check, it worked after setting to english by default and then reading it from storage next time again...
About intl, I think we wouldn't need to restart the app when changing locale then.
Several places where trying to access .name the linter complains and it won't build... I replaced it by .language and .country but then the first RegExp would fail the first time in a null check, it worked after setting to english by default and then reading it from storage next time again...
About intl, I think we wouldn't need to restart the app when changing locale then.
Pretty sure the .name
is caused by older version of dart. Could use intl, but thats comes with the cause of refactoring lot of code, if there is a way to rebuild the whole MaterialApp
widget completely, then we won't be needing to restart the app. (I've tried changing key
, wrapping the whole app within a StatefulWidget
and use setState
to rebuild and marking as needs build way but none of them seem to rebuild everything but only some parts of the widgets)
Hey @zyrouge !
This PR adds:
ValueListenableBuilder
widget capable of listening 2 valuespt_br
translationBtw, I had some issues with recent translations changes but I managed to fix it for running locally (I am not pushing these translation changes since I just wanted to check this buffering feature). Maybe we could use intl to facilitate things a little bit?
Let me know what you think. Thank you!