Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Doesn't work with schema path outside project root

See original GitHub issue

schema: {
    files: '../graphql/*.graphql'
}

doesn’t work, while

schema: {
    files: 'graphql/*.graphql'
}

works just fine.

Using it on Windows 10, not sure how to get any useful error message (I just see an error icon in VSCode and the plugin features don’t work).

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

peterholakcommented, Aug 22, 2017

I have a project where both the client and the server (multiple different servers in fact) are in the same git repository, and share the same graphql schema. So the directory structure goes something like

|- client
    |- package.json
    |- webpack.config.js
    |- ...
|- server1
|- server2
|- graphql
    |- schema.graphql
|- README.md and other stuff

In VSCode, I only open the client directory, because it’s more convenient (no irrelevant clutter when doing project-wide search, correct default working directory for scripts, etc.).

0reactions

kumarharshcommented, Jul 4, 2019

🎉 This issue has been resolved in version 1.14.0 🎉

The release is available on:

Your semantic-release bot 📦🚀