Peter Wall

Hi Anton, thanks for this. Yes, I am looking into `oneOf` at the moment, in particular for cases like the following: ``` { "$schema": "https://json-schema.org/draft/2019-09/schema", "$id": "https://pwall.net/test-oneof", "title": "Customer", "type":...

Thanks for giving such a comprehensive example. The sort of cases I have been looking at involve the use of a "discriminator" field ("customerType" in my example), which would allow...

I have made two changes to the Code Generator. The first is to allow `oneOf` and `anyOf`, but ignore their contents. The resulting code will in some cases have references...

Hi Myron, I'm sure I don't need to tell you that this is a tricky issue. Producing a solution that meets even a moderate subset of the possible requirements is...

OK, version 0.47 includes an implementation of `oneOf` similar to my `TypeA`/`TypeB`/`TypeC` example above. It generates `interface` rather than `open class`, because base classes can be problematic with data classes....

Hi @trajano , as you will have found if you read the entire thread of this issue, code generation for `oneOf` and `anyOf` is tricky. I don't know what output...

Hi @TheKeeperOfPie – sorry it's taken me so long to get back to you – I'm on vacation at the moment and I've only just got a moment to myself...

Hi - thanks for these suggestions. On the first point, using the `const` value as a parameter to the base constructor from the derived class - I like the idea,...

In regard to the question of the recommended way of defining classes that are to be deserialized polymorphically - yes, I support the idea of defining a a "type" field...

Keep it open - I have worked out a fix for that missing validation bug, and I should be able to get a new version uploaded to Maven Central within...