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(ui): keep a ref report's connection overlay, +4 edit-flow defects
None of these five touched the secrets mechanism, which the review pass
traced end to end without breaking; all five were in what surrounds it.
A ref-based report's report-local connectionString was deleted on save.
The wizard offers no connection field for a registered source, so the
save path dropped it — but a report-local overlay is legitimate config
under D42 (report-local wins), and deleting it silently repointed the
report at the registry's connection. A stored one is kept as it arrived;
one is still never invented, since there is no field to invent it from.
The matching banner also stopped rendering for ref sources, where it
pointed at a control that is not on the page.
A failed GET .../config was indistinguishable from "not editable", so
Edit degraded to a blank create wizard with no message — inviting the
user to retype a whole report over a working one. The more useful
observation is that this is the same conflation _sourcesLoaded had just
been added to fix one function above: I fixed the instance, not the
pattern.
A corrupt STORED document was a 400 on PUT while GET .../config answered
the identical condition with a 500, blaming the caller for a file they
never sent.
validate?for= reported the report's own name as taken, putting "name
already taken" under every successful edit validation.
Changing the source mid-edit left no way forward: the old credential is
correctly dropped, but nothing said so and the save failed with a generic
compile error.
Each fix verified by reverting it and confirming the new test fails, then
the full suite: 1 156 tests green.
<span style="font-size:12px">You changed the source from what "@Wizard.EditingOriginalName" was reading, so its stored connection was not carried over — restoring it into a different source is not something the engine can assume. Name an environment variable below; savingwithoutoneisrejected.</span>
0 commit comments