feat: Enhance C# Package Autocomplete with SDK and Property directives support

[TarasKovalenko]

feat: Enhance C# Package Autocomplete with SDK and Property directives support

• Updated package.json to reflect new version and expanded description.
• Introduced new interfaces for SDK and Property information.
• Refactored completion provider to handle #:sdk and #:property directives.
• Added common SDKs and MSBuild properties for autocompletion.
• Improved hover provider to display detailed information for SDKs and properties.
• Updated activation events to trigger on new directive formats.
• Enhanced documentation and examples for better user guidance.

Summary by CodeRabbit

• New Features

  • Added directive-based IntelliSense and hover support for #:package, #:sdk, and #:property.
  • Enhanced NuGet package search with richer details, version suggestions, caching, and download-based ranking.
  • Hovers now show metadata and helpful links for packages, SDKs, and MSBuild properties.

• Documentation

  • Expanded README with Directive Reference, Advanced Configuration, testing guidance, and broader examples.
  • Updated setup for .NET 10 preview and file-based apps; refreshed extension naming/branding.

• Chores

  • Bumped version to 1.0.0 and updated dependencies.
  • Raised minimum VS Code version to 1.103.0.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Adds directive-based functionality to the VS Code extension, expanding from package-only to support for #:package, #:sdk, and #:property completions and hovers. Updates README to document new directives and workflows. Adjusts package metadata and tooling versions. Activation now registers new directive-aware completion and hover providers with caching and timeout handling.

Changes

Cohort / File(s)	Summary
Documentation README.md	Rewrites and expands docs to cover file-based directives: adds sections for Package Management, SDK Selection, MSBuild Properties, Directive Reference, and advanced workflows. Updates prerequisites to .NET 10 preview and VS Code requirements; refreshes links, roadmap, and metadata.
Packaging & Tooling package.json	Updates description, version to 1.0.0, keywords (adds sdk), VS Code engine to ^1.103.0; bumps dev dependencies (@types/vscode, @types/node, typescript, @vscode/vsce) and runtime axios. No code changes.
Extension Logic src/extension.ts	Replaces package-only providers with directive-aware providers: supports #:package, #:sdk, #:property for completions and hovers. Adds static SDK/property data, caching, timeout for NuGet lookups, routing by directive, and richer item docs. Activation updated to new triggers.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor U as User
  participant VS as VS Code
  participant EP as Extension (Completion Provider)
  participant NU as NuGet API
  note over U,VS: Typing in C# file-based app
  U->>VS: Type "#:..." or continue after directive
  VS->>EP: Request completions (position, line)
  EP->>EP: Parse directive (#:package|#:sdk|#:property)
  alt #:package
    EP->>EP: If after package name: suggest versions
    EP->>NU: Search packages (with cache, 5s timeout)
    NU-->>EP: Package list
    EP-->>VS: Completion items (sorted by downloads)
  else #:sdk
    EP->>EP: Lookup COMMON_SDKS
    EP-->>VS: SDK completion items (static docs)
  else #:property
    EP->>EP: If name context → COMMON_PROPERTIES
    EP->>EP: If value context → possible values/default
    EP-->>VS: Property name/value completion items
  end
  VS-->>U: Show suggestions

Loading

sequenceDiagram
  autonumber
  actor U as User
  participant VS as VS Code
  participant HP as Extension (Hover Provider)
  participant NU as NuGet API
  U->>VS: Hover over directive/value
  VS->>HP: Hover request (range, text)
  HP->>HP: Identify directive context
  alt #:package
    HP->>NU: Fetch package metadata (5s timeout)
    NU-->>HP: Description, version, downloads, link
    HP-->>VS: Hover markdown with package info
  else #:sdk
    HP->>HP: findSdkInfo()
    HP-->>VS: Hover markdown with SDK metadata
  else #:property
    HP->>HP: findPropertyInfo()
    HP-->>VS: Hover markdown with property info
  end
  VS-->>U: Show hover

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Poem

A nibble of colons, a whisker of hash,
I hop through directives with zippy dash.
Packages, SDKs, properties too—
Autocomplete fields in morning dew.
Caches are warm, timeouts behave,
Hovering hints a user will crave.
Thump-thump—v1.0, onward we rave! 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

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 415b86e and 82b124c.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• README.md (4 hunks)
• package.json (3 hunks)
• src/extension.ts (6 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Taras/v.1.0.0

---

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.

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

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.