Add field selector and ability to filter by formula #16
Conversation
This file contains 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
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.
What?
This PR will add the ability to select only defined fields and filter by an Airtable formula for the
airtable_tabledata source.Why?
It will reduce the records (and fields) returned by the data source because currently everything is returned at once and it's a pain to deal with when you have a fairly large table.
How?
This will add two more optional fields to the data source named
fields(a list of strings) andfilter_by_formula(string). Users can define a list of fields to only return them from the API and use an Airtable formula to further filter the records.Testing
Unfortunately only locally tested, as far as I can see the tests were made with a private Airtable base.
More info
More tests should be implemented, especially for the new two parameters we've added to the data source. Can be easily tested locally though (with a private table of course)
Thanks!