-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat(localization): add schema for localization.json files #1713
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 62028f3. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
packages/@o3r/localization/builders/helpers/localization.generator.ts
Outdated
Show resolved
Hide resolved
}, | ||
"dictionary": { | ||
"type": "boolean", | ||
"description": "Determine if the item can have multiple extensions", |
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.
does this description really match what this field does ?
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.
Just used the description from TS interface, it is not perfect but not wrong.
Basically it determines that the key can have a .<somthing>
suffix.
If you have better, I take it :)
ca5444e
to
49a5d34
Compare
49a5d34
to
62028f3
Compare
Proposed change
Add localization.json files JSON Schema
Related issues