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
{{ message }}
Repository navigation
Commit 2964115
Browse filesBrowse the repository at this point in the historyBrowse files
fix(maestro): give target-resolution misses their own typed failure reason
An out-of-range selector index over otherwise-visible matches produced a
resolution with matched/visible evidence but no target, and every miss was
reported with the same generic 'did not resolve to a visible element' text.
assertVisible then accepted the vacuous matched/visible pair, so a flow
could assert an element its selector never selected.
Carry a MaestroTargetFailureReason from the resolution site through the
daemon match projection to the reporter: messages now name the selector
and the actual miss (no match, none visible, index out of range, no usable
geometry), the typed reason rides along in error details, and observation
conditions hold only for an actionable resolution.
0 commit comments