Support custom deserialization and primitive strings

[gaffney]

I have a DateRanges object that, while having a "start" and "end" member, is deserialized as a primitive array, e.g. ['20130210-20130315','20130520-20130524'] rather than

[
  {
    "start":"2013-02-10",
    "end":"2013-03-15"
   },
  {
    "start":"2013-05-20",
    "end":"2013-05-24"
  }
]

since I use @JsonValue in the Set<DateRange> getter. (And DateRange has it's start and end elements ignored with @JsonIgnore.)

That said, my Json object already does this properly (and I have custom deserializer for each in the ObjectMapper), but I don't believe I have a way of telling Swagger to use my parser. The model it shows in the UI is totally off.

[gaffney]

And yes I realize I can use a model converter; my point here is that I shouldn't have to.

[fehguy]

Hi, I'm happy to merge any commonly-used formatters into the core. There are a lot of combinations so we haven't covered them all. If you'd like to join in and contribute, it'd be appreciated.

[rage-shadowman]

A validating regex format parameter would be a good addition for string query parameters. Then you could describe the query parameter: DateRange in string format [show format here]

[fehguy]

Hi, you should be able to use the fix in #588 to address the same goal.