Files
threshold-ui/addons/core/translations
Randall MoreyandZhihe Li 7350c0e08c Feature metadata (#1661)
* feat: 🎸 load edition from controller-metadata.json

* refactor: 💡 rename edition and add licensed features support

* chore: 🤖 support dev toggling of licensed features

* chore: 🤖 rename ent edition

* Update ui/admin/app/services/feature-edition.js

* Update ui/admin/app/instance-initializers/feature-edition.js

Co-authored-by: Zhihe Li <zhihe.li@hashicorp.com>

* chore: 🤖 cleanup

* chore: 🤖 feature edition disabled in tests / fix test cases

* test: 💍 remove feature disable calls in tests

* test: 💍 fix broken tests

* fix: 🐛 fix config bug

* fix: 🐛 fix broken test due to feature flags

---------

Co-authored-by: Zhihe Li <zhihe.li@hashicorp.com>
2023-03-31 17:38:17 -07:00
..
2023-03-31 17:38:17 -07:00
2023-03-31 17:38:17 -07:00

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.