-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not restarting when making changes to .graphql files #120
Comments
I think we need to modify Lines 187 to 200 in e49b220
Also if you run |
Would you agree with me on this? I don't know what the So I don't really know whether the |
I agree with those points. I'm thinking that the condition on L190 should probably be removed. If we get a change notification, we should restart, full stop. |
@puchm Could you install from git and see if the latest commit fixes your issue? |
@STRML yes, it works! thank you. |
Published in |
I am trying to get this to watch for changes inside my
.graphql
files. This is the command I tried:I also tried a few of the other options but didn't succeed with that either - including running the command with polling.
What happens is that the watcher runs and it restarts when I make changes to any of the .ts files that have been imported by the entrypoint, but it doesn't restart when I make changes to my GraphQL files.
I think what is happening is that the watcher is only watching files that have been imported from the main file. However, the schema is not imported using an
import
statement but actually it is using a function from another package which just gets supplied with the file path - it looks like this:I think that when supplying the
--watch
flag, the watcher should watch two things:--watch
option (and their subdirectories) that has one of the right extensions - regardless of whether it was imported somewhere or not.Incase you think that this is an error with my system and not the package, here is some info on my system:
7.3.0
and7.3.1
- same result on both12.18.2
Thank you for your help in advance!
The text was updated successfully, but these errors were encountered: