Skip to content

Conversation

@RodgeFu
Copy link
Contributor

@RodgeFu RodgeFu commented Sep 25, 2025

The change in the PR mainly contains 3 parts:

  1. change to compiler to support async linter, optimize getSignatureHelp and provide LmProvider
  2. change to vscode extension to support custom request for server to call to provide AI capability
  3. A sample linter lib 'azure-linter' providing: (not a good name, just a sample lib to demo linter rules using AI)

How to try it:

  1. install the compiler
  2. install the linter lib
  3. install the vscode extension
  4. Update tspconfig.yaml to include the linter rule like below
linter:
  enable:
    "azure-linter/csharp.naming.boolean-property-starts-with-verb": true
    "azure-linter/csharp.naming.duration-with-unit": true
    "azure-linter/csharp.naming.avoid-too-generic-name": false

** This PR/branch is for trying the impact from async linter rule. Not expected to be merged. If things go well, I will file separated PRs for different feature areas to review and merge.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 25, 2025

❌ There is undocummented changes. Run chronus add to add a changeset or click here.

The following packages have changes but are not documented.

  • @typespec/compiler
  • typespec-vscode
Show changes

@azure-sdk
Copy link
Collaborator

azure-sdk commented Sep 25, 2025

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants