String interpolation in queries. #3564
Replies: 1 comment 3 replies
-
yes it's possible, but the expression is replaced with a newline in our LSP and other graphql LSPs. and an empty leaf expression is invalid in graphql. so there just needs to be at least one literal field to make the validation work. we and other graphql LSPs do not support anything beyond this, because we cannot infer the values. yes it's annoying but the only way around this is to disable the relevant graphql validation rules by providing a custom ruleset in graphql config |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, is it even possible to implement subqueries / partially valid queries that can be imported as const to another query while keeping the LSP support?
I notice that on importing substring consts Im losing some LSP support like formatting and the file turns red and indicate error in VSCode, although the query works just fine.
Is there a workaround? If not, is there a possibility to set an ignore line, like a // @ts-ignore for the line "interfering" ?
Beta Was this translation helpful? Give feedback.
All reactions