Skip to content

Conversation

@Sysix
Copy link
Member

@Sysix Sysix commented Apr 30, 2025

Summary by CodeRabbit

  • New Features
    • Added support for activating the extension when working with Astro language files in VSCode.

@github-actions github-actions bot added A-editor Area - Editor and Language Server C-bug Category - Bug labels Apr 30, 2025
Copy link
Member Author

Sysix commented Apr 30, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@Sysix Sysix marked this pull request as ready for review April 30, 2025 13:58
@camc314 camc314 added the 0-merge Merge with Graphite Merge Queue label Apr 30, 2025
@coderabbitai
Copy link

coderabbitai bot commented Apr 30, 2025

Walkthrough

The change updates the VSCode extension's activation events to include support for the "astro" language. Now, the extension will activate when files of either the Svelte or Astro languages are opened or edited. No other modifications to functionality, commands, configuration, or dependencies were made.

Changes

File(s) Change Summary
editors/vscode/package.json Added "onLanguage:astro" to the activation events for the extension.

Poem

In VSCode's warren, new files appear,
Astro joins Svelte—let's give a cheer!
With every hop, the extension wakes,
For stars and components, whatever it takes.
🐇✨


📜 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 0931bf9 and 4ee95ec.

📒 Files selected for processing (1)
  • editors/vscode/package.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • editors/vscode/package.json

🪧 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 generate sequence diagram to generate a sequence diagram of the changes in 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.

Copy link
Contributor

camc314 commented Apr 30, 2025

Merge activity

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
editors/vscode/package.json (1)

37-37: Enable Astro activation event
Adding "onLanguage:astro" triggers activation for Astro files as intended. Please verify that "astro" matches VS Code’s built-in language ID, and consider updating the README or extension documentation to mention Astro support.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8bfd5e3 and 3dc5327.

📒 Files selected for processing (1)
  • editors/vscode/package.json (1 hunks)
🔇 Additional comments (1)
editors/vscode/package.json (1)

36-36: Enable Svelte activation event
Including "onLanguage:svelte" correctly ensures the extension activates when opening Svelte files.

graphite-app bot pushed a commit that referenced this pull request Apr 30, 2025
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

- **New Features**
  - Added support for activating the extension when working with Astro language files in VSCode.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@graphite-app graphite-app bot force-pushed the 04-30-fix_editor_activate_extension_when_astro_files_are_opened_too branch from 3dc5327 to 0931bf9 Compare April 30, 2025 14:13
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

- **New Features**
  - Added support for activating the extension when working with Astro language files in VSCode.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@graphite-app graphite-app bot force-pushed the 04-30-fix_editor_activate_extension_when_astro_files_are_opened_too branch from 0931bf9 to 4ee95ec Compare April 30, 2025 14:25
@graphite-app graphite-app bot merged commit 4ee95ec into main Apr 30, 2025
16 checks passed
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label Apr 30, 2025
@graphite-app graphite-app bot deleted the 04-30-fix_editor_activate_extension_when_astro_files_are_opened_too branch April 30, 2025 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-editor Area - Editor and Language Server C-bug Category - Bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants