Skip to content

getEffectiveBaseTypeNode: only use JSDoc augments if there is extends #29349

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 1 commit into from
Feb 5, 2019

Conversation

ajafff
Copy link
Contributor

@ajafff ajafff commented Jan 10, 2019

Suggested by @sandersn in #29308 (comment)

@@ -2513,14 +2513,15 @@ namespace ts {
}

export function getEffectiveBaseTypeNode(node: ClassLikeDeclaration | InterfaceDeclaration) {
if (isInJSFile(node)) {
const baseType = getClassExtendsHeritageElement(node);
if (baseType && isInJSFile(node)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DanielRosenwasser @sandersn should it be error to have augments clause and not have extends clause?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be too noisy. Every time we add errors like this they add noise to erroneous jsdoc -- ones where people weren't actually using the jsdoc and didn't want to.

@@ -2513,14 +2513,15 @@ namespace ts {
}

export function getEffectiveBaseTypeNode(node: ClassLikeDeclaration | InterfaceDeclaration) {
if (isInJSFile(node)) {
const baseType = getClassExtendsHeritageElement(node);
if (baseType && isInJSFile(node)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be too noisy. Every time we add errors like this they add noise to erroneous jsdoc -- ones where people weren't actually using the jsdoc and didn't want to.

@sandersn sandersn merged commit 12edac0 into microsoft:master Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants