-
-
Notifications
You must be signed in to change notification settings - Fork 111
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(developer): utilize CLDR ABNF rules to validate transforms #13175
Comments
srl295
added a commit
that referenced
this issue
Feb 13, 2025
- update fetch-latest-cldr.sh - so next time, abnf will get updated. - note, this is abnf from 47 but we’re not doing the full 47 import yet because it's not released. Fixes: feat(developer): utilize CLDR ABNF rules to validate transforms #13175
srl295
added a commit
that referenced
this issue
Feb 13, 2025
- refactor const generator - output as .sh also - use variable instead of fixed 46 Fixes: #13175
srl295
added a commit
that referenced
this issue
Feb 13, 2025
- convert each .abnf to a .pegjs file Fixes: #13175
srl295
added a commit
that referenced
this issue
Feb 14, 2025
- update fetch-latest-cldr.sh - so next time, abnf will get updated. - note, this is abnf from 47 but we’re not doing the full 47 import yet because it's not released. Fixes: feat(developer): utilize CLDR ABNF rules to validate transforms #13175
srl295
added a commit
that referenced
this issue
Feb 14, 2025
- convert each .abnf to a .pegjs file Fixes: #13175
srl295
added a commit
that referenced
this issue
Feb 14, 2025
- just convert over all abnf (as we do with copying imports) - hard coded CLDR version number for now Fixes: #13175
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CLDR now has ABNF rules for transform from= and to= rules.
Use these to validate at the developer side that valid strings are being used.
The text was updated successfully, but these errors were encountered: