Laurent Bovet

Or generate `addToDescendants(String element)` Easier to realize and conceptually correct.

I suggest that we provide this feature "behind a flag", i.e. that the current behavior stays the default and that we activate the "non-required-as-nullable" feature explicitely and on demand.

This should actually be solved in the NJsonSchema project, I think. This line sets the nullability (the "?") of the generated property: https://github.com/RSuter/NJsonSchema/blob/master/src/NJsonSchema.CodeGeneration.CSharp/Models/PropertyModel.cs#L42 It uses only the "nullable" property and...

Please try with an intermediate definition, e.g. ``` json "definitions" : { "d": { "type": "object", "oneOf": [ { "$ref": "#/definitions/a" }, { "$ref": "#/definitions/b" }, { "$ref": "#/definitions/c" }...

Many thanks for this contribution. I was pretty sure that such a feature would be the first to be requested :) As you say, the merge strategy should be adaptable...

I'm willing to fix this but it's difficult to find the time these days. As a workaround, you can create another for/sequence for the intermediate items: ```yaml seq: !- -...

I think it should be possible to make slf4j work with GWT with the help of some third-party project (https://github.com/bmeurer/gwt-slf4j) I will try to make this work and also the...

I use this in some corporate project. Basically, in a GWT project, you and then you can directly write a JSNI function that returns the a jQuery promise like this:...

Yes, this is an intermediate solution until there is something better integrated with the multi-target approach.

Not planned. This was a small explorative project. I may find time to build and publish the artifact on GitHub maven repo.