Patchloom 0.37.3

What's new in 0.37.3

Patchloom 0.37.3
YAML is parsed without the archived unsafe-libyaml crate. Edits to ini
files, markdown lists, and document moves keep the surrounding text
instead of rewriting or deleting it.
Highlights
Unquoted yes, no, on, and off in YAML stay strings. doc set
on an ini line keeps the spaces around = and a spaced ; or #
note. md upsert-bullet puts the new item in that heading's list,
before a nested heading. doc move refuses to replace a key that
already has a value, and [0], 0, and 00 name the same array slot.
Bug fixes
- YAML was parsed with the archived unsafe-libyaml crate.
Parsing now uses noyalib. Unquoted yes, no, on, and off
stay strings. A document doc set still appends a trailing newline
when the serializer omits one (#2668).
- doc set on port = 8080 ; primary rewrote the line as port=9090.
The spaces around = disappeared and the note was deleted. The
edited line now keeps that spacing and the note. A new value that
would be read back shorter, because a space before ; or #
starts a comment, is invalid_input and the file stays unchanged.
8080;primary and foo#bar stay part of the value (#2673).
- replace told every refused file to pass --allow-absent-old.
A file that simply did not contain the pattern printed that hint.
The hint is now only for exact_old_absent, when a fuzzy candidate
was found and not written. A plain miss prints refused PATH: no_matches (#2674).
- md upsert-bullet placed the new item after a nested section.
Adding - beta under # List wrote it after the body of ## Other,
so it read as part of that section. The new item stays with the
heading's own list, before the first child heading. A bullet that
exists only under the child is not treated as already present.
A second upsert of the same item does not add it again (#2675).
- doc move onto a key that already had a value replaced that value.
Moving server.http onto server.host exited 0 and replaced
localhost with 8080. The command now returns already_exists
and leaves the file unchanged. Moving a field into an earlier array
slot no longer clears the sibling that slid into the old index (#2676).
- doc move treated [0], 0, and 00 as different array slots.
Moving items[0].child to items.0.child.nested deleted the value
and exited 0. The same destination written as items[0].child.nested
was already refused. rows[0][0] to rows.0[2] wrote the values in
the wrong order, and rows[0][0] to rows.0[1] left the array
unchanged. …

Full release notes »