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
fix(config): let only one bag claim a placeholder's address, +3 UI defects
The first finding corrects this branch's own reasoning. When the
addressed placeholder was introduced I considered requiring the address
to match the slot it appears in and rejected it, because a legitimate
removal shifts positions. Right rejection, wrong rule: the address never
needed to match the POSITION, it needed to be claimed by only one bag.
Duplicating a section by hand — which the new banners tell users to do
for anything the wizard cannot edit — copies its placeholders too, and
both copies resolved to the same stored credential. Many placeholders
inside one bag share its address and always will; two different bags
naming the same one is now a 400.
A transient GET /sources failure repointed a report: the Builder cleared
source.ref when the list came back empty, and a failed call was
indistinguishable from an empty one, so a blip converted a
registry-backed report into an inline one on save.
Format and destination ids were matched ordinally while the engine
resolves them case-insensitively — a stored "CSV" with the csv checkbox
ticked counted as two formats and saved two CSV outputs; the same on
destination types dropped the stored properties.
A 404 on PUT was reported as an unreachable engine. A report deleted from
another tab is a rejected request carrying a usable message, and mapping
it to Unavailable threw that message away and blamed the network.
Each fix verified by reverting it and confirming the new test fails, then
the full suite — not only the projects I thought I had touched.
0 commit comments