Co-authored-by: Joel <iamjoel007@gmail.com>
Co-authored-by: crazywoola <427733928@qq.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Novice <novice12185727@gmail.com>

Co-authored-by: Yeuoly <admin@srmxy.cn>

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Co-authored-by: 刘江波 <jiangbo721@163.com>

Signed-off-by: -LAN- <laipz8200@outlook.com>

Co-authored-by: zxhlyh <jasonapring2015@outlook.com>
Co-authored-by: Yeuoly <admin@srmxy.cn>

Co-authored-by: NFish <douxc512@gmail.com>
Co-authored-by: JzoNg <jzongcode@gmail.com>
Co-authored-by: Garfield Dai <dai.hai@foxmail.com>

Signed-off-by: yihong0618 <zouzou0208@gmail.com>

refactor(api): Separate SegmentType for Integer/Float to Enable Pydantic Serialization (#22025)

This PR addresses serialization issues in the VariablePool model by separating the `value_type` tags for `IntegerSegment`/`FloatSegment` and `IntegerVariable`/`FloatVariable`. Previously, both Integer and Float types shared the same `SegmentType.NUMBER` tag, causing conflicts during serialization.

Key changes:
- Introduce distinct `value_type` tags for Integer and Float segments/variables
- Add `VariableUnion` and `SegmentUnion` types for proper type discrimination
- Leverage Pydantic's discriminated union feature for seamless serialization/deserialization
- Enable accurate serialization of data structures containing these types

Closes #22024.

Signed-off-by: -LAN- <laipz8200@outlook.com>

Signed-off-by: -LAN- <laipz8200@outlook.com>
Co-authored-by: QuantumGhost <obelisk.reg+git@gmail.com>

Signed-off-by: neatguycoding <15627489+NeatGuyCoding@users.noreply.github.com>

Co-authored-by: QuantumGhost <obelisk.reg+git@gmail.com>

Co-authored-by: 刘江波 <jiangbo721@163.com>

Co-authored-by: lizb <lizb@sugon.com>

Co-authored-by: crazywoola <427733928@qq.com>

This pull request introduces a feature aimed at improving the debugging experience during workflow editing. With the addition of variable persistence, the system will automatically retain the output variables from previously executed nodes. These persisted variables can then be reused when debugging subsequent nodes, eliminating the need for repetitive manual input.

By streamlining this aspect of the workflow, the feature minimizes user errors and significantly reduces debugging effort, offering a smoother and more efficient experience.

Key highlights of this change:

- Automatic persistence of output variables for executed nodes.
- Reuse of persisted variables to simplify input steps for nodes requiring them (e.g., `code`, `template`, `variable_assigner`).
- Enhanced debugging experience with reduced friction.

Closes #19735.

Co-authored-by: lizb <lizb@sugon.com>

Co-authored-by: tech <cto@sb>

Co-authored-by: tech <cto@sb>