From ab81a481bccfb79e65e404b4efc5a0e5f740074e Mon Sep 17 00:00:00 2001 From: aleph-naught2tog Date: Tue, 13 Nov 2018 22:15:33 -0600 Subject: [PATCH] Fixes broken link The original declaration files link was dead, and the page it had been pointing to now refers us to the `declaration files/Introduction.md`. This will fix the issue mentioned in #28484. --- JavaScript-Language-Service-in-Visual-Studio.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/JavaScript-Language-Service-in-Visual-Studio.md b/JavaScript-Language-Service-in-Visual-Studio.md index c65e867..dd685f9 100644 --- a/JavaScript-Language-Service-in-Visual-Studio.md +++ b/JavaScript-Language-Service-in-Visual-Studio.md @@ -85,7 +85,7 @@ See [this doc](https://github.com/Microsoft/TypeScript/wiki/JsDoc-support-in-Jav #### IntelliSense based on TypeScript Declaration Files -Because JavaScript and TypeScript are now based on the same language service, they are able to interact in a richer way. For example, JavaScript IntelliSense can be provided for values declared in a `.d.ts` file ([more info](https://github.com/Microsoft/TypeScript-Handbook/blob/master/pages/Writing%20Definition%20Files.md)), and types such as interfaces and classes declared in TypeScript are available for use as types in JsDoc comments. +Because JavaScript and TypeScript are now based on the same language service, they are able to interact in a richer way. For example, JavaScript IntelliSense can be provided for values declared in a `.d.ts` file ([more info](https://github.com/Microsoft/TypeScript-Handbook/blob/master/pages/declaration%20files/Introduction.md)), and types such as interfaces and classes declared in TypeScript are available for use as types in JsDoc comments. Below, we show a simple example of a TypeScript definition file providing such type information (via an interface) to a JavaScript file in the same project (using a JsDoc tag).