Document native template rendering type coercion (#34641)#69152
Conversation
shahar1
left a comment
shahar1
left a comment
There was a problem hiding this comment.
@deepujain please note that you (or your operator) should include AI attribution in the PR as we state in the AI guidelines.
This PR, as well as others, are blocked from being merged until this is corrected.
Please be warned that creating additional PRs except for the 10 you've already created (listed below) without addressing the above might cause in a permanent block from Apache organization on GitHub.
List of PRs:
potiuk
added
the
ready for maintainer review
potiuk
left a comment
potiuk
left a comment
There was a problem hiding this comment.
Docs-only — correct and useful caveat about native-template type coercion ("42" -> 42). Verified the diff. LGTM.
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
3 participants
Title: Document native template rendering type coercion (#34641)
Summary
Document that
render_template_as_native_obj=Trueuses Jinja native rendering and can coerce numeric-looking strings into Python numbers. This keeps the current behavior intact while making the tradeoff clear in both the operator templating docs and the Params docs.Changes
airflow-core/docs/core-concepts/operators.rst-- add a note thatNativeEnvironmentfollows Python literal rules and can convert strings such as"42"to42.airflow-core/docs/core-concepts/params.rst-- add the same caution where typed Params and native template rendering are introduced.Test plan
git diff --checkprek run --stage pre-commit --files airflow-core/docs/core-concepts/operators.rst airflow-core/docs/core-concepts/params.rstWas generative AI tooling used to co-author this PR?
Generated-by: OpenAI Codex following the guidelines
Fixes #34641