fix: correctly use filtered form fields when preparing the connection data. #395
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
justlevine
force-pushed
the
fix/form-fields-page-filter
branch
from
a7586a5 to
150d184
Compare
3 tasks
justlevine
force-pushed
the
fix/form-fields-page-filter
branch
from
4e55091 to
d51c09a
Compare
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 fixes the
FormFieldConnectionResolverso the form fields filtered by the connectionwhereargs are used, instead of the pre-filtered values.Why
Closes #392
How
Testing Instructions
Additional Info
Checklist: