optimizely / optimizely/csharp-sdk
[ENHANCEMENT] Consider moving from Newtonsoft to System.Text.Json
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 20
- Forks
- 20
- Avg merge
- 22h 59m
- Merged PRs (30d)
- 1
Description
Description
In general it seems most major libraries are moving way from Newtonsoft to System.Text.Json. It would be good to see this library do the same.
Benefits
System.Text.Json seems to be the future of JSON parsing in .NET and is faster than Newtonsoft.
Detail
No response
Examples
No response
Risks/Downsides
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating every Newtonsoft dependency and serialization entry point in the C# SDK, then compare the required behavior with System.Text.Json. Define the migration scope and compatibility risks before changing anything; done means the SDK no longer relies on Newtonsoft while preserving its current JSON behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100