You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens in many scenarios but there has not been a pattern that sticks out. It can be inconsistent and hard to reproduce.
The scenario that is reproducible is slightly difficult but does reproduce:
You'll need a backend graphql API with introspection available in order to set this up properly.
Setup a simple react/ts project
Setup graphQL Apollo client
Setup graphQL codegen
Write an INVALID query
Create a query using apollo's useQuery hook that queries your invalid query
Notice the inlay hint errors
Correct the invalid query
Notice that the inlay error still exists but the types are all generated and valid
Check for existing issues
Describe the bug / provide steps to reproduce it
This happens in many scenarios but there has not been a pattern that sticks out. It can be inconsistent and hard to reproduce.
The scenario that is reproducible is slightly difficult but does reproduce:
You'll need a backend graphql API with introspection available in order to set this up properly.
useQuery
hook that queries your invalid queryFundamental code example:
Environment
Zed: v0.165.4 (Zed)
OS: macOS 14.5.0
Memory: 16 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
Notice the error of destructuring
any
value, but clearly it knows the type in the other overlay.If applicable, attach your Zed.log file to this issue.
Zed.log
The text was updated successfully, but these errors were encountered: