-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Parse comment on @property tag and use as documentation comment #21119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1586,42 +1586,35 @@ namespace ts { | |
((node as JSDocFunctionType).parameters[0].name as Identifier).escapedText === "new"; | ||
} | ||
|
||
export function getAllJSDocs(node: Node): (JSDoc | JSDocTag)[] { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this was internal, right? I don't see a jsdoc on it, so I assume so. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. API tests should ensure we don't delete internal things. |
||
if (isJSDocTypedefTag(node)) { | ||
return [node.parent]; | ||
} | ||
return getJSDocCommentsAndTags(node); | ||
} | ||
|
||
export function getSourceOfAssignment(node: Node): Node { | ||
function getSourceOfAssignment(node: Node): Node { | ||
return isExpressionStatement(node) && | ||
node.expression && isBinaryExpression(node.expression) && | ||
node.expression.operatorToken.kind === SyntaxKind.EqualsToken && | ||
node.expression.right; | ||
} | ||
|
||
export function getSingleInitializerOfVariableStatement(node: Node, child?: Node): Node { | ||
function getSingleInitializerOfVariableStatement(node: Node, child?: Node): Node { | ||
return isVariableStatement(node) && | ||
node.declarationList.declarations.length > 0 && | ||
(!child || node.declarationList.declarations[0].initializer === child) && | ||
node.declarationList.declarations[0].initializer; | ||
} | ||
|
||
export function getSingleVariableOfVariableStatement(node: Node, child?: Node): Node { | ||
function getSingleVariableOfVariableStatement(node: Node, child?: Node): Node { | ||
return isVariableStatement(node) && | ||
node.declarationList.declarations.length > 0 && | ||
(!child || node.declarationList.declarations[0] === child) && | ||
node.declarationList.declarations[0]; | ||
} | ||
|
||
export function getNestedModuleDeclaration(node: Node): Node { | ||
function getNestedModuleDeclaration(node: Node): Node { | ||
return node.kind === SyntaxKind.ModuleDeclaration && | ||
(node as ModuleDeclaration).body && | ||
(node as ModuleDeclaration).body.kind === SyntaxKind.ModuleDeclaration && | ||
(node as ModuleDeclaration).body; | ||
} | ||
|
||
export function getJSDocCommentsAndTags(node: Node): (JSDoc | JSDocTag)[] { | ||
export function getJSDocCommentsAndTags(node: Node): ReadonlyArray<JSDoc | JSDocTag> { | ||
let result: (JSDoc | JSDocTag)[] | undefined; | ||
getJSDocCommentsAndTagsWorker(node); | ||
return result || emptyArray; | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,8 +27,7 @@ | |
"pos": 15, | ||
"end": 21 | ||
} | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,8 +27,7 @@ | |
"pos": 15, | ||
"end": 21 | ||
} | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,8 +17,7 @@ | |
"pos": 9, | ||
"end": 15, | ||
"escapedText": "return" | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,8 +27,7 @@ | |
"pos": 17, | ||
"end": 23 | ||
} | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,8 +27,7 @@ | |
"pos": 18, | ||
"end": 24 | ||
} | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -33,8 +33,7 @@ | |
"length": 1, | ||
"pos": 18, | ||
"end": 20 | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -44,8 +44,7 @@ | |
"length": 2, | ||
"pos": 18, | ||
"end": 22 | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -44,8 +44,7 @@ | |
"length": 2, | ||
"pos": 18, | ||
"end": 23 | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -44,8 +44,7 @@ | |
"length": 2, | ||
"pos": 18, | ||
"end": 23 | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -44,8 +44,7 @@ | |
"length": 2, | ||
"pos": 18, | ||
"end": 24 | ||
}, | ||
"comment": "" | ||
} | ||
}, | ||
"length": 1, | ||
"pos": 8, | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just to make sure I'm not missing something: This is the only line required to make the tests pass, right? The rest looks like refactoring.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why isn't isn't indent needed to get the correct offset, like with the other call to parseTagComments? Does tryParseChildTag need to track indent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I needed to make a few other changes to
parser.ts
to avoid skipping the@
token at the end of a comment and to useundefined
instead of""
for the comment.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like it will be needed to get the best comment text, that will be a bigger change though. Filed #21123