-
Notifications
You must be signed in to change notification settings - Fork 26
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
System.Text #171
Comments
Hi @Brilbroeder its not something currently on the roadmap but I'm not opposed to the next major version switching. Curious what other projects (example stripe/stripe-dotnet#2495) are doing and what advantages it would bring? |
I have seen project that by default have system.text as the json (de)serializer but that allow to switch to newtonsoft in configuration. I've had projects that had really weird behaviour and after some days of trial-and-error to found out that a version conflict of newtonsoft was the source of evil. Hence I have developped some preference for System.Text. System.Text as a json serializer is as at least perfomant as newtonsoft, but with some specialised niche features missing. So in most case system.text would be just fine. I've had a project with a mix of system.text and newtonsoft, given both have classes with the same name, things got mixed up and was not working. Use the correct namespace at the correct location, and all worked fine. Hence I try to use one (de)serialization library per solution to avoid these kind of issues ;-) |
Ok, I could get behind switching outright in the next major version. I don't think it makes sense to support targeting both. I don't have any timeframe in mind, but PRs are welcome |
Is a System.Text compatible version on the roadmap ?
The text was updated successfully, but these errors were encountered: