Skip to content
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

Code review for E6 module work #872

Closed
jonathanolson opened this issue Feb 6, 2020 · 22 comments
Closed

Code review for E6 module work #872

jonathanolson opened this issue Feb 6, 2020 · 22 comments

Comments

@jonathanolson
Copy link
Contributor

(SR, CM, JB? code review, 4-8 hours) [sprintable, pre-publication] Code quality for modulify and the preprocessed modules, the revisions in the chipper build, and the webpack file: Much of the code is prototype-oriented. This is fine for tasks like grunt migrate which will ultimately be deleted after we run it once. But for grunt modulify and the JS harnesses for images, audio, text, etc should be brought to production standards.
Inline templates in modulify should be top level template files
JO: I would prefer grunt modulify would just change the repo that it is run in, and it should be included as part of grunt update

Once things are more solidified, we should review all changed chipper files and make sure they are up to our standards.

@jbphet
Copy link
Contributor

jbphet commented Feb 19, 2020

@jonathanolson

Once things are more solidified, we should review all changed chipper files and make sure they are up to our standards.

This issue is assigned to me, but I'm not clear on what I need to do to address it. It almost sounds like it's not quite ready for review. @jonathanolson - can you please clarify?

@jonathanolson
Copy link
Contributor Author

It sounds like it's not ready yet, presumably this would be done a bit more during the "sprint"? It's unclear and very broad to me.

@pixelzoom pixelzoom changed the title Code quality check and reviews for es6 module work Code review for E6 module work Feb 25, 2020
@chrisklus
Copy link
Contributor

chrisklus commented Feb 26, 2020

Code to review:

in joist:

  • SimLauncher.js

in chipper:

samreid added a commit that referenced this issue Feb 26, 2020
@pixelzoom
Copy link
Contributor

@ariel-phet Before someone(s) are assigned to code review, we should confirm that the authors have done a review themselves using the CRC.

@pixelzoom pixelzoom removed their assignment Mar 3, 2020
@jonathanolson
Copy link
Contributor Author

reportUnusedMedia/reportUnusedStrings are commented out in buildRunnable, otherwise I believe the code I wrote is ready to review.

@jonathanolson jonathanolson removed their assignment Mar 5, 2020
@pixelzoom
Copy link
Contributor

3/5/20 dev meeting

@mattpen
Copy link
Contributor

mattpen commented Mar 19, 2020

3/19 dev meeting:

@samreid still needs to self-review modulify.js

@Denz1994 will start review of buildRunnable.js, webpackBuild.js, and Gruntfile.js.

@jonathanolson said that most recent changes should be g2g, but there may be old changes that are not up to standards.

samreid added a commit that referenced this issue Mar 24, 2020
@samreid
Copy link
Member

samreid commented Mar 24, 2020

modulify.js is now ready for code review. Please note I added a few questions for the reviewer in comments.

@samreid samreid removed their assignment Mar 24, 2020
@Denz1994
Copy link
Contributor

Denz1994 commented Mar 25, 2020

I reviewed the code that was relevant to webpack in buildRunnable.js chipper/gruntfile.js and webpackBuild.js. There were only a few suggestions in the REVIEW comments added (nothing major). The grunt webpack-dev-server help doc was clear and all the options documented were tested. I will reassign to @jonathanolson to address the comments.

@samreid
Copy link
Member

samreid commented Apr 5, 2020

Mipmaps failed for some images, via the interlacing pattern described in #831. I wasn't sure how throw interplayed with async so I tried removing the try/catch and adding a manual test throw new Error() and it had the desired behavior. I'll commit this change.

samreid added a commit that referenced this issue Apr 5, 2020
@samreid
Copy link
Member

samreid commented Apr 5, 2020

Should modulifyFile (in modulify.js) be simplified with logic? This looks fine to leave as-is for me.

Thanks, I removed those comments.

@samreid samreid assigned jonathanolson and unassigned samreid Apr 5, 2020
@Denz1994 Denz1994 mentioned this issue Apr 7, 2020
5 tasks
@Denz1994
Copy link
Contributor

Denz1994 commented Apr 7, 2020

Review comments for sortImports.js have been added to #930.

@Denz1994
Copy link
Contributor

Denz1994 commented Apr 9, 2020

From Dev Meeting 04/09/2020:

I'll review generateDevelopmentHTML.js and generateTestHTML.js this week. @jonathanolson Will respond to review statements in sortImports.js.

@Denz1994
Copy link
Contributor

I've started reviewing getInitializationScript.js and buildStandAlone.js. I'll add SimLauncher.js as a priority as well. These files should be reviewed by Friday.

@samreid
Copy link
Member

samreid commented Apr 23, 2020

SimLauncher has many changes in a branch, see phetsims/joist#621 that will be moved to master soon.

@zepumph
Copy link
Member

zepumph commented Apr 23, 2020

From dev meeting today, @Denz1994 will wait on reviewing SimLauncher.js until @samreid merges those changes.

@samreid
Copy link
Member

samreid commented Apr 24, 2020

I addressed review feedback and moved SimLauncher to master.

@Denz1994
Copy link
Contributor

Denz1994 commented May 7, 2020

The last file to review is modulify.js. I'll get to it this week to finish off this chip away.

@Denz1994 Denz1994 mentioned this issue May 14, 2020
12 tasks
@Denz1994
Copy link
Contributor

Denz1994 commented May 14, 2020

All the files listed in #872 (comment) were reviewed or have their own code review issues.

@Denz1994 Denz1994 removed their assignment May 14, 2020
@jonathanolson
Copy link
Contributor Author

Looks like everything is in remaining other issues, closing here. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants