academypoa / airtablekit Goto Github PK

Possible tools:

• jazzy: https://github.com/Realm/Jazzy
• swift-doc: https://github.com/SwiftDocOrg/swift-doc

Since we have most of the 'single' record operations in-place, a nice addition to the library would be providing 'batching' operations of the same type.

Take 'create' as an example. Today, if I wanted to add multiple records to my base, I would have to iterate over then and call this function several times on my own. I believe this behavior can safely be incorporated into the library leveraging combine and properly handling errors as they occur.

As proposed by @rafaelruwer, we can port our Docs folder markdown files to a Github wiki.
This requires the repo to be public though, so this issue should only be addressed once we make the repo public.

filterByFormula={Field Name}="value"

The delete operation requires us to create a Record, where the batch operation does not.

It would be great if we could have a similar call in the both the single and batch version.

Can I filter records or request records from an Airtable view?

Hi! I'm not getting any errors, but it also doesn't seem to be making any changes to my table. Do you know how I can fix this? Best,

When I was creating the example app of the Repo, I had to perform some work to have everything running smoothly and I was wondering if maybe we could have a property wrapper for an element that maps to an Airtable record.

I haven't given this much thinking, but I'm opening the issue so that we can discuss it later.

Since our Record object has a dictionary to hold its payload, it would be nice being able to use it with the '.' operator instead of using "[""]".
A quick look here made it appear simple to implement.

Allow them to be more flexible:

• id and createdTime should be nil-able;
• init over .create/.udpate.

I kind of struck on how to retrieve values from list method

let publisher = airtable.list(tableName: "Test table")

Any help is appreciated. Thank u!

The Airtable API provides two ways in which one can update a record, PATCH (not all fields) and PUT (all fields). I think deciding which type of operation to perform should be decided by the library and made abstract to library users.

I propose making 'patch' and 'put' (offered by the API, but not available in the library yet) private and creating a general 'update' function which decides which of these operation to perform.

This change appears to be feasible and not too time consuming.

Is there any way for AirtableKit to handle Airtable data sources with more than 100 rows? Airtable returns on "offset" to fetch the next page of records if the data source has more than 100 rows, but this seems to be ignored and only the first 100 rows are ever fetched.

This should be a simple fix where we just need to change the SPM configuration for the AirtableKit package.

Here is its current state, pointing to a specific branch:

All facade methods remain untested. Implement unit tests for them so we get more coverage and safety when implementing new features.

Hi,

I want to extract from AirTable each row of my table and make it onto an array.

Each row is a bubble with different attributes (columns of my table) a name, a URL to a logo and a size.

I would like to be able to extract from AirTable all of the rows (bubbles), iterate on them like I would do with a for loop.

To be more precise : I would like to obtain an array of sub arrays that are my rows from AirTable.

I don't know how to implement that... any idea ? Thanks

PS: I need to do so in a GameScene because each row will generate a SpriteKitNode

To provide the standard CRUD functionality, I think adding a delete function would be required.
This should not be difficult as the operation sequence does not appear to be very different from what we already have in the other CRUD functions.
In addition, the Airtable REST API provides this functionality. All we need is the is the 'record id'.

First of all thanks for developing this kit! I'm just getting started and look forward to getting it set up. In the meantime I have a question, which I'm afraid will impact everybody using this kit.

" API keys will be deprecated by the end of January 2024. After this date, API keys will stop working and you will have to migrate to personal access tokens. Personal access tokens allow you to more securely grant API access to Airtable data."

Are there any plans to migrate to access tokens? @rafaelruwer @nicolasnascimento

Again thanks for your amazing efforts!

To have the library public, we should add an example of using it in an iOS project