-
Notifications
You must be signed in to change notification settings - Fork 80
fix(docs): use updated translation bundle paths to generate translations.json
#11219
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥇
@@ -24,7 +24,7 @@ | |||
Object.keys(messagesFileMain).forEach((key) => (data[component][key] = {})); | |||
|
|||
const messagesFilenames = (await readdir(t9nPath, { withFileTypes: true })).map((dirent) => dirent.name); | |||
const messagesFilenameRegex = new RegExp(`${component}\\.t9n\\.(.*)\\.json`); | |||
const messagesFilenameRegex = new RegExp(`messages\\.(.*)\\.json`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sidenote: should have been caught here #11054.
Is there a way to add a test to assert this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, we don’t have tests for our support files/scripts, but we could explore adding something like output snapshot diffing, similar to the design tokens. Open to ideas here. Could you open a follow-up issue for this?
Related Issue: #10731
Summary
Updates
generateT9nDocsJSON.ts
to reference the updated translations bundle file name (see #11054).