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
Three real findings:
1. entryMatchesId only did exact string equality, missing the
relative-IRI case (line 639). JSON-LD profiles often write VM
ids as `"#lws-key-1"` which resolve against the document URL.
Without absolutization, fragment-collision detection would walk
PAST an existing relative entry as if free, then merge would
create a duplicate. Now resolves both sides against baseUrl
before comparing. Verified across absolute/relative/object-
wrapped forms.
2. authentication de-dupe had the same blind spot (line 631) —
could push an absolute IRI even when an equivalent "#fragment"
already existed. Now absolutizes both sides via the same helper.
3. PATCH-failure path left the test UI in a stale "ready to test"
state if a prior run had succeeded (line 500). Could mislead a
user into hitting Test with a kid the server may not have. Now
clears lastVmKid, hides testSection, resets testResult in the
catch block.
0 commit comments