Apollo-tooling: VSCode: Autocomplete/suggestion after fragment in query

Created on 8 Nov 2018  路  5Comments  路  Source: apollographql/apollo-tooling

The autocomplete/suggestion after a fragment is not showing up. Before the spreaded fragment, it works as expected.

Basic example, where name is not showing up:

const exampleQuery = gql`
  query Somethings($input: ThingsInput) {
    things(input: $input) {
      description 
      ...AlltThingsProps
      name
    }
  }
  ${ThingsFragments.allThingsProps}
`;
vscode 馃悶 bug

Most helpful comment

I just encountered the same issue and made a small video showing it. Not really sure about any other way to reproduce, it's just configured with my local schema, nothing spectacular about it.

As you can see, autocomplete before used fragment works just fine, but it gets broken after it.

ezgif com-video-to-gif 1

All 5 comments

Thanks for submitting @daugsbi, is this still happening? I can't reproduce. If you can, a repo that I can clone to reproduce would be very helpful!

fragment_autocomplete

Hi Trevor, the autocomplete works now.
Got still an issue when I press CTRL+Space (Basic code completion) without any character after a fragment, it shows me some additional wrong information(other than before the fragment), for example "const". See the screenshots below for clarification.
vscodeapolloissue
vscodeapolloissueafterfragment

I can still reproduce this, so just mentioning this is still relevant while I triage these issues :)

I just encountered the same issue and made a small video showing it. Not really sure about any other way to reproduce, it's just configured with my local schema, nothing spectacular about it.

As you can see, autocomplete before used fragment works just fine, but it gets broken after it.

ezgif com-video-to-gif 1

Well, turns out this was never an issue of Apollo extension but rather the GraphQL for VSCode which I had installed when investigating this issue.

I am not sure if Apollo suffers the same issue because autocomplete does not work at all. We had to revert back to original extension.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lirbank picture lirbank  路  4Comments

fenech picture fenech  路  3Comments

hashlin picture hashlin  路  4Comments

clayne11 picture clayne11  路  3Comments

ethansinjin picture ethansinjin  路  3Comments