Blazor JS import/export interop updates #29102
Merged
Conversation
This file contains 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
pavelsavara
approved these changes
Apr 27, 2023
|
There are no changes yet. I keep hoping that I will find time to work on it. |
|
Ok ... I'll get this in. Thanks. |
Donciavas
pushed a commit
to Donciavas/AspNetCore.Docs
that referenced
this pull request
Feb 7, 2024
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.
Fixes #29101
I thought import/export JS interop might replace the prior interop approaches for .NET 8, but that doesn't seem to be the case. Here, I'm making minor updates to extend the existing SxS coverage into .NET 8.
Pavel, are there any changes that we need to make for .NET 8 coverage?
Internal previews
[JSImport]/[JSExport]interop with ASP.NET Core Blazor