Skip to content
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

Fetch new content in development #21

Closed
adrienpoly opened this issue Oct 15, 2018 · 2 comments
Closed

Fetch new content in development #21

adrienpoly opened this issue Oct 15, 2018 · 2 comments

Comments

@adrienpoly
Copy link

Hello

Thanks for this excellent source plugin. While in development I was wondering if there is a way to force to refresh the GraphQl nodes when I update Airtable data.

Currently, the only solution I found was to kill my dev server and start it again.

Maybe there is another trick?

Thanks

@brendanmc6
Copy link
Collaborator

brendanmc6 commented Oct 15, 2018

@adrienpoly This is something I was looking into as well-- from what I understand, this would only be possible if Airtable themselves integrated Webhooks. Here is a popular feature request thread on precisely this topic:

https://community.airtable.com/t/webhooks-for-records/1966

As for avoiding a dev server restart but still doing things manually, it seems Gatsby has implemented an endpoint you can send a POST to, which triggers a data refresh. It isn't well documented, I've never tried it (gatsby develop is fast enough for me) but these two threads might help you get there:

gatsbyjs/gatsby#3293
gatsbyjs/gatsby#3054

This is really a gatsby.js topic and not airtable specific. Good luck, let me know if you find a good solution!

@adrienpoly
Copy link
Author

thanks a lot @brendanmc6 , it is very helpful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants