Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This pull request improves Airtable collection sync speed using the same method used in Notion - if an item hasn't been edited since the last sync, don't update it in the collection.
Airtable doesn't include a last edited date on all items by default like Notion does. But Airtable does have a "last modified time" field. So what this update does is check if there is a last modified time field in the base, and if so, uses that value on each item to determine whether to update it or not.
If the base doesn't have a last modified time field, a note is shown at the top of the field mapping UI:
Closes #461
Solves the second point in this Slack message: https://framer-team.slack.com/archives/C06FEPVRM52/p1770924863842099
Changelog
Testing