* chore: 🤖 JSON credential data modeling Added json type to credential model, created `json_object` attribute for `json` type, updated credential serializer to handle `json_object` attribute data being sent to backend and updated normalizer to handlle secret untracked 'json_object'. ✅ Closes: ICU-6653, ICU-6684, ICU-6685, ICU-6802, ICU-6803 * Update en-us.yaml fixed spelling * Update addons/api/addon/models/credential.js Co-authored-by: Cameron Perera <cameron.perera@hashicorp.com> * refactor: 💡 refactor credential serializer and .yaml Refactored credential serializer to check for `json_object` existence before serializing and changed help variable in `.yaml` file for credentials. * refactor: 💡 refactor for credential serializer Refactor credential serializer removed redundant code, Co-authored-by: Cameron Perera <cameron.perera@hashicorp.com>
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.