Skip to content

fix: fix the Converting circular structure to JSON error #13482

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from

Conversation

eveningwater
Copy link

@eveningwater eveningwater commented Jun 16, 2025

fix the Converting circular structure to JSON error

Summary by CodeRabbit

  • Bug Fixes
    • Improved handling of unsupported values in display strings by warning and preventing rendering of certain elements.

Copy link

coderabbitai bot commented Jun 16, 2025

Walkthrough

A conditional check was added to the toDisplayString function to detect if the input is a Vue VNode-like object. If so, a warning is logged in development mode and an empty string is returned, preventing further processing of VNode values. No changes were made to function signatures or exports.

Changes

File Change Summary
packages/shared/src/toDisplayString.ts Added isVNodeLike helper, VNode-like check, warning log, and early return in toDisplayString

Poem

A VNode hopped into a string,
But warnings made the bell ring.
"No rendering here!" the message cried,
So out the VNode quickly shied.
Now strings are safe and clear,
With empty returns, there's nothing to fear!
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 532cfae and 10f36c8.

📒 Files selected for processing (1)
  • packages/shared/src/toDisplayString.ts (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules
  • GitHub Check: Header rules
  • GitHub Check: Pages changed

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
packages/shared/src/toDisplayString.ts (1)

20-21: Tighten the helper’s typing & follow house style

isVNodeLike works, but we can give callers a more useful type-guard and stay consistent with the 2-space / spaced-keyword style used elsewhere in this file.

-const isVNodeLike = (val: unknown): boolean =>
-  !!(val && (val as any).__v_isVNode === true)
+const isVNodeLike = (val: unknown): val is { __v_isVNode: true } =>
+  !!(val && (val as any).__v_isVNode === true)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6848b65 and c8b7edf.

📒 Files selected for processing (1)
  • packages/shared/src/toDisplayString.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules
  • GitHub Check: Header rules
  • GitHub Check: Pages changed

Comment on lines +27 to +33
// fix: https://github.com/vuejs/core/issues/13481
if(isVNodeLike(val)){
if(__DEV__){
console.warn('[Vue warn]: Interpolated value is a VNode – this is unsupported and was likely passed by mistake. Returning an empty string.');
}
return '';
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

⚠️ Potential issue

Style nits aside, nested VNodes can still explode JSON.stringify

  1. Minor: the current formatting (if(__DEV__){) diverges from the rest of the file (if (__DEV__) {).
  2. Major: the early return only protects when the root value is a VNode.
      toDisplayString([h('div')]) will still reach JSON.stringify and throw the exact same “Converting circular structure to JSON” error because replacer does not recognise VNodes.

Proposed fix (includes style clean-up + VNode handling in replacer):

@@
-    // fix: https://github.com/vuejs/core/issues/13481
-    if(isVNodeLike(val)){
-      if(__DEV__){
-        console.warn('[Vue warn]: Interpolated value is a VNode – this is unsupported and was likely passed by mistake. Returning an empty string.');
-      }
-      return '';
-   }
+  // #13481 – avoid JSON-stringifying VNodes (circular refs)
+  if (isVNodeLike(val)) {
+    if (__DEV__) {
+      console.warn(
+        '[Vue warn]: Interpolated value is a VNode – this is unsupported ' +
+        'and was likely passed by mistake. Returning an empty string.'
+      )
+    }
+    return ''
+  }
@@
   if (isRef(val)) {
     return replacer(_key, val.value)
+  } else if (isVNodeLike(val)) {
+    // Prevent circular reference blow-ups when VNodes are nested inside
+    // arrays / objects passed to toDisplayString.
+    return '[VNode]'
   } else if (isMap(val)) {
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
// fix: https://github.com/vuejs/core/issues/13481
if(isVNodeLike(val)){
if(__DEV__){
console.warn('[Vue warn]: Interpolated value is a VNode – this is unsupported and was likely passed by mistake. Returning an empty string.');
}
return '';
}
// #13481 – avoid JSON-stringifying VNodes (circular refs)
if (isVNodeLike(val)) {
if (__DEV__) {
console.warn(
'[Vue warn]: Interpolated value is a VNode – this is unsupported ' +
'and was likely passed by mistake. Returning an empty string.'
)
}
return ''
}
if (isRef(val)) {
return replacer(_key, val.value)
} else if (isVNodeLike(val)) {
// Prevent circular reference blow-ups when VNodes are nested inside
// arrays / objects passed to toDisplayString.
return '[VNode]'
} else if (isMap(val)) {
// ...
}
🤖 Prompt for AI Agents
In packages/shared/src/toDisplayString.ts around lines 27 to 33, fix the style
of the if statement to match the file's convention by adding spaces: change
`if(__DEV__){` to `if (__DEV__) {`. Also, extend the VNode handling by updating
the JSON.stringify replacer function to detect and handle nested VNodes,
preventing circular structure errors when VNodes appear inside arrays or
objects. This involves adding a check for VNode-like objects within the replacer
and returning an empty string for them, ensuring no VNode causes JSON.stringify
to throw.

@edison1105
Copy link
Member

edison1105 commented Jun 17, 2025

Thanks for the PR, but I don't think it's worth it.
see #13481 (comment)

@edison1105 edison1105 closed this Jun 17, 2025
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