When navigating via a response body link (e.g., #pets/{petId}/GET?petId=42), the link value overrides a pinned value (petId=99). The pin icon still shows "pinned" but the displayed value isn't the pinned one. This is confusing.
More broadly, users might want to pin multiple value sets for the same operation — e.g., pin petId=42 for one workflow and petId=99 for another, and switch between them.
This needs deeper thinking about:
- How to visualize "pinned but overridden by link navigation"
- Whether to support multiple named pin sets (like browser profiles or test scenarios)
- How pin sets interact with link navigation and bookmarks
- Storage model for multiple sets
Discovered while redesigning body links to use real <a href> with query parameters (#4).
When navigating via a response body link (e.g.,
#pets/{petId}/GET?petId=42), the link value overrides a pinned value (petId=99). The pin icon still shows "pinned" but the displayed value isn't the pinned one. This is confusing.More broadly, users might want to pin multiple value sets for the same operation — e.g., pin
petId=42for one workflow andpetId=99for another, and switch between them.This needs deeper thinking about:
Discovered while redesigning body links to use real
<a href>with query parameters (#4).