-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Issue 104700: Clarify error message for collection property with no getter #104861
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
Closed
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -610,6 +610,23 @@ public class ClassWithRequiredExtensionDataProperty | |
| public required Dictionary<string, JsonElement>? TestExtensionData { get; set; } | ||
| } | ||
|
|
||
| [Fact] | ||
| public async Task RequiredCollectionPropertyWithoutGetterThrows() | ||
| { | ||
| string json = """{"Foo":"foo","Bar":"bar"}"""; | ||
| InvalidOperationException exception = await Assert.ThrowsAsync<InvalidOperationException>( | ||
| async () => await Serializer.DeserializeWrapper<ClassWithRequiredCollectionPropertyWithoutGetter>(json)); | ||
| Assert.Contains(nameof(ClassWithRequiredCollectionPropertyWithoutGetter.TestCollectionPropertyWithoutGetter), exception.Message); | ||
| } | ||
|
|
||
| public class ClassWithRequiredCollectionPropertyWithoutGetter | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Just to make sure we're not regressing things here, could you also add a test for class like so: class ClassWithCollectionCtorParam(Dictionary<string, JsonElement> value)
{
public Dictionary<string, JsonElement> Value { get; } = value;
}And then try to deserialize it using an |
||
| { | ||
| public required Dictionary<string, JsonElement>? TestCollectionPropertyWithoutGetter | ||
| { | ||
| set => TestCollectionPropertyWithoutGetter = value; | ||
| } | ||
| } | ||
|
|
||
| [Fact] | ||
| public async Task RequiredKeywordAndJsonRequiredCustomAttributeWorkCorrectlyTogether() | ||
| { | ||
|
|
||
This file contains hidden or 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
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.
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.
I don't think this is the correct way to address the problem. A fix should instead try to make the scenario work as expected. If you remove
JsonRequiredfrom the repro in #104700 then deserialization works as expected and this should too.