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
Add nullness warnings in JsonParse #9595
Conversation
da3145b
to
2ad44d9
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
What's the correct way to link to a method when I don't care which overload I'm linking to? The bot appears to be complaining that |
It should be |
This comment was marked as outdated.
This comment was marked as outdated.
Looks like this feature does not work with cref. Try converting remarks to markdown (like there: https://github.com/dotnet/dotnet-api-docs/blob/main/xml/System.Reflection.Metadata/MetadataReader.xml#L40) and use xref syntax:
|
Learn Build status updates of commit a884853: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
You can link to the overloads page using cref (see https://learn.microsoft.com/contribute/content/dotnet/api-documentation#cross-references):
|
Is this something you would prefer me to do instead of what's currently on the branch? The round-trip time is very long and I can't even see the result. |
I updated it. I would also like @eiriktsarpalis to review this PR before we merge it. |
This comment was marked as outdated.
This comment was marked as outdated.
Learn Build status updates of commit aac16ce: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Summary
Today I discovered the surprising fact that
JsonNode.Parse(x).ToJsonString()
may throw on valid inputs. It seems reasonable to document this.