Erik Moeller
Erik Moeller
Thanks Ro for drafting this issue, which is still very much applicable to the new app. There is one substantive way in which (as of current discussions in #2581) we...
Keeping open; every string should be open to i18n (in some instances folks may want to transliterate rather than translate).
Added to proposals backlog for now so we can make a final decision on whether we want to pursue this and potential relative priority, in a future proposal review.
Closing as we're focused on the rewrite, which will use a different test framework, so these questions will have to be considered anew.
Update from 2022-08-11 review with @tina-ux @nathandyer @l3th3 @eloquence: - Still relevant, worthy of further investigation. Could be a good first issue / summer cleanup candidate.
Closing for now as a proof-of-concept; will be revisited as part of larger sync & API overhaul.
This will need to be implemented in the new client, though likely as a post-1.0.0 feature. Keeping open for now, but can be closed and re-scoped if needed.
(Leaving unmilestoned for now given lower potential impact)
We still agree that static analysis would be useful here, want to further investigate pyre and/or alternatives, so keeping on near-term backlog.
Closing, non-critical issue specific to the current codebase, which is undergoing a rewrite. Equivalents can be considered in the context of the new codebase.