Uh oh!
There was an error while loading. Please reload this page.
Add parameters' type information in JSDoc comments scaffolding - #12722
Conversation
Hi Anubha Mathur (@anubmat), I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
TTYL, MSBOT; |
Anubha Mathur (anubmat)
commented
Dec 8, 2016
jram (@jramsay) , Bill Ticehurst (@billti) , Vlad Yazhbin [twitter.com/vla] (@vlad), Can someone please review? |
| const lineStart = sourceFile.getLineStarts()[posLineAndChar.line]; | ||
| const indentationStr = sourceFile.text.substr(lineStart, posLineAndChar.character); | ||
| const isJavaScriptFile = hasJavaScriptFileExtension(sourceFile.fileName); // JSX or JS file |
There was a problem hiding this comment.
I don't think that this comment adds anything.
There was a problem hiding this comment.
agreed.. added because of jsx files... will remove.
👍 after addressing my one nit. |
Bill Ticehurst (billti)
commented
Dec 8, 2016
Looks good for now. We might want to make this behavior optional (based on a editor config setting) if we get feedback that some folks don't like it. I'd assume some devs don't want the type annotations in their JsDoc comments. Thanks! 👍 |
Adds type {any} in comments for parameters in JS and JSX files

Earlier type was missing:
