Fix handling of non-object troubleshooting data - #7826
Open
vichekaoeun wants to merge 1 commit into
Open
Conversation
Contributor
|
Should we also add a check for this to |
Contributor
Author
|
yes I think that would make sense but I think it could go into a separate function like clean_troubleshooting since it would mix unrelated issues to the wrong field otherwise. |
vichekaoeun
force-pushed
the
fix-troubleshoot-validation
branch
from
August 13, 2026 01:03
e4f0f63 to
ce4ca5b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolved bug #3116 causing 500 error when troubleshooting data contains JSON that is not an object. Added tests for non-object JSON on form