-
Notifications
You must be signed in to change notification settings - Fork 2
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
Checkbox is one word #910
Comments
Google votes 9,020,000 votes for "check box" and 25,300,000 votes for "checkbox". |
Our codebase has 1176 occurrences of |
On MDN https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement "checkbox" appears 7 times and "check box" appears 0 times. Likewise the spec refers to checkbox (17 times) and never "check box". Note these are for the HTML element not the scenery component, but it seems we should follow the same logic. I'm inclined to go with "checkbox". I'll add lint rules and look at updating these. |
I noticed that @pixelzoom used "Check box" and CheckBox in sun--it would be good to get him to sign off before we start making changes. @pixelzoom can you please review this issue and comment? |
I'm fine with whichever you choose. Is this and #909 primarily motivated by consistency of phetioIDs? |
Btw... I've used "check box" mainly for consistency with the UI toolkits I've used in the past. E.g. JCheckBox (Java Swing), QCheckBox (Qt), CheckBox (X/Motif), ... |
This issue was discovered while working on making It seems odd because Java has Iterating through top hits in google search for "checkbox API":
I'm still leaning toward the one-word solution. I'll add a lint rule and start converting usages. |
After adding this lint rule, lint-everything reports:
This may take some time unless we can take error-free shortcuts. |
I was able to pull changes on my Windows machine, thanks @samreid. Closing this isssue. |
Similar to #909 it seems we should make checkbox be one word and avoid "checkBox" or "check box".
Having a uniform custom will make it easier to avoid casing mismatch bugs, and will help us keep a consistent API for sim development and for PhET-iO clients.
The text was updated successfully, but these errors were encountered: