* fix: 🐛 refactor info-field component Overall context of how the `<InfoField/>` was changed to the correct order. Corrected css grid to have the order of `label,input-field,helper-text`. Also refactored all component instances affected by the change. * refactor: 💡 refactor styling for icon to be center refactor will get the icon as close to center as possible. * chore: 🤖 ssh type first; update names and descriptions * chore: 🤖 tweak info field styles * chore: 🤖 fix formatting/linting issue * refactor: 💡 credential stylistic changes per PR feedback * chore: 🤖 reuse configPath * fix: 🐛 fix lint error * chore: 🤖 add target type field helper text Co-authored-by: dvonanderson <devon.anderson@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.