-
-
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
refactor(common): move remaining LDML keyboard types into LdmlKeyboardTypes
#12713
Conversation
…rdTypes` Follows: #12712
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
*/ | ||
export { UnicodeSetParser, UnicodeSet } from './ldml-keyboard/unicodeset-parser-api.js'; | ||
export { VariableParser, MarkerParser } from './ldml-keyboard/pattern-parser.js'; | ||
export { ElementString } from './kmx/kmx-plus/element-string.js'; |
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.
Should this be separate from LdmlKeyboardTypes
?
In #12712, I thought I saw ElementString
exported separately from LexicalModelTypes
.
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.
No, ElementString
is not exported from LexicalModelTypes
. There is just a unit test that refers to ElementString
which was impacted by the update in #12712.
There's a bit of fuzziness between KMXPlus and LDMLKeyboard (because KMXPlus is an implementation for LDMLKeyboard spec) and I think for now, the layout I have is probably oaky.
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.
lgtm
Changes in this pull request will be available for download in Keyman version 18.0.146-alpha |
Follows: #12712
@keymanapp-test-bot skip