-
Notifications
You must be signed in to change notification settings - Fork 481
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
Javalab: Pass execution type parameter to Javabuilder #42938
Conversation
apps/src/javalab/Javalab.js
Outdated
}; | ||
|
||
Javalab.prototype.onTest = function() { | ||
// TODO: Add any necessary pre-run steps here (incrementing attempts count, resetting mini-app, etc) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In onRun
we save the project, reset the mini-app, and increment the attempt count. Do we need to do any of that here as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm ping Hannah and Mike about this (they're not on github often, so it's best to tag them in Slack). We do need to save the project (so Javabuilder can get the right version of the code), and we may want to reset the mini-app, but I have no idea about whether we should record a milestone. Hannah & Mike will likely have opinions here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This passes a new "execution type" parameter to Javabuilder to eventually support running tests and other configurations (see: code-dot-org/javabuilder#136). For now, no behavior should be changed - the
onRun
function now opens a connection to Javabuilder with an execution type of "RUN", and later, theonTest
function can be used to open a connection with an execution type of "TEST".Links
Testing story
Tested locally on All The Things levels Confirmed that standard Javalab behavior is unchanged.
Deployment strategy
Follow-up work
Privacy
Security
Caching
PR Checklist: