You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example, the type def Props fails because of the intersection syntax, which is not supported by JSDoc:
{/** @typedef { { foo: number } & { bar: number } } Props *//** @type {function(Props): Props} */constfn=props=>props;fn({foo: 'x'});// <-- expected error, got none}
Is TypeScript planning to extend the JSDoc syntax to support TypeScript syntax within the comments, or is it only following the official JSDoc standard?
For context, this would be useful because we are gradually introducing TypeScript to our codebase via checkJs. As a workaround, I am putting these typings into a declaration file on a global namespace:
TypeScript Version: 2.3.4
Code
In this example, the type def
Propsfails because of the intersection syntax, which is not supported by JSDoc:Is TypeScript planning to extend the JSDoc syntax to support TypeScript syntax within the comments, or is it only following the official JSDoc standard?
For context, this would be useful because we are gradually introducing TypeScript to our codebase via
checkJs. As a workaround, I am putting these typings into a declaration file on a global namespace: