facebook / facebook/relay

[VSCode extension] New fields from resolvers not recognised by LSP

Open
#4,142 2 comments 1 reaction 0 assignees View on GitHub
bug rust
Dominant language
Rust
Stars
19k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

I created a new relay client-side resolver for a new property on a graphQL object. (Using this [guide](https://relay.dev/docs/guides/relay-resolvers)) and everything works as expected besides that the property in vscode is highlighted as unknown.

![SCR-20221130-h4r](https://user-images.githubusercontent.com/7422767/205086314-5d044983-2d93-4550-aabe-eb621e5e1790.png)

I am currently using the following version of the relay extension in vscode:

![SCR-20221130-m5f](https://user-images.githubusercontent.com/7422767/205086352-284f0204-421e-4696-87f5-41f66aac5247.png)

Am I missing something or is this an issue?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the report in the Relay VSCode extension using the client-side resolver described in the linked Relay resolvers guide. Inspect the extension's LSP field-recognition path and compare its schema inputs with the resolver's new property. Done means the resolver-provided property is no longer highlighted as unknown in VSCode.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.