feat(update): create class update method to avoid API find call #103
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
updatemethod that the instancesavemethod uses, or can be used separately.To test I did the following:
record = OurTableKlass.find('recmBCJvI3hbRRo8c'); record["Name"] = "test change 1"; record.saveto see the record update in Airtablerecord.fieldsAirtable::Application.update('recmBCJvI3hbRRo8c', { "Name" => "test change 2" })to see the record update again in Airtable