Fix debugging messages in the formatRenderedProblem
method.
#2662
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.
The
formatRenderedProblem
method of theFormatRenderedProblem
module ensures that thedebug_messages
key of the rendered problem result is an array reference, but checks the wrong thing. It checks if the result itself is an array reference instead of thedebug_messages
hash key of the result. Since the result is always a hash reference and never an array reference, this means that the debugging messages from PG are always wiped out and replaced with a reference to an empty array.This was discovered when investigating #2661. If we want to switch the PG problem editor to using the
debug
output format of theformatRenderedProblem
method we could, but in order to get the benefit of that change we need this.