Optional Support

[yehuda-c]

Would be great if there was a way to configure this to serialize / deserialize json schema fields using Java 8 Optionals, so that fields of type T with required=false are deserialized to Optional and fields with required=true are deserialized to T rather than needing to use @JsonAttribute annotations.

[cowtowncoder]

I am not sure how this is related to what this module does, JSON Schema generation?

[yehuda-c]

JSON Schema generation will have a required field set to true or false. If this is settable based on whether the POJO contains an Optional, that would be amazing. For example:

{
  "type": "object",
  "properties": {
    "street_address": { "type": "string" },
    "city":           { "type": "string" },
    "state":          { "type": "string" }
  },
  "required": ["state"]
}

Would produce the pojo

public class Example {
    Optional<String> streetAddress;
    Optional<String> city;
    String state;
}

Does that explain this better?

[cowtowncoder]

@yehudacohen Yes, that helps. Now, I was under impression that Optional (and other "reference types") did indeed set required to false, but if this is not the case it should be changed to do so.
Reverse (non-Optional marked as required) can not be made to work easily, although explicit required=true for @JsonProperty does do that.

Which version have you tried this with? Just want to verify that behavior you see is the latest one with 2.8.6.

[owulff]

I'm looking for this feature (generate Optional generic) as well to be able to differentiate between a field which is set to null (default initialized) and not sent (optional).

[cowtowncoder]

At this point I would need to know exactly what THIS module would need to do differently.
Since module does not serialize/deserialize anything, either directly, or via jackson-databind, I wonder if this belongs to some other tool like "schema to pojo" generators.