-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Update source-gen APIs according to review #59042
Conversation
Note regarding the This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change. |
Tagging subscribers to this area: @eiriktsarpalis, @layomia Issue DetailsImplements API approved in #45448 (comment). These are cosmetic changes to APIs called by generated code to configure type metadata, to make them easier to extend with new features in future versions of the generator/STJ. Should be ported to 6.0.
|
src/libraries/System.Text.Json/gen/JsonSourceGenerator.Emitter.cs
Outdated
Show resolved
Hide resolved
I want to call out new commit 4ce31e9 ("Rename fast-path func name and add src-gen/JsonNode interop support"). It implements the proposed API for tomorrow - #45448 (comment). |
...em.Text.Json/tests/System.Text.Json.SourceGeneration.Tests/Serialization/NodeInteropTests.cs
Show resolved
Hide resolved
...braries/System.Text.Json/src/System/Text/Json/Serialization/Metadata/JsonMetadataServices.cs
Show resolved
Hide resolved
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.
LGTM pending API approval especially around the SerializeHandler\Serialize changes.
Possible Mono\WASM issues:
|
API has been approved, so this is good to merge when green - #45448 (comment). |
@lewing @radical @SamMonoRT - Have any of you seen the failure before? It appears to be an issue with WASM AOT.
|
@lewing @radekdoulik Could this be due to running out of memory, or other resources? |
Was chatting with @eerhardt about the AOT failure offline.. FWIW I wanted to note that the size of the test .dll in question here ( |
cc @vargaz |
/backport to release/6.0-rc2 |
Started backporting to release/6.0-rc2: https://github.com/dotnet/runtime/actions/runs/1244163258 |
I thought RC1 is our go-live release and people can start shipping on it, including e.g. publishing NuGet packages with pregenerated code in it. Will the NuGet packages using the RC1 S.T.Json source generator be usable on the RTM runtime? I'm looking at a |
@MichalStrehovsky support for go-live releases like RC1 ends as soon as the next one goes out, RC2 in this case. |
In the past, we have sometimes treated APIs in the go-live releases as frozen. We are clearly not doing that this time. I have added dotnet/core#6570 (comment) to make sure we mention this in the .NET 6 RC2 announcement. |
Implements API approved in #45448 (comment). These are cosmetic changes to APIs called by generated code to configure type metadata, to make them easier to extend with new features in future versions of the generator/STJ.
Should be ported to 6.0.