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
In the Transaction History page (and components showing history of transactions), the transactions identified as "Revoke" have a hard-coded part in English. We want to make it translatable and also allow the translations to not be tied to the English syntax (for the order of words).
Example in French:
References and additional details
The Transaction History entries are composed here:
Apparently handle multiple parsers, and also will default to the generic case if the transaction could not definitely be identified. The hard-coded part is on line 56.
I suggest that for the two specific branches that mention the method and symbol (including the one that has the hard-coded "approval") we start using strings with token variables if possible. This way translators could also use a syntax that is correct in their language.
Acceptance Criteria
At very least make the label for Revoke transaction is translatable. If possible allow a different language syntaxes through string variables for the symbol/method for both Approve and Revoke labels.
Translations in the currently supported languages will be handled by the Globalization Workstream.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered:
Overview
In the Transaction History page (and components showing history of transactions), the transactions identified as "Revoke" have a hard-coded part in English. We want to make it translatable and also allow the translations to not be tied to the English syntax (for the order of words).
Example in French:
References and additional details
The Transaction History entries are composed here:
web/src/components/TransactionHistoryRows/TransactionMethod.tsx
Lines 43 to 60 in 4513a73
Apparently handle multiple parsers, and also will default to the generic case if the transaction could not definitely be identified. The hard-coded part is on line 56.
I suggest that for the two specific branches that mention the method and symbol (including the one that has the hard-coded "approval") we start using strings with token variables if possible. This way translators could also use a syntax that is correct in their language.
Acceptance Criteria
At very least make the label for Revoke transaction is translatable. If possible allow a different language syntaxes through string variables for the symbol/method for both Approve and Revoke labels.
Translations in the currently supported languages will be handled by the Globalization Workstream.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered: