fix: separate model name and namespace on components generator

[rsodre]

Fixes torii sync on Dojo alpha.9

Introduced changes

• generateComponents fix

Checklist

• Linked relevant issue
• Updated relevant documentation
• Added relevant tests
• Add a dedicated CI job for new examples
• Performed self-review of the code

Summary by CodeRabbit

• Improvements
  • Enhanced clarity in model name processing, allowing for better distinction between namespace and model name.
  • Updated output formatting to ensure accurate representation of both namespace and model name in generated components.

[coderabbitai]

Walkthrough

The changes involve modifications to the generateComponents.cjs file, specifically in how model names are processed. The extraction of the model's namespace and name from the model.tag string has been refined, allowing for clearer differentiation between the two. The output formatting has also been updated to reflect these changes, ensuring both the namespace and model name are accurately represented.

Changes

File Path	Change Summary
packages/core/bin/generateComponents.cjs	Updated logic for processing model names by destructuring the model.tag string into modelNamespace and modelNameNoNamespace. Adjusted output formatting to include the new variables.

Poem

In the meadow where bunnies play,
Changes hop in a bright new way.
Names and namespaces, clear as can be,
A joyful dance, oh so free!
With each tweak, we leap and bound,
In code's embrace, new joys are found! 🐇✨

---

Tip

Early access features: disabled

We are currently testing the following features in early access:

• Anthropic claude-3-5-sonnet for code reviews: The new Claude model has stronger code understanding and code generation capabilities than the previous models. We're excited to hear your feedback as we evaluate its performance over the next few days.

Note:

• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
• Please join our Discord Community to provide feedback and report issues on the discussion post.

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 60d08ef and cc672c5.

Files selected for processing (1)

• packages/core/bin/generateComponents.cjs (2 hunks)

Additional comments not posted (2)

packages/core/bin/generateComponents.cjs (2)

85-85: LGTM!

The code change is approved. Destructuring the result of model.tag.split("-") into modelNamespace and modelNameNoNamespace improves the clarity of the code by explicitly separating the namespace and model name.

---

105-106: LGTM!

The code changes are approved. Setting the namespace to modelNamespace and the name to modelNameNoNamespace in the fileContent improves the structure of the generated output by ensuring that both the namespace and the model name are correctly represented.