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

Gamelab respect debuggerDisabled #20245

Merged
merged 5 commits into from Jan 30, 2018
Merged

Conversation

cpirich
Copy link
Contributor

@cpirich cpirich commented Jan 26, 2018

  • Gamelab now honors the debuggerDisabled level flag to determine when the debugger is disabled. All new levels created will have the debugger enabled by default. To simplify the transition, we've disabled the debugger in all of the existing Gamelab curriculum levels and level builders can go back and selectively choose to enable it where it makes sense.
  • Fixed a long-standing debugger bug where the last statement remains highlighted in droplet/ace after resuming the debugger (e.g. pressing "Continue" after being stopped at a breakpoint)
  • Added debugger highlighting tests that verify proper calls to ace's addMarker and removeMarker

// NOTE: We will go back to using !config.level.debuggerDisabled soon,
// but are testing with project levels only for now
var breakpointsEnabled = config.level.isProjectLevel;
var breakpointsEnabled = !config.level.debuggerDisabled;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This files looks good.

// If we were running atMaxSpeed and just reached a breakpoint, the
// code may not be selected in the editor, so do it now:
this.selectCurrentCode();
if (atMaxSpeed) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to see the highlighting bug behavior tested, but code looks good.

@caleybrock
Copy link
Contributor

The preferred method of updating the levels would be to run a script on the LB machine since this can cause conflicts, but it looks like there aren't any Game Lab levels being edited on LB right now, so I think this could work.

@caleybrock
Copy link
Contributor

Looks like circle has a JS interpretor failure, related to this change?

Copy link
Contributor

@caleybrock caleybrock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm guessing Circle just failed to run properly and you just need to re-build it.

@cpirich
Copy link
Contributor Author

cpirich commented Jan 29, 2018

Trying to re-build on CircleCI - the last run hit this error inside appLabgameLabTest.log:

29 01 2018 18:34:52.419:ERROR [launcher]: PhantomJS crashed.

@cpirich cpirich merged commit 60bb4af into staging Jan 30, 2018
@cpirich cpirich deleted the gamelab_respect_debugger_disabled branch January 30, 2018 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants