-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tooling] Generate translation reference JSON during build #6143
Comments
@macandcheese I think we could generate something for this quite easily. What's the desired timeline for this? |
As soon as reasonable without a rush - not high priority. Whenever it is available I can add it into documentation site. Currently we only show the English string. |
Yeah I can whip something up after the patch period and other v1 stuff quiets down |
@benelan Were you able to whip something up for this? We modified the milestone, but can move it sooner if it's feasible. |
I haven't gotten to this yet, there are some higher priority items on my plate |
**Related Issue:** #6143 ## Summary Generates `dist/extras/translations-json.json` which contains the t9n values per component in the following format: ```jsonc { "components": { "calcite-action": { "loading": { "en": "Close", "es": "Cerrar" // ... }, "disabled": { "en": "Close", "es": "Cerrar" // ... } }, "calcite-alert": { "loading": { "en": "Close", "es": "Cerrar" // ... }, "disabled": { "en": "Close", "es": "Cerrar" // ... } } } } ```
Installed and assigned for verification. |
Verified with |
Summary
The documentation site uses the
docs-json.json
file in theextras
folder of our distributable to format and display docs to users. We would benefit from having a similar output for the updated translation files.docs-json.json
includes each file'smessageOverride
string names, but not the default values, which would be valuable to show in documentation. It would be great if these were included as well.Alternatively, and maybe easier than fighting jsdoc, we could generate our own
translations-json.json
at build time, since the files seem to be in a predictable location and format: (/dist/assets/<component>/t9n
).Desired Outcome
Something like this, but any format works as long as the default are available somehow.
Resources
No response
The text was updated successfully, but these errors were encountered: