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

Javalab: Pass execution type parameter to Javabuilder #42938

Merged
merged 5 commits into from
Oct 13, 2021

Conversation

sanchitmalhotra126
Copy link
Contributor

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, the onTest 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:

  • Tests provide adequate coverage
  • Privacy and Security impacts have been assessed
  • Code is well-commented
  • New features are translatable or updates will not break translations
  • Relevant documentation has been added or updated
  • User impact is well-understood and desirable
  • Pull Request is labeled appropriately
  • Follow-up work items (including potential tech debt) are tracked and linked

@sanchitmalhotra126 sanchitmalhotra126 requested a review from a team October 11, 2021 23:57
};

Javalab.prototype.onTest = function() {
// TODO: Add any necessary pre-run steps here (incrementing attempts count, resetting mini-app, etc)
Copy link
Contributor Author

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?

Copy link
Contributor

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.

Copy link
Contributor

@jmkulwik jmkulwik left a comment

Choose a reason for hiding this comment

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

LGTM!

@sanchitmalhotra126 sanchitmalhotra126 merged commit a7e55d8 into staging Oct 13, 2021
@sanchitmalhotra126 sanchitmalhotra126 deleted the javabuilder-test branch October 13, 2021 23:19
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

3 participants