gitlawrandjialin
c025257fea
Add a Clone action to instance template cards. It reuses the create flow prefilled from the source, dropping the source id and ownership so the backend assigns a fresh id and scopes the copy to the caller's own principal. Clone is offered on every visible template — including admin-curated Global rows a non-admin can otherwise only view — so users can fork a Global preset into their own organization without admin involvement. The prefilled name defaults to a `-clone` suffix (trimmed to the 63-char limit) so cloning within the same scope doesn't collide on the unique name. Edit/Delete remain gated on ownership; Clone is always available.
Adding a New Language Configuration
To add a new language configuration, follow these steps:
1. Duplicate an Existing Language Directory
- Choose any existing language directory that you are familiar with, and duplicate it.
- Name the new directory according to the
langattribute specified inlang-config-map.tsx.
2. Create a New .ts File in the Current Directory
- In the
localesdirectory, create a.tsfile named to align with the new directory. - Copy the contents of the
en-US.tsfile into this new.tsfile. - Update the following line to match your new language directory:
const requireContext = require.context( `./{new-language-directory}`, false, /\.ts$/ );
3. Translate Each Attribute Value
-
Open the
.tsfile in the new directory. -
For each key-value pair:
- If a translation is available, replace the value with the translated text.
- If no translation is available, keep the
Englishvalue as default.
-
Note: Keeping the English text as the default ensures the application remains functional even if some translations are missing.
4. Finalize the Configuration
- Review and ensure all translations are complete.
- If any translations are missing, they will default to
English. - Your new language configuration is now ready for use!
5. Verify that all language keys are consistent.
npm run check:locales