0 Fork 0

Files

T

Cameron Perera a48fd5d9f4 refactor: 💡 remove Type column from channel table (#201 )

* refactor: 💡 remove Type column from channel table

✅ Closes: ICU-8772

* refactor: 💡 remove Type reference from Channel details sidebar

* refactor: 💡 remove unused Type translation

2023-04-18 12:30:37 -05:00

actions

Main to session recording (#178 )

2023-04-03 20:28:31 -07:00

errors

[COMPLIANCE] Add Copyright and License Headers (#1617 )

2023-03-01 09:39:41 -06:00

form

fix: 🐛 Fix vault worker filter description (#1651 )

2023-03-02 10:25:37 -05:00

notifications

[COMPLIANCE] Add Copyright and License Headers (#1617 )

2023-03-01 09:39:41 -06:00

resources

refactor: 💡 remove Type column from channel table (#201 )

2023-04-18 12:30:37 -05:00

states

[COMPLIANCE] Add Copyright and License Headers (#1617 )

2023-03-01 09:39:41 -06:00

en-us.yaml

Main to session recording (#178 )

2023-04-03 20:28:31 -07:00

README.md

docs: ✏️ Create README for translations (#1182 )

2022-07-13 11:17:13 -05:00

README.md

Translations

Translations are used to keep template, form, and component files free of raw strings and create a single source of truth for text used throughout the repository.

Examples:

{{t 'states.' message.type}}

{{t (concat "errors." this.messageCode ".description")}}

Actions

Action translations are reserved for actions a user can trigger.

Errors

Translations that are for varying error titles and descriptions.

Form

Translations for label and description text required for form fields.

Notifications

Translations for notification messages.

Resources

Translations with direction relation to different resources (e.g. accout, org, host).

States

Translations for text related to different states data could be in (e.g. active, inactive, error).

Root Translations

Translations for titles, descriptions, and translations that do not fit into other translation files.