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
feat(ir): validate front-matter task steps against typed builders
Add a parse direction to the typed task builders: parse_task_step()
deserializes an authored ADO task-step mapping and validates it by
reusing the builder structs as the schema. Derive Deserialize (keyed on
ADO input names, deny_unknown_fields) on CopyFiles and the Docker@2
command variants, plus a flexible bool deserializer accepting both rue
and "true".
Partial coverage is safe and additive: parse_task_step returns
Ok(Some(TaskStep)) for a recognized+valid step, Ok(None) for anything not
modeled (unmapped task or non-task step) so the caller keeps the original
YAML as today's opaque passthrough, and Err only for a recognized task
with invalid inputs (missing required, unknown key, bad value, or an
input for the wrong command). Wired up for CopyFiles@2 and Docker@2 as a
proof of concept.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
0 commit comments