-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Developers using System.Text.Json have their top requests addressed so that they can use STJ in more scenarios #45190
Comments
JsonSerializer TimeSpan support - is very important, everyone run back to Newtonsoft because of this. |
The pace is too slow, everyone need this features now. maybe put it in 5.0.2 or 5.1 is better. |
Allow support for non-public members +++++ |
Can any of these be plugged in naturally by a 3rd party if they had the right extensibility support? A 3rd party library can evolve so much easier than .NET |
Failing null deserialization on non-nullable references types (#1256) would be awesome. Right now we have to check the entire children tree whether there was a null value, which is very annoying. |
Please allow to leave "null" when serialize unsupported types. |
@BreyerW I was updating the related issue #40099 as done for 6.0 and noticed that #42163 is marked for "Future". I recall discussing it with @jozkee earlier - it strikes me as a niche and design-heavy problem that we might not get to in 6.0. It would be good to see more feedback from other customers to prioritize the work for the current release. My intention when adding it to this list was to remember assess to its feasibility for 6.0. At this point it seems unlikely, given the other JSON work we need to do in this release (https://themesof.net/?q=json%20is:open%20kinds:teu). Can we continue the discussion over at #42163? The feature to deserialize into an existing object (#29538) was mentioned as a potential workaround and is more likely to make it to 6.0 given it's relative technical simplicity, precedent in Newtonsoft.Json, and demand from multiple customers. |
Please, also add support for the new DateOnly and TimeOnly structs. |
I updated the work items: Added
Moved to "More extensible object and collection converters" #36785
Moved to future
These are good features but can be addressed later given other work we need to do for this release. |
I know Ideally I'd like to reuse the same DTO types in
For example, I have a class that represents a Click to expand!
|
This is tracked by #31511.
Kindly open a new issue to track this feature request.
This is generally tracked by #44428. Please add a note on that issue describing the sort of functionality enhancements you'd like to see. |
Triage - we can consider this work done and I'll close this issue. We've addressed what we could in the .NET 6.0 timeframe, and can consider the other tasks in .NET 7.0 planning. |
Work
Utf8JsonWriter
Writing raw JSON values when using Utf8JsonWriter #1784The text was updated successfully, but these errors were encountered: