-
-
Notifications
You must be signed in to change notification settings - Fork 130
refactor(developer): rename layr.lists to layr.forms 🔱 #15142
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(developer): rename layr.lists to layr.forms 🔱 #15142
Conversation
The name `form` better represents the semantic meaning of the structure, and reduces confusion with the `list` section and other uses of `list` in KMX+. Test-bot: skip
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
ermshiperete
left a comment
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.
I can see that using form instead of list is better, but I'm still struggling with that term, probably because form has so many different meanings. It's not obvious what's meant with it. Would one of hardware form, hardware, kind, category be better?
developer/src/common/web/utils/src/types/kmx/kmx-plus-builder/build-layr.ts
Outdated
Show resolved
Hide resolved
developer/src/common/web/utils/src/types/kmx/kmx-plus-builder/build-layr.ts
Outdated
Show resolved
Hide resolved
I'm using the terminology from the spec, https://unicode.org/reports/tr35/tr35-keyboards.html#element-layers, where it talks about "This element contains a set of layer elements with a specific physical form factor, whether hardware or touch layout." So agree that 'form' has multiple meanings, but at least this lines up with the spec 😁 |
Co-authored-by: Eberhard Beilharz <ermshiperete@users.noreply.github.com>
The name
formbetter represents the semantic meaning of the structure, and reduces confusion with thelistsection and other uses oflistin KMX+.Test-bot: skip