Added content for new numscript interpreter

[Amruta-Ranade]

No description provided.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 19, 2025 6:38am

[coderabbitai]

Walkthrough

The documentation has been updated to clarify that Ledger v2.2 now supports two versions of the Numscript interpreter. The default interpreter integrated into the Ledger service remains unchanged and will not receive further updates, while a new, portable interpreter requires manual activation and will be actively maintained. The changes include detailed instructions on enabling the new interpreter via specific settings and note that the Numscript playground uses the new interpreter. The versioned documentation also updates the title from "Embedding" to "Selecting an interpreter."

Changes

File(s)	Change Summary
docs/.../embedding.mdx versioned_docs/.../embedding.mdx	Clarified dual interpreter approach: the default interpreter (integrated, static) versus a new portable interpreter (manual activation, maintained). The versioned doc now has an updated title and activation instructions for experimental features.
sidebars.ts	Added a new label "Selecting an interpreter" to the sidebar configuration for improved navigation regarding interpreter selection in the Numscript category.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant LedgerService as Ledger Service
    participant Interpreter

    User->>LedgerService: Access Numscript functionality
    LedgerService->>Interpreter: Use default interpreter (auto-enabled)
    Note over LedgerService,Interpreter: Original interpreter is static
    User->>LedgerService: Enable experimental features settings
    LedgerService->>Interpreter: Activate new portable interpreter
    Interpreter-->>LedgerService: Process updated logic
    LedgerService-->>User: Display Numscript output (playground may differ)

Loading

Poem

A rabbit hops with glee,
Two scripts in harmony we see,
One stays still with the old lore,
The new one’s active, offering more,
Enable the drift, adjust the fate,
Ledger dances to a versatile state!
🐇✨ Enjoy the update!

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 abd0249 and 9bc9f8d.

📒 Files selected for processing (2)

• docs/numscript/embedding.mdx (1 hunks)
• sidebars.ts (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/numscript/embedding.mdx

🔇 Additional comments (1)

sidebars.ts (1)

213-213: Label update looks good and matches document content changes.

The updated label "Selecting an interpreter" provides clear navigation to information about the two Numscript interpreter versions mentioned in the AI summary. This change properly reflects the updated content in the document and maintains sidebar navigation consistency.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.
• @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.