Skip to content

[Refactor/Chore] Clarify variable type naming #30632

@laipz8200

Description

@laipz8200

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Description

Rename the base Variable class to VariableBase and rename VariableUnion to Variable to make the type names match their actual roles (base class vs. Pydantic union for serialization). Update type hints and imports accordingly to improve readability.

Motivation

The current naming makes it easy to confuse the abstract base class with the union type used for serialization. Clarifying the names reduces ambiguity in type hints and helps prevent misuse in runtime checks.

Additional Context

No behavior change expected; this is a naming/type clarity refactor.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions