Fix: loops with non-required inputs - #435
Merged
Merged
Conversation
Signed-off-by: brookewp <brooke.kaminski@automattic.com>
Contributor
|
Test this PR in WordPress Playground. |
Signed-off-by: brookewp <brooke.kaminski@automattic.com>
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
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.
After merging #418, I noticed that the Airtable loop block shows a manual input button because there are multiple inputs in the schema for paginating. To fix this, we'll need to add a check for non-required input variables like what @chriszarate is adding in #428
Hopefully we'll have less conflicts by using the same method. The main difference is I added it as a conditional to the
render_queryas I suggested here: #428 (comment)