You do not need to switch an application from JSON to TOON all at once. DevOp.Toon supports a practical migration path where both formats can coexist.
using DevOp.Toon;
var service = new ToonService();
string toon = service.Json2Toon("""
{
"id": 42,
"name": "Widget",
"tags": ["sale", "featured"]
}
""");
string json = service.Toon2Json(toon);
JSON interop is useful when:
Start by generating TOON from existing JSON payloads and comparing:
Keep JSON internally for now, but introduce TOON at selected boundaries such as:
Move application services to IToonService and use JSON conversion only where interoperability still matters.
The interop path makes adoption easier, but the biggest long-term gains usually come when TOON becomes a first-class transport or persistence format rather than a temporary conversion step.