-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Profiles & Formats (Airtable (JSON)) #44
Comments
JSON is definitely possible and not hard to add. Would the key names be the same as the CSV table column names? |
Yes, the key column names would be identical to our Airtable CSV. |
Why not just always output both a csv file and a json file? No additional arguments or options required and it's no extra overhead really. The done file can contain both file paths. |
This is implemented. Will be in next alpha build. |
Yes, that could work too! Thank you. |
Even though Airlift supports both This is to standardise output format filetype. |
There isn't any harm in generating both files and it takes zero time and very little disk space. If it's ever needed in future then you already have it. |
True, there is no harm. We just the code in but we just off the generation part for now? |
Sure, if you want. |
Thank you! |
@orchetect I wondering if we can add an additional profile for Airtable that is in JSON format.
If @theogscott going to use AirtableKit, it would be great if the CLI and Library is able to provide a native way to generate the output data in JSON format.
From the example of AirtableKit, the library will aspects data in this format :
I wonder if it would allow easier facilitation of uploading the data directly to Airtable via Marker Data App. Hence, @theogscott could pass the .json file programmatically.
The current Airtable profile could be rename to Airtable (CSV). We could still keep the this profile for users who want to upload the data manually.
The text was updated successfully, but these errors were encountered: