-
Notifications
You must be signed in to change notification settings - Fork 763
Fix missing JSDoc comments on destructured interface properties #2195
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
Open
Copilot
wants to merge
9
commits into
main
Choose a base branch
from
copilot/fix-inherited-jsdoc-comments
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+133
−14
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
de2f333
Initial plan
Copilot bfff6ef
Add test for destructured interface JSDoc comments
Copilot 2462931
Fix destructured interface members to show JSDoc comments
Copilot daf041f
Update baselines for destructured binding element JSDoc
Copilot ff34e99
Refactor: Extract findPropertyInType helper and improve comments
Copilot f0f9fef
Simplify findPropertyInType using IsUnion() and Types() methods
Copilot f6b3006
Address review: check all declarations for binding elements, update t…
Copilot 8a13eab
Add marker before baz: to test property name hover
Copilot 73c9497
Revert to ValueDeclaration approach and add test for binding element …
Copilot 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
81 changes: 81 additions & 0 deletions
81
internal/fourslash/tests/destructuredInterfaceJSDoc_test.go
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 |
|---|---|---|
| @@ -0,0 +1,81 @@ | ||
| package fourslash_test | ||
|
|
||
| import ( | ||
| "testing" | ||
|
|
||
| "github.com/microsoft/typescript-go/internal/fourslash" | ||
| "github.com/microsoft/typescript-go/internal/testutil" | ||
| ) | ||
|
|
||
| func TestDestructuredInterfaceJSDoc(t *testing.T) { | ||
| t.Parallel() | ||
| defer testutil.RecoverAndFail(t, "Panic on fourslash test") | ||
| const content = ` | ||
| interface FooBar { | ||
| /** foo comment */ | ||
| foo: number; | ||
| /** bar comment */ | ||
| bar: string; | ||
| /** baz comment */ | ||
| baz: string; | ||
| } | ||
|
|
||
| declare const fubar: FooBar; | ||
|
|
||
| const {/*1*/foo, /*2*/bar, /*3*/baz: /*4*/biz} = fubar; | ||
| ` | ||
| f, done := fourslash.NewFourslash(t, nil /*capabilities*/, content) | ||
| defer done() | ||
| f.VerifyQuickInfoAt(t, "1", "const foo: number", "foo comment") | ||
| f.VerifyQuickInfoAt(t, "2", "const bar: string", "bar comment") | ||
| f.VerifyQuickInfoAt(t, "3", "(property) FooBar.baz: string", "baz comment") | ||
| f.VerifyQuickInfoAt(t, "4", "const biz: string", "baz comment") | ||
| } | ||
|
|
||
| func TestDestructuredInterfaceJSDocWithRename(t *testing.T) { | ||
| t.Parallel() | ||
| defer testutil.RecoverAndFail(t, "Panic on fourslash test") | ||
| const content = ` | ||
| interface FooBar { | ||
| /** foo comment */ | ||
| foo: number; | ||
| /** bar comment */ | ||
| bar: string; | ||
| } | ||
|
|
||
| declare const fubar: FooBar; | ||
|
|
||
| const {foo: /*1*/myFoo, bar: /*2*/myBar} = fubar; | ||
| ` | ||
| f, done := fourslash.NewFourslash(t, nil /*capabilities*/, content) | ||
| defer done() | ||
| f.VerifyQuickInfoAt(t, "1", "const myFoo: number", "foo comment") | ||
| f.VerifyQuickInfoAt(t, "2", "const myBar: string", "bar comment") | ||
| } | ||
|
|
||
| func TestDestructuredWithOwnJSDoc(t *testing.T) { | ||
| t.Parallel() | ||
| defer testutil.RecoverAndFail(t, "Panic on fourslash test") | ||
| const content = ` | ||
| interface Foo { | ||
| /** This is bar from the interface */ | ||
| bar: string; | ||
| /** This is baz from the interface */ | ||
| baz: number; | ||
| } | ||
|
|
||
| declare var foo: Foo; | ||
|
|
||
| /** Comment on the variable statement. */ | ||
| const { | ||
| /** Comment on bar destructuring. */ /*1*/bar, | ||
| /** Comment on baz destructuring. */ /*2*/baz | ||
| } = foo; | ||
| ` | ||
| f, done := fourslash.NewFourslash(t, nil /*capabilities*/, content) | ||
| defer done() | ||
| // When binding elements have their own JSDoc, TypeScript doesn't currently show it in hover | ||
| // Instead, it falls back to the property's JSDoc from the interface | ||
| f.VerifyQuickInfoAt(t, "1", "const bar: string", "This is bar from the interface") | ||
| f.VerifyQuickInfoAt(t, "2", "const baz: number", "This is baz from the interface") | ||
| } |
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
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
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.
I'm not so familiar with this, so it could be right, but what I would say is that maybe this needs to be more general and look at all declarations nodes from a given symbol like
getDocumentationCommentdid in the original codebase.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.
Done in f6b3006. Made the implementation more general by iterating through all
symbol.Declarations(instead of just checkingsymbol.ValueDeclaration) to find binding elements. This matches the pattern in TypeScript wheregetDocumentationCommentprocesses all declarations from a symbol.