Return nested recipe's dataframe from the recipe write connector - #1163
Draft
mborodii-prog wants to merge 4 commits into
Draft
Return nested recipe's dataframe from the recipe write connector#1163mborodii-prog wants to merge 4 commits into
mborodii-prog wants to merge 4 commits into
Conversation
When a recipe is used as a write: - recipe: step, its own write: - dataframe: step can now shape the outer recipe's returned dataframe, instead of being silently discarded. Addresses the second scenario in #1157.
mborodii-prog
force-pushed
the
fix/1157-write-recipe-return-value
branch
from
September 2, 2026 06:57
9733d84 to
41c887b
Compare
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.
When a recipe is used as a write: - recipe: step, its own write: - dataframe: step can now shape the outer recipe's returned dataframe, instead of being silently discarded. Addresses the second scenario in #1157.
Linked issue
Closes #
What changes
Describe the user-visible or API behavior change. Keep unrelated changes in a
separate PR.
How it was verified
List the focused tests and any manual or live-service verification performed.
Compatibility and risk
Describe compatibility impact, migration needs, credentials/external services,
and the safest rollback.
Ready-for-review checklist
mainand has no merge conflictsSee the pull request workflow.