"undefined undefined" when opening .graphql file containing queries about vscode-graphql HOT 6 CLOSED

Seeing this on the 0.0.8 I got from the marketplace.

ZEBRA 1: undefined undefined
ZEBRA: GraphQLProjectConfig {
  config: 
   { schemaPath: './services-js/commissions-app/graphql/schema.graphql',
     includes: [ './services-js/commissions-app/src/client/**/*.{graphql,ts,tsx,js,jsx}' ],
     extensions: { endpoints: [Object] } },
  configPath: '/Users/FinneganHopkins/Source/monorepo/.graphqlconfig',
  projectName: 'commissions-app' } /Users/FinneganHopkins/Source/monorepo/services-js/commissions-app/graphql/schema.graphql

Query file (./services-js/commissions-app/src/client/graphql/test.graphql):

query {
  commissions {
    applyUrl
  }
}

from vscode-graphql.

The same happens for graphql-server-example/queries/queries.graphql

from vscode-graphql.

Fixed via prisma-labs/graphql-prisma-typescript#246

Also, you are on an older version of extension. Can you please download it via the marketplace?

from vscode-graphql.

I did!

from vscode-graphql.

Reproduction:

1. Create a create-react-app with TypeScript (create-react-app my-app --scripts-version=react-scripts-ts from https://github.com/wmonk/create-react-app-typescript)
2. Add graphql-tag and graphql to project
3. Install the plugin to VSCode
4. Clone an exisiting schema (or fetch your own) into schema.graphql in project root
5. Go into App.tsx and add

import gql from 'graphql-tag';

const TEST_QUERY = gql`
  query {
    // Expect automagical Intellisense and validation, be disappointed :)
  }
`

6. Check the "Output" pane in VS Code for GraphQL Language Server, see

ZEBRA 1: undefined undefined
ZEBRA: GraphQLProjectConfig {
  config: 
   { schemaPath: 'schema.graphql',
     includes: [ 'schema.graphql' ],
     extensions: { endpoints: [Object] } },
  configPath: '[path to project]/.graphqlconfig.yaml',
  projectName: 'app' } [path to project]/schema.graphql

from vscode-graphql.

@marktani The original problem of vague logs in output "GraphQL Language Server" are resolved in 0.0.9.

The issue with autocomplete can be logged following these instructions and is unrelated to output "GraphQL Language Server" logs.

I will investigate it further under this issue (#21). Closing this one.

from vscode-graphql.