Skip to content

Add inlay hint support#1339

Closed
kitsonk wants to merge 1 commit intomicrosoft:gh-pagesfrom
kitsonk:feat_inlay_hints
Closed

Add inlay hint support#1339
kitsonk wants to merge 1 commit intomicrosoft:gh-pagesfrom
kitsonk:feat_inlay_hints

Conversation

@kitsonk
Copy link
Copy Markdown

@kitsonk kitsonk commented Sep 3, 2021

Ref #956

@kitsonk kitsonk mentioned this pull request Sep 3, 2021
@matklad
Copy link
Copy Markdown
Contributor

matklad commented Sep 3, 2021

dupe of #1249 ?

Comment on lines +9027 to +9040
/**
* The kind of this hint.
*/
kind?: InlayHintKind;

/**
* Whitespace before the hint.
*/
whitespaceBefore?: boolean;

/**
* Whitespace after the hint.
*/
whitespaceAfter?: boolean;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we include a note in the comment that states what happens when these optional fields are omitted?

@kitsonk
Copy link
Copy Markdown
Author

kitsonk commented Sep 3, 2021

@matklad that hasn't been aligned to what vscode implemented and hasn't been updated since 8th June, which this PR is aligned to and I raised it based off this comment #956 (comment).

I would be fine with #1249 being aligned to what shipped in vscode. All I want to do is get the feature added, by hook or crook.

@kitsonk
Copy link
Copy Markdown
Author

kitsonk commented Sep 3, 2021

Also @matklad this comment seems to indicate that the PR is "obsolete" but left up to @dbaeumer to close when appropriate: #1249 (comment)

@kitsonk kitsonk closed this Jan 21, 2022
@dbaeumer
Copy link
Copy Markdown
Member

Yes, I think we should continue in #1249

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