feat: add debugPrintFollyDynamic helper to debug shadow tree updates

[jpudysz]

Summary

Summary by CodeRabbit

• New Features
  • Added enhanced debug logging for structured data, allowing detailed inspection of object contents in the JavaScript console.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-unistyles-2.0	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 14, 2025 10:22am
react-native-unistyles-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 14, 2025 10:22am

[coderabbitai]

Walkthrough

A new inline function, debugPrintFollyDynamic, was introduced in the margelo::nitro::unistyles::helpers namespace within the Helpers.h header. This function enables structured logging of folly::dynamic objects to the JavaScript console, supporting recursive parsing of various dynamic types.

Changes

File(s)	Change Summary
cxx/common/Helpers.h	Added debugPrintFollyDynamic function for structured debug logging of folly::dynamic objects.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/folly

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 auto-generate unit tests to generate unit tests for 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.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

cxx/common/Helpers.h (1)

321-366: Consider adding error handling for dynamic type conversion.

The parser lambda handles most folly::dynamic types correctly, but consider adding error handling around type conversions to prevent potential crashes during debugging.

For safer type handling, consider wrapping the conversions:

        if (value.isBool()) {
-            std::string output = key + ": " + (value.getBool() ? "true" : "false");
+            std::string output = key + ": " + (value.asBool() ? "true" : "false");
            log.call(rt, output);
            return;
        }

Also, consider adding a try-catch block around the type conversions to handle any unexpected cases gracefully during debugging.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between de519c9 and 80c633b.

⛔ Files ignored due to path filters (1)

• example/ios/Podfile.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• cxx/common/Helpers.h (1 hunks)

🔇 Additional comments (2)

cxx/common/Helpers.h (2)

317-319: Good implementation approach - consistent with existing patterns.

The function signature and console setup follow the established patterns in the codebase, maintaining consistency with the existing debugPrintJSIObject function.

---

368-378: Proper header/footer structure and root object handling.

The main logic correctly handles both object and non-object root values, and the header/footer structure matches the existing JSI debug function pattern.