fix: ensure that codecs for base JS elements are registered

[tbouffard]

Previously, codecs for Object and Array weren't registered when calling registerEditorCodecs.

Summary by CodeRabbit

• Refactor
  • Improved codec registration process by centralizing base codec registration logic
  • Added a mechanism to prevent redundant codec registrations
  • Simplified codec initialization in model and editor registration functions

[coderabbitai]

Walkthrough

The pull request modifies the codec registration process in the serialization module by introducing a new registerBaseCodecs function. This function centralizes the registration of base codecs (empty object and empty array) with a flag to prevent redundant registrations. The changes simplify the existing registerModelCodecs and registerEditorCodecs functions by extracting the base codec registration logic into a separate, reusable function that can be called with an optional force parameter.

Changes

File	Change Summary
packages/core/src/serialization/register.ts	- Added isBaseCodecsRegistered boolean variable - Introduced registerBaseCodecs(force = false) function - Updated registerModelCodecs and registerEditorCodecs to use registerBaseCodecs(force)

Possibly related PRs

• docs: add a Codecs page #524: Documentation updates explaining codec configuration and usage, which complements the new codec registration mechanism introduced in this PR.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9303a85 and 5491f83.

📒 Files selected for processing (1)

• packages/core/src/serialization/register.ts (3 hunks)

🔇 Additional comments (3)

packages/core/src/serialization/register.ts (3)

45-53: Consider concurrency and add documentation for registerBaseCodecs.

This global variable and function approach is convenient, but in multi-threaded or concurrent environments, global state can lead to race conditions if calls happen in parallel. If concurrency is not a concern for your project, this is fine; otherwise, consider adding synchronization safeguards and a brief docstring clarifying how this is intended to be used.

---

101-101: Good practice: centralizing the base codecs registration.

Calling registerBaseCodecs(force) here eliminates repeated logic and ensures consistent codec availability. Good job on keeping the code DRY.

---

148-149: Maintain consistency across registration flows.

Just as with registerModelCodecs, calling registerBaseCodecs(force) helps avoid missing base codecs in editor flows. This further promotes a unified approach for all registration sequences.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.