📝 Update Builder's Record Selector docs #37752
Merged
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
the
area/documentation
girarda
approved these changes
May 1, 2024
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
Relates to https://github.com/airbytehq/airbyte-platform-internal/pull/12298
The Builder documentation for the Record Selector component needs to be updated based on the changes proposed in that ^ PR.
This should only be merged after the above PR is shipped.
How
This PR updates the docs to reflect the changes to Record Selector in the Builder:
Record Selectorbefore is now theField Pathinput inside of theRecord SelectorcomponentRecord Filtercan now be configured, so documentation was added for thatCast Record Fields to Schema Types(i.e. SchemaNormalization) can also now be configured, so documentation was added for thatUser Impact
Updated docs
Can this PR be safely reverted and rolled back?