cadl/packages/typespec-vs
Timothee Guerin 7312314bcb
Remove old message burried in changelog (#2989)
2024-03-05 16:05:57 -08:00
..
scripts 2/3 TypeSpec: Renaming files 2023-02-16 13:07:22 -08:00
src Publish Visual Studio Extension (#2854) 2024-01-30 11:17:38 -08:00
CHANGELOG.json Prepare Publish for January Release (#2816) 2024-01-24 11:14:23 -08:00
CHANGELOG.md Remove old message burried in changelog (#2989) 2024-03-05 16:05:57 -08:00
Directory.Build.rsp 2/3 TypeSpec: Renaming files 2023-02-16 13:07:22 -08:00
LICENSE 2/3 TypeSpec: Renaming files 2023-02-16 13:07:22 -08:00
Microsoft.TypeSpec.VS.sln 2/3 TypeSpec: Renaming files 2023-02-16 13:07:22 -08:00
README.md Publish Visual Studio Extension (#2854) 2024-01-30 11:17:38 -08:00
nuget.config 2/3 TypeSpec: Renaming files 2023-02-16 13:07:22 -08:00
package.json Bump versions for release march 2024 (#2988) 2024-03-05 15:31:47 -08:00
publishManifest.json Publish Visual Studio Extension (#2854) 2024-01-30 11:17:38 -08:00
typespec.pkgdef Adding .cadl & package.json cadlMain back compat support (#1666) 2023-02-24 14:39:43 -06:00

README.md

TypeSpec Language Support for Visual Studio

Repository | Documentation | Issues | Samples

This provides provides TypeSpec language support for Visual Studio.

Features

  • Live diagnostic reporting
  • Syntax highlighting
  • Code completion
  • Code folding
  • Formatting
  • Hover info
  • Rename refactoring
  • Go to definition

Configure TypeSpec Visual Studio Extension

  1. Create a file .vs/VSWorkspaceSettings.json at the root of the project.
  2. Add configuration as key value pair in this file. Example:
{
  "typespec.tsp-server.path": "${workspaceFolder}/my-nested-project/node_modules/@typespec/compiler"
}

TypeSpec wil interpolate a few variables using this pattern ${<name>}. For example ${workspaceFolder}.

Available variables:

  • workspaceFolder: Correspond to the root of your Visual Studio workspace.