-
Notifications
You must be signed in to change notification settings - Fork 10.5k
IJSUnmarshalledObjectReference for unmarshalled JS interop calls on JavaScript objects. Fixes #25208 #25548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IJSUnmarshalledObjectReference for unmarshalled JS interop calls on JavaScript objects. Fixes #25208 #25548
Conversation
ad7c3cf to
a575bf7
Compare
src/Components/WebAssembly/JSInterop/src/WebAssemblyJSRuntime.cs
Outdated
Show resolved
Hide resolved
src/JSInterop/Microsoft.JSInterop/src/Properties/AssemblyInfo.cs
Outdated
Show resolved
Hide resolved
…into t-mabuc/js-unmarshalled-object-reference
src/JSInterop/Microsoft.JSInterop/src/Implementation/JSObjectReference.cs
Show resolved
Hide resolved
src/Components/WebAssembly/WebAssembly/src/Rendering/WebAssemblyRenderer.cs
Show resolved
Hide resolved
SteveSandersonMS
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fantastic - awesome work here!
|
Hello human! Please make sure you've included the Shiproom Template in a comment or (preferably) the PR description. Also, make sure this PR is not marked as a draft and is ready-to-merge. |
|
@Pilchie can we get your approve here for RC2? |
|
Approved for .NET 5 RC2. |
Description
Added
IJSUnmarshalledObjectReference, allowing high-performance JS interop calls on Blazor WebAssembly.Customer Impact
Component vendors may utilize unmarshalled JS interop calls for improved performance.
Regression?
No.
Risk
Little risk - this is an area that is well tested.
Addresses #25208