-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
queryName query #178
Comments
👋 Thanks for the kind words. I think you are on the right track. If you have suggestions to make the documentation more clear, I always appreciate pull requests 😊 . |
That probably isn't intuitive that that error just gets fed through to the graphql query. I wonder if maybe we wrap this in a try/catch block and throw a |
This issue has been automatically marked as stale because it has not had any recent activity for 30 days. It will be closed if no further activity occurs within 7 days. Remove stale label, comment, and/or apply "ongoing issue" label to prevent this from being closed. Thank you for your contributions. |
Thanks for this wonderful plug-in, which is super useful! But I'm cracking my head trying to get the queryName option to run, so that I can have better distinguish data from two separate tables to run createPage across two different templates. My GraphQL continues to show only Airtable and allAirtable tables, even after running "gatsby clean", despite trying many variations.
Within Airtable or allAirtable tables I can see a new field, "queryName": true,
But I am expecting to see new tables AirtableTable1 and AirtableTable2 here. Or do I have the wrong end of the stick?
gatsby: 2.19.45
gatsby-source-airtable: 2.1.0
gatsby-cli: 2.11.0
The text was updated successfully, but these errors were encountered: