Hover not working about vscode-graphql HOT 12 CLOSED

@peterschussheim : DateTime, String, Int have hover support for "test definition" already, not sure where they can go when peeked into because they don't have a physical type definition.

@marktani : It is a side effect of creating "go to" definition. That is how VSCode works.
The other extension chooses to show "peek" in hover in place of "comment", which is incorrect IMO as it won't show anything for built-in types or have separate code paths for it. Not sure.

from vscode-graphql.

Thanks for sharing the image. Such a "peek definition" is already there. In this extension, you need to press cmd + hover to get a "peek".

We support this for type definition, input definition, enum definition, fragment definitions.

Does this information solve it for you? Do you think we can document it better to enhance the experience.

Please feel free to raise a PR to make it better or suggest here. Thanks!

from vscode-graphql.

What is a token?

from vscode-graphql.

Edited original post. Token in this context refers to a variable or symbol in the editor.

from vscode-graphql.

@peterschussheim : Thanks for reporting this, can you please share a screenshot of the symbol on which hover does not work?

Currently, we only support hover for NamedType and Directive. If this is for a variable then it is an enhancement and not a bug. Thanks.

from vscode-graphql.

@divyenduz What is the roadmap for complete hover support?

from vscode-graphql.

@peterschussheim : Currently, we are awaiting feedback and estimating the amount of work for complete support as it will span across both language services (GraphQL and TS). Can you please share a screenshot of your specific case?

from vscode-graphql.

here is a screenshot of hovers in kumar harsh's extension:

from vscode-graphql.

What about support for:

• DateTime
• String
• Int

from vscode-graphql.

In this extension, you need to press cmd + hover to get a "peek".

I didn't know about this!! It's like a hidden gem 😄Not sure how we can better document this.

from vscode-graphql.

Most intellisense extensions show both the declaration line and the documentation (comment) of the field rendered as markdown with a hover provider

from vscode-graphql.

I tried this actually - the issue here i found, is that if we print the type on hover as you suggest @felixfbecker, then when users ctrl/cmd-click to peek definition, it renders it unreadable/unusable, because the type is printed in duplicate and cut off

its more practical to have the full type documentation printed, and if you want to peek the type representation, then you can!

coming up, we can show other information on hover, such as references, etc. but viewing the language definition itself is peek/view definition's job

from vscode-graphql.