Print JSON object in console#175
Merged
Merged
Conversation
DavidOkulski
requested review from
JohYoshidaBCGov,
bzimonjaSDPR,
dbellbro and
saranyaviswam
saranyaviswam
approved these changes
Jan 22, 2026
bzimonjaSDPR
approved these changes
Jan 23, 2026
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
3 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.
What changes did you make?
Parse the JSHandle@object from the browser logs in Pupeteer during backend generation.
Why did you make these changes?
Backend generation works locally, but hangs on this step when doing background generation on OpeShift:
Browser logs: log (Form Loader) raw result: JSHandle@objectNeed to parse the object to see if the corect result is being returned or an error is occurring.
What alternatives did you consider?
None.
Checklist