Repository navigation
fix: preserve source and business identity in stateful UI captures - #84
Merged
Merged
Conversation
|
View your CI Pipeline Execution ↗ for commit d76e51d
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hoppscotch exposed three broken handoff paths: initialization failed alongside application Zod3, source queries captured shared-button wrapper props, and a portable Generate Token locator also resolved in another collection's dialog.
Pin browser-shared schemas to Zod4 and declare React/Vue injected dependencies before Vite optimization. Capture the proved Vue source owner through ancestry, label fallback context, and pin the instance across asynchronous manifest lookup. Require a stable non-secret data-ds-context per enclosing dialog; unscoped and legacy dialog locators refuse replay. Preserve useful refusal reasons through HTTP/WS/MCP. Redact OAuth client-secret fields and marked-secret records before serialization limits can discard their marker.
Validation:
Source-owner matching is Vue-specific and depends on exact dev metadata. Other adapters label nearest/unavailable context. Dialog replay requires an application context key; it does not infer business identity or restore backend/auth state. These capabilities remain unpublished until a separately authorized release.