From cb0c5bd0decb58209ff849fef9b3d08e5328644d Mon Sep 17 00:00:00 2001 From: Kyle Kukshtel Date: Sat, 7 Dec 2024 13:17:21 -0500 Subject: [PATCH] update type mappings link for JS interop (old one 404s) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 170591e..73be197 100644 --- a/README.md +++ b/README.md @@ -201,7 +201,7 @@ Most of the marshalled types work in both directions, as parameters and as retur The following table details supported type mappings: -[.NET 8 JS Interop Type Mapping](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/includes/js-interop/8.0/import-export-interop-mappings.md) +[.NET 8 JS Interop Type Mapping](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/client-side/dotnet-interop/index.md#type-mappings) Note, some combinations of type mappings that require nested generic types in `JSMarshalAs` are not currently supported. For example, attempting to materialize an array from a JS promise such as `[return: JSMarshalAs>>()]` will generate a compile time error. An appropriate workaround will vary depending on the scenario, but this specific scenario explored in the [Type Mapping Limitations](#type-mapping-limitations)] section.