-
Notifications
You must be signed in to change notification settings - Fork 14
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
Can phet.chipper.stings.get
and string!getStringFromFileContents
be simplified?
#796
Comments
…ete chipper-strings.js; mapString doesn't need stringTest parameter, #796
In the above commit I did the following work on the a11ystring-plugin branch:
The goal of these changes was to help with clarity, and to simplify the code that is run between built mode and requirejs. Both call mapString, but before it was pretty confusing how the process for loading the built strings worked. I think in-lining the method previously defined in Note this is all on the branch, because there are too many changes about strings on that branch for me to touch master right now. @jonathanolson you have the most commits on chipper-strings.js, would you mind reviewing? Does the change to |
I checked over the commit. It looks good, and I like the changes. Separating out the second parameter to a closure variable seems perfect. |
Excellent! I will close this issue, but it won't be on master for now. see #777 |
From work with @samreid over in #786, I wonder if these two functions can be combined somehow. These two functions do similar things, but one for requirejs and the other for built mode. I'm especially looking at how both call mapString. Perhaps this could be simplified into a function in ChipperStringUtils.js or something.
The text was updated successfully, but these errors were encountered: