posts/deserialization-with-schemas/

[giscus[bot]]

posts/deserialization-with-schemas/

This past weekend, I wondered if it was possible to validate JSON as it was being deserialized. For streaming deserialization, this is very difficult, if not impossible. It’s certainly not something that a validator like JsonSchema.Net is set up to do. But I found another option.

https://blog.json-everything.net/posts/deserialization-with-schemas/

[thomwinans]

Greetings. I'm new to your framework but wished to let you know I am grateful for it, especially as a natural part of JSON processing... doing so without a schema validator is not as fun ;-). So thank you.

I like this work especially, as well, and wished to ask how you think it would be accomplishable without POCO. Perhaps rules of sorts, described elsewhere. I will learn and experiment for myself (it may already exist, if so, apologies for my current ignorance).

Tying JSON to objects/classes as a precursor to JSON processing comes with limits in my view... I don't want to code/compile because I may map and enrich before doing so, which means I don't want to use the more traditional DTO as a pattern... I want data in motion as JSON, through JSON pipelines that invoke my APIs, and then I will convert to some class if I'd like or simply persist as JSON, but at my discretion and without intermediate classes.

Again, thanks for your work, I wish you good success, and please pardon my ignorance if what I've said above is already covered/existent.

Best,
Tom

[gregsdennis]

Thanks for the comment, Tom.

I don't think the approach described in this post limits what you want to do. The only thing it does is add schema validation when you do want to deserialize into a class (and it doesn't need to be a POCO). You still have the option to maintain your data as JSON when you want to.