feat: export unwrapProxy and IS_PROXIED from public API#6
Merged
Conversation
Allows consumers to manually unwrap @persist proxies for structuredClone and other non-RPC serialization use cases. Related to cloudflare#100
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.
Summary
Exports
unwrapProxyandIS_PROXIEDfrom the main package entry point.Problem
The
unwrapProxyfunction was added in PR #5 (cherry-pick of cloudflare#100) but only used internally for RPC auto-unwrapping.Consumers need direct access to
unwrapProxyfor:structuredClone()calls on @persist objectsSolution
Export both symbols from
index.ts:unwrapProxy<T>(value: T): T- Recursively strips proxy wrappersIS_PROXIED- Symbol to detect proxied objectsUsage