feat: richer hover info (signature, deprecation, defaults)

[JoviDeCroock]

What / Why

Hovering a GraphQL field previously showed a single flat string (produced by graphql-language-service's getHoverInformation) stuffed into the quick-info documentation, with no displayString, no argument info, and no deprecation notice. This PR upgrades getGraphQLQuickInfo so hovers are structured like regular TypeScript quick info:

1. Signature line (in displayParts → displayString): ParentType.fieldName: ReturnType, and for fields with arguments ParentType.fieldName(arg: ArgType = default): ReturnType. Types are printed as proper GraphQL types (String!, [Pokemon]), default values via astFromValue + print.
2. Deprecation (in documentation + a deprecated JSDoc tag so editors can render strikethrough): @deprecated: <reason>, falling back to the GraphQL spec default No longer supported when the reason is empty.
3. Schema description as documentation, as before.

Hover now also resolves:

• field & directive arguments — the argument's own type, default value, description, and deprecation (Query.pokemons(limit: Int = 10))
• enum values — PokemonType.Grass plus description/deprecation
• directives — @include plus description
• fragment type conditions / named types — on Pokemon shows the type and its description

Implementation notes

• Instead of getHoverInformation (which returns a pre-joined string), the hover now uses the same underlying helpers — getTokenAtPosition + getTypeInfo from graphql-language-service — and renders the pieces itself, so signature/deprecation/description can be placed into the right ts.QuickInfo slots (displayParts, documentation, tags). The token/cursor resolution code (call expression vs. tagged template, span math) is unchanged.
• The token kinds handled mirror getHoverInformation's: Field/AliasedField, Argument, Directive, EnumValue, NamedType. All of the requested positions (arguments, enum values, type conditions) were resolvable with the existing helpers, so no follow-ups were needed there.
• When the cursor is on a token we can't produce hover info for (punctuation, variables, etc.), we now return undefined so the guard() fallback lets the original language service respond — previously an empty tooltip was returned.
• test/e2e/fixture-project-tada/schema.graphql gained a default value (pokemons(limit: Int = 10, ...)) to cover default-value printing; this doesn't affect the generated gql.tada introspection (argument info isn't part of it).

Before / After examples

Hovering pokemons in query { pokemons(limit: $limit) { ... } }:

	displayString	documentation
Before	(none)	Query.pokemons: [Pokemon] List out all Pokémon, optionally in pages
After	Query.pokemons(limit: Int = 10, skip: Int): [Pokemon]	List out all Pokémon, optionally in pages

Hovering the deprecated classification field:

	displayString	documentation	tags
Before	(none)	Pokemon.classification: String Deprecated: And this is the reason why	(none)
After	Pokemon.classification: String	@deprecated: And this is the reason why	[{ name: 'deprecated', text: 'And this is the reason why' }]

Hovering the limit argument (new — previously rendered Query.pokemons(limit: Int) without the default):

	displayString
After	Query.pokemons(limit: Int = 10)

Hovering Pokemon in fragment pokemonFields on Pokemon (new): displayString Pokemon.

Existing assertions in tada.test.ts, graphqlsp.test.ts, combinations.test.ts, client-preset.test.ts, and multi-schema-tada.test.ts were updated accordingly — e.g. documentation === 'Query.posts: [Post]\n\nList out all posts' became displayString === 'Query.posts: [Post]' + documentation === 'List out all posts'.

Test plan

• pnpm --filter @0no-co/graphqlsp run build — passes
• pnpm run test:e2e (full suite, forks a real tsserver) — 11 files / 55 tests, all passing, including new assertions for:
  • a field with arguments and a default value
  • a deprecated field (documentation line + deprecated tag)
  • an argument hover
  • a fragment type-condition hover

Note: the pre-commit husky bootstrap (.husky/_/husky.sh) is missing in fresh checkouts after pnpm install, so the hook was bypassed after running prettier --write on all touched files manually (the hook only runs lint-staged/prettier).

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: 15ac3d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@0no-co/graphqlsp	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR