Skip to content

Log error message as JSON string to actually see what instaql-queries is#2742

Closed
clarkg wants to merge 2 commits into
instantdb:mainfrom
clarkg:main
Closed

Log error message as JSON string to actually see what instaql-queries is#2742
clarkg wants to merge 2 commits into
instantdb:mainfrom
clarkg:main

Conversation

@clarkg

@clarkg clarkg commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Right now instantql-queries is printed as unhelpful [[Object]]

clarkg added 2 commits June 7, 2026 02:32
otherwise `instantql-queries` is being printed as unhelpful `[[Object]]`
Log error message as JSON string
@coderabbitai

coderabbitai Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9820b3a2-578f-41e5-9de7-8ead8a7bedd8

📥 Commits

Reviewing files that changed from the base of the PR and between 25fec97 and 72d063c.

📒 Files selected for processing (1)
  • client/packages/core/src/Reactor.js

📝 Walkthrough

Walkthrough

The _handleReceiveError method in Reactor's error handler is updated to log error messages using pretty-printed JSON formatting. This change improves debuggability by making error payloads human-readable in console output rather than displaying raw object references.

Changes

Error logging improvement

Layer / File(s) Summary
Enhanced error message logging
client/packages/core/src/Reactor.js
The _handleReceiveError method now logs the received error message using JSON.stringify(msg, null, 2) to format the error payload as readable JSON instead of logging the raw msg object.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the main change: converting error message logging to JSON stringification to improve visibility of the instantql-queries object.
Description check ✅ Passed The description is related to the changeset, explaining the problem that the JSON stringification change addresses.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@dwwoelfel

Copy link
Copy Markdown
Contributor

@clarkg would this work for you? #2745

@clarkg

clarkg commented Jun 8, 2026

Copy link
Copy Markdown
Contributor Author

@clarkg would this work for you? #2745

@dwwoelfel that would work tyvm! very kind

@clarkg clarkg closed this Jun 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants