Skip to content

Conversation

@theblang
Copy link
Contributor

@theblang theblang commented Sep 13, 2023

With the upcoming plan changes, monthly API quota limits are being set, 1k for the free plan and 100k for the mid-level plan. This might be problematic for us, so I realized we could cut down almost 50% if we don't always require two API calls to sync record changes. Thus, I made a class update method that the instance save method uses, or can be used separately.

To test I did the following:

  • Ran record = OurTableKlass.find('recmBCJvI3hbRRo8c'); record["Name"] = "test change 1"; record.save to see the record update in Airtable
  • Sanity checked record.fields
  • Ran Airtable::Application.update('recmBCJvI3hbRRo8c', { "Name" => "test change 2" }) to see the record update again in Airtable

@theblang
Copy link
Contributor Author

@Meekohi @sirupsen Hey y'all! Either of you have some time for a review on this one? The new API limits makes the need for some optimization more important.

@Meekohi Meekohi merged commit 8c1999a into sirupsen:master Sep 18, 2023
@Meekohi
Copy link
Collaborator

Meekohi commented Sep 18, 2023

lgtm :shipit:

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

Successfully merging this pull request may close these issues.

2 participants