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
When calling a function with object parameters documented with JSDoc, Visual Studio Code will not give intellisense completions if the parameter was documented using the object literal format with the comment broken up over multiple lines.
This type of formatting allows for better readability when documenting objects with a lot of properties, so it would be helpful if this was supported.
TypeScript Version: 2.1.0-dev.20160824
Code
Expected behavior:
The properties of an object parameter should be recognized when it is documented using the JSDoc object literal @param syntax, even if the comment spans multiple lines.
Actual behavior:
No properties of the object are recognized unless the JSDoc comment is only a single line.
The text was updated successfully, but these errors were encountered:
Yep, my changes should fix this since jsdoc type parsing now delegates to the real typescript type parser, which of course doesn't care about whitespace.
(Note: object literal types aren't actually standard jsdoc, they seem to have been introduced by Closure and TypeScript.)
When calling a function with object parameters documented with JSDoc, Visual Studio Code will not give intellisense completions if the parameter was documented using the object literal format with the comment broken up over multiple lines.
This type of formatting allows for better readability when documenting objects with a lot of properties, so it would be helpful if this was supported.
TypeScript Version: 2.1.0-dev.20160824
Code
Expected behavior:
The properties of an object parameter should be recognized when it is documented using the JSDoc object literal @param syntax, even if the comment spans multiple lines.
Actual behavior:
No properties of the object are recognized unless the JSDoc comment is only a single line.
The text was updated successfully, but these errors were encountered: