🪲 Fix front-end print statement missing warning for music #5488
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR solves the issue of warning messages appearing on music adventures when no print statement is present
In spite of not requiring print statements to output, until now submitting a piece of code to a music adventure without including a print statement would result in a warning such as in the following example:
I have solved the issue by checking whether the adventure has any music before issuing the warning in a similar manner to what is done with adventures including turtles
Fixes #5000
How to test
Follow these steps to verify this PR works as intended:
*Check that no warning appears: