Skip to content

Add STJ 8.0.5 #1060

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

Merged
merged 2 commits into from
Oct 15, 2024
Merged

Add STJ 8.0.5 #1060

merged 2 commits into from
Oct 15, 2024

Conversation

marcpopMSFT
Copy link
Member

I ran the generate command, added the STJ items, and updated the build.props. We need it for this and various other PRs into the templating repo which has a hardcoded STJ version as it doesn't get it through codeflow: dotnet/templating#8430

I'm a bit surprised no one else needed a the SBRP update for STJ.

@marcpopMSFT marcpopMSFT requested a review from a team as a code owner October 14, 2024 22:44

public sealed partial class JsonCollectionInfoValues<TCollection>
{
public JsonTypeInfo ElementInfo { get { throw null; } init { } }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The init is incorrectly generated here and should be changed to set. See #861 (comment).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a plan to update the tooling to handle this? This is already far too much friction for updating a single version number and it's only going to get worse as the push to get these updated asap ramps up.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the generate command when I ran it generated a bunch of additional files that I had to mentally filter out for other packages (System.Text.Encodings.Web, System.Runtime.InteropServices, and Microsoft.Bcl.asyncingterfaces). It'd be great to clean up the generation tool for that as well because if we're going to enable nuget audit and be updating packages regularly that aren't in source build, we need the process to be as smooth as possible.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the generate command when I ran it generated a bunch of additional files that I had to mentally filter out for other packages (System.Text.Encodings.Web, System.Runtime.InteropServices, and Microsoft.Bcl.asyncingterfaces). It'd be great to clean up the generation tool for that as well because if we're going to enable nuget audit and be updating packages regularly that aren't in source build, we need the process to be as smooth as possible.

This is called out in https://github.com/dotnet/source-build-reference-packages?tab=readme-ov-file#workflow. It is ok to include those changes.

@marcpopMSFT marcpopMSFT requested a review from mthalman October 15, 2024 18:26
@mthalman mthalman merged commit 4660d88 into dotnet:main Oct 15, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants