feat: add output_passthrough to ConditionalRouter for non-Jinja2 routing

[spideyashith]

Proposed Changes

Adds an optional output_passthrough field to ConditionalRouter routes.
When set to True, the output field is treated as a plain variable name
instead of a Jinja2 template, passing the value directly from kwargs to the
route output. This enables routing of complex non-basic types (dataclasses,
Pydantic models) without unintended Jinja2 processing.

Closes #9355

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist

• I have read the contributing guidelines
• I have added tests that prove my fix is effective or that my feature works
• I have added/updated the docstrings for all modified components
• New and existing unit tests pass locally with my changes
• Release notes have been added

Note

This PR was developed with AI assistance.

[vercel]

@spideyashith is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[spideyashith]

I've opened a PR to address this: #11555. The implementation adds an output_passthrough field to routes that skips Jinja2 processing and passes variables directly, enabling routing of complex non-basic types.

[davidsbatista]

I ask you in the future for upcoming PRs to stick to our PR template.

[davidsbatista]

I've opened a PR to address this: #11555. The implementation adds an output_passthrough field to routes that skips Jinja2 processing and passes variables directly, enabling routing of complex non-basic types.

Which issue are you referring to? Is another issue introduced by opening this PR?

[spideyashith]

I've opened a PR to address this: #11555. The implementation adds an output_passthrough field to routes that skips Jinja2 processing and passes variables directly, enabling routing of complex non-basic types.

Which issue are you referring to? Is another issue introduced by opening this PR?

Sorry for the confusion! I mistakenly posted that comment inside the PR instead of on the original issue. This PR addresses issue #9355 — adding a way to route complex types in ConditionalRouter without Jinja2 processing.

[spideyashith]

I've opened a PR to address this: #11555. The implementation adds an output_passthrough field to routes that skips Jinja2 processing and passes variables directly, enabling routing of complex non-basic types.

Which issue are you referring to? Is another issue introduced by opening this PR?

Hi @davidsbatista, apologies for the confusion — that comment was meant for issue #9355, not this PR. I've also updated the PR description to follow the project template. Please let me know if any changes are needed, happy to update!

[spideyashith]

Hi @davidsbatista, just checking in — happy to make any changes if needed. Let me know!