[Sprite Lab] Workspace alert for execution errors

[mikeharv]

Context and summary: If a behavior or function is undefined in a student's Blockly code, calling it results in an execution error. There is no user-facing console in Sprite Lab so all feedback is hidden. Because execution errors cause Sprite Lab to crash, these issues are often misdiagnosed by users as "disappearing sprites". Ideally, we want to prevent student programs from getting into this kind of state. In the meantime, we can alert the user if they do get into this state.
This change utilizes WorkspaceAlert which we also use across various labs for other purposes, such as when warning the student about code changes while the program is running.

Function Example:

Behavior Example:

Animation to show non-immediate error:

Links

• jira ticket: STAR-2099

Testing story

This change would not be used in Game Lab, because there is a Debug Console already available:

This change would be easy to add to Poetry, but is likely not needed. Behaviors are only selectable by drop-down and cannot be edited or deleted. Functions are also not available to students.

Deployment strategy

Follow-up work

STAR-121: [Sprite Lab] Prevent broken behaviors from causing a crash

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

[epeach]

This looks good! Do we want to cover this with a test in SpriteLabTest.js?

[maddiedierker]

naming nit: this function makes an assumption about what it should do ("if i hit an execution error, alert the student"). there are a few problems with this assumption:

• the user won't always be a student
• changing how we react to execution errors would require changing the same of this function (what if, in the future, instead of alerting, we decide to log to the debug console?)
• this code shouldn't really care how the error is handled, but rather that consumers who do care can handle it however they want

[maddiedierker]

nit: always prefer returning early to reduce nesting (which improves readability) over wrapping all functionality in a conditional

if (!msg) {
  return;
}

// now everything else can be at this indentation level

[maddiedierker]

this context is useful, but it should probably live in SpriteLab.js

[KylieModen]

LGTM - workspace alert looks great, ahead of ship let's notify the curriculum team of the change in their slack channel

[maddiedierker]

🎉 great work, mike -- diving into the JSInterpreter code was really complicated and you did a great job navigating it!