-
Notifications
You must be signed in to change notification settings - Fork 8
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
PhET-iO API error when using 'screens' query parameter #190
Comments
This apparently does need to be addressed for RC. |
phetsims/tandem#194 has been addressed and verified in master. But I've hit a merge conflict trying to cherry-pick the changes, see phetsims/tandem#194 (comment). I'll need assistance from @zepumph. |
@zepumph provide details on how to resolve merge conflicts in phetsims/tandem#194 (comment), so I'll try again. |
I resolved the merge conflict in phetioApiValidation.js by changing this: this.enabled = assert &&
Tandem.VALIDATION &&
phet.chipper.queryParameters.screens === null &&
phet.chipper.queryParameters.homeScreen; ... to this: this.enabled = assert &&
Tandem. PHET_IO_ENABLED &&
phet.chipper.queryParameters.screens === null &&
phet.chipper.queryParameters.homeScreen; Seems to work OK in ph-scale 1.4 and ph-scale-basics-1.4, but makes me nervous to be doing partial cherry-picks. Ready for testing in next RC. |
This is irrelevant for ph-scale-basics. To verify in the next ph-scale RC:
It is expected that all 3 screens will still be shown in the Studio tree. |
No API error and no console issues, all screens are still showed in the Studio tree but only the name property. |
@brooklynlash You're probably only seeing |
Yes, my mistake. I need to remember to do that next time |
Great, thanks. Closing. |
See phetsims/tandem#194. No idea if I need to address this for ph-scale RC.
The text was updated successfully, but these errors were encountered: