fix: vscode extension syntax language id

[ymc9]

Summary by CodeRabbit

• Chores
  • Bumped the VS Code extension version to 3.0.6.
  • Updated the grammar scope name for the zmodel-v3 language to "source.zmodel-v3".

[coderabbitai]

Walkthrough

Updates VSCode extension manifest: increments version to 3.0.6 and changes the zmodel-v3 grammar scope name from "source.zmodel" to "source.zmodel-v3".

Changes

Cohort / File(s)	Summary of changes
VSCode extension manifest packages/ide/vscode/package.json	Bumped version 3.0.5 → 3.0.6; updated contributes.grammars[*].scopeName for zmodel-v3 from "source.zmodel" → "source.zmodel-v3".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: separate extension and language id for vscode extension #217 — Migrates VSCode extension/language id to "zmodel-v3", aligning with the grammar scope change here.
• merge dev to main #228 — Updates extension version and aligns ZModel identifiers; complements this grammar scopeName update.

Poem

I twitch my whiskers, version hops to six,
New scope in burrows: zmodel-v3 clicks.
Tiny nibble, tidy trail, no fuss,
Syntax seeds planted—carrots for us.
Hop, save, shine—extensions in the mix! 🥕✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/vscode-language-id

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[Copilot]

Pull Request Overview

This PR fixes the syntax language identifier for the ZenStack VSCode extension by updating the scopeName to properly align with the language ID and incrementing the version number.

• Updates the scopeName from "source.zmodel" to "source.zmodel-v3" to match the language ID
• Increments the extension version from 3.0.5 to 3.0.6

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[claude]

Claude finished @ymc9's task —— View job

---

PR Review: VSCode Extension Syntax Language ID Fix

I've reviewed this PR that fixes the VSCode extension syntax language identifier. Here's my comprehensive analysis:

Todo List:

• Read the modified package.json file
• Analyze the scopeName and version changes
• Review for code quality and best practices
• Check for potential issues or security concerns
• Provide comprehensive feedback

Summary of Changes

The PR makes two focused changes to packages/ide/vscode/package.json:

1. Version bump: 3.0.5 → 3.0.6 (line 4)
2. ScopeName alignment: source.zmodel → source.zmodel-v3 (line 78)

Code Quality & Best Practices ✅

Excellent alignment and consistency:

• The scopeName change properly aligns with the language.id (zmodel-v3) declared on line 60
• This follows VSCode extension best practices where scopeName should correspond to the language identifier
• The version increment follows semantic versioning for a patch fix

Configuration consistency:

• Language ID: zmodel-v3
• Scope Name: source.zmodel-v3
• Activation Event: onLanguage:zmodel-v3
• All three now consistently reference the same identifier

Potential Issues ⚠️

Missing syntax grammar file:

• The package.json references ./syntaxes/zmodel.tmLanguage.json (line 79), but this file doesn't appear to exist in the repository
• This could cause the syntax highlighting to fail entirely
• Recommendation: Verify the syntax grammar file exists or update the path

No description in PR:

• While the change is straightforward, a brief description of why this fix was needed would be helpful for future reference

Performance Considerations ✅

• Changes are configuration-only with no performance impact
• VSCode will load the language configuration efficiently

Security Concerns ✅

• No security issues identified
• Changes are limited to language identifier configuration
• No external dependencies or executable code modifications

Test Coverage 📝

Recommendations for testing:

• Verify syntax highlighting works correctly with .zmodel files
• Test that VSCode properly recognizes the language for files with the .zmodel extension
• Confirm language features (if any) activate correctly with the new scope name

Additional Observations

Positive aspects:

• Focused, surgical fix addressing a specific configuration mismatch
• Proper semantic versioning
• Maintains backward compatibility for file extensions
• Clean, consistent naming convention

Questions for consideration:

• Was there a specific issue this fixes (syntax highlighting not working, IntelliSense problems, etc.)?
• Should there be a changelog entry documenting this fix?

Overall Assessment: ✅ APPROVED

This is a well-executed fix that properly aligns the VSCode extension's language configuration. The changes are minimal, focused, and follow VSCode extension best practices. The only concern is the potentially missing syntax grammar file, which should be verified.

Recommendation: Merge after confirming the syntax grammar file exists and syntax highlighting works correctly.

[claude]

Claude finished @ymc9's task —— View job

---

PR Review: VSCode Extension Syntax Language ID Fix

I've reviewed this PR that fixes the VSCode extension syntax language identifier. Here's my comprehensive analysis:

Todo List:

• Read the modified package.json file
• Analyze the scopeName and version changes
• Review for code quality and best practices
• Check for potential issues or security concerns
• Provide comprehensive feedback

Summary of Changes

The PR makes two focused changes to packages/ide/vscode/package.json:

1. Version bump: 3.0.5 → 3.0.6 (line 4)
2. ScopeName alignment: source.zmodel → source.zmodel-v3 (line 78)

Code Quality & Best Practices ✅

Excellent alignment and consistency:

• The scopeName change properly aligns with the language.id (zmodel-v3) declared on line 60
• This follows VSCode extension best practices where scopeName should correspond to the language identifier
• The version increment follows semantic versioning for a patch fix

Configuration consistency:

• Language ID: zmodel-v3
• Scope Name: source.zmodel-v3
• Activation Event: onLanguage:zmodel-v3
• All three now consistently reference the same identifier

Potential Issues ⚠️

Missing syntax grammar file:

• The package.json references ./syntaxes/zmodel.tmLanguage.json (line 79), but this file doesn't appear to exist in the repository
• This could cause the syntax highlighting to fail entirely
• Recommendation: Verify the syntax grammar file exists or update the path

No description in PR:

• While the change is straightforward, a brief description of why this fix was needed would be helpful for future reference

Performance Considerations ✅

• Changes are configuration-only with no performance impact
• VSCode will load the language configuration efficiently

Security Concerns ✅

• No security issues identified
• Changes are limited to language identifier configuration
• No external dependencies or executable code modifications

Test Coverage 📝

Recommendations for testing:

• Verify syntax highlighting works correctly with .zmodel files
• Test that VSCode properly recognizes the language for files with the .zmodel extension
• Confirm language features (if any) activate correctly with the new scope name

Additional Observations

Positive aspects:

• Focused, surgical fix addressing a specific configuration mismatch
• Proper semantic versioning
• Maintains backward compatibility for file extensions
• Clean, consistent naming convention

Questions for consideration:

• Was there a specific issue this fixes (syntax highlighting not working, IntelliSense problems, etc.)?
• Should there be a changelog entry documenting this fix?

Overall Assessment: ✅ APPROVED

This is a well-executed fix that properly aligns the VSCode extension's language configuration. The changes are minimal, focused, and follow VSCode extension best practices. The only concern is the potentially missing syntax grammar file, which should be verified.

Recommendation: Merge after confirming the syntax grammar file exists and syntax highlighting works correctly.

---

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e013774 and df82fd8.

📒 Files selected for processing (1)

• packages/ide/vscode/package.json (2 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

{packages,samples,tests}/**

📄 CodeRabbit inference engine (CLAUDE.md)

Packages are located in packages/, samples/, and tests/

Files:

• packages/ide/vscode/package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build-test (20.x)

🔇 Additional comments (1)

packages/ide/vscode/package.json (1)

4-4: Approve version bump; update CHANGELOG & verify packaging
Version in package.json is correctly set to 3.0.6—ensure the scope name change is noted in CHANGELOG and release notes. Please run the build and vsce package scripts locally in packages/ide/vscode to confirm the manifest/version are correctly applied.