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
MINOR: yml: support inline maps and reject scalar exit-code-map
The parser only knew inline lists, so exit-code-map: {SIGTERM: 0}
parsed as a scalar string. StringMap() on a scalar returns an empty
map and parseProcess guards on len > 0, so the whole remap table was
silently dropped: the config loaded clean and on-failure fired on the
supposedly remapped exit code.
Teach parseScalar the flow-mapping form, recursively and under the
same maxParseDepth cap as block nesting. splitCSV now tracks []/{}
depth so commas inside nested structures or quotes do not split
entries, and inline maps get the same strictness as block maps:
missing colons and duplicate keys fail with line numbers. Sequence
items written as inline maps parse as mappings too.
Also validate exit-code-map at load: a scalar or list value is now a
config error naming the process and the expected form, instead of a
silent no-op. An absent or empty key stays legal. environment and
signal-rewrite gain the inline form for free via the shared parser.
0 commit comments