-
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
Util vs Utils #966
Comments
@chrisklus said:
I don't think the name should be based on how many methods are in the file. We don't want to have to change (or remember to change) a name when the number of methods is increased from 1 to > 1. @samreid asked:
Plurals seems more correct to me. But I don't feel to strongly about this issue, if the consensus ends up being "do nothing". |
My feelings mirror @pixelzoom's, with the note that now I prefer files named with the "theme" of what they provide. If things provide many different themes (DOT/Util), I'd prefer (long-term) to break them out into multiple files. For example in DOT/Util, I'd want to at least separate e.g. |
Based on prior remarks, this seems like we have the correct name in the public PhET-iO API. Therefore, this issue would not block publication. |
12/13/18 dev meeting: The majority agrees with keeping a "Utils" naming convention. @samreid has volunteered to make refactors. |
Signed-off-by: Chris Malley <[email protected]>
@samreid FYI... I converted the "singular" list in #966 (comment) into a check list. And I took care of my sims. |
I made these changes in my working copy and ran a full aqua an phet brand. No problems noted. I sent the following message to slack:
|
So everything in the checklist in #966 (comment) can be checked? |
I think my commits + pushes will cover the entire checklist. |
After noticing that my working copy had text like "Utilsities" in the iOS repo, I realized I'll need to try this again. |
I message on Slack:
But on second thought it will be safer to wait until after July 31. Going on hold for a while. |
Renames completed and I added a bad-text rule to prevent new modules from being named ending in UPDATE: I should note local aqua and lint are passing. |
CT seems OK and the new lint rule seems OK, closing. |
From https://github.com/phetsims/phet-io/issues/1366
@pixelzoom said:
@chrisklus replied:
We should make a choice on this and be consistent, in the near future for PhET-iO API.
Here is a list of the current names we use for this.
Util, singular:
~/github$ find . -not -path "*node_modules*" -name "*Util.js"
Utils, plural:
@pixelzoom what do you recommend?
The text was updated successfully, but these errors were encountered: