You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 105dff2
Browse filesBrowse the repository at this point in the historyBrowse files
fix: coerce LIST[BOOL] items per RFC 0007 §2.15 (#352)
fix: coerce LIST[BOOL] items per RFC 0007 §2.15
Each LIST[BOOL] item accepts the same values as scalar BOOL
(bool literals, int/float 0/1, true/yes/on/1, false/no/off/0).
Python stored values verbatim, so heterogeneous lists failed
expression evaluation with 'List contains incompatible types' and
homogeneous non-bool spellings silently produced wrongly-typed lists.
Coerce each item to a canonical bool at the job-creation boundary,
reusing the scalar BOOL coercion (moved to a version-agnostic
_bool_coercion module): template defaults and submitted values
(native list and JSON string), gated exactly on LIST_BOOL. This also
covers environment-template merged defaults, which bypass model
validators via model_copy. Per-item failures carry 'Parameter <name>:'
context; JSON parse errors stay verbatim like other list types.
Template objects keep the author's original spellings.
Behavior change: created-Job LIST[BOOL] values are now canonical
booleans (e.g. ["yes","no"] stores and interpolates as true/false),
matching openjd-rs.
Signed-off-by: Yongzhi Wei <276409147+wyongzhi@users.noreply.github.com>
0 commit comments