-
-
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
Support using extract airtable schema to streamline config #271
Comments
Also, thank you thank you thank you for this wonderful package! ❤️ |
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. |
This would a good addition to the readme as well. ❤️ |
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. |
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. |
There are a few ways out there to generate a json representation of an airtable schema. One is via this browser extension:
https://github.com/ashwinputhige/airtable-schema-chrome-extension
(Another is using something like airtable's "schema" app/block, though that work need a fork to expose the schema object, and a pro account to install the app after March 2021 when they become a pros feature.)
Would be neat if someone were to share a small bit of glue code to pre-configure this source using a json file. If I find time, will share back here.
The text was updated successfully, but these errors were encountered: