support for merge-patch json or perhaps generic json type registration? #891
Description
At
kin-openapi/openapi3filter/req_resp_decoder.go
Line 1006 in 62bf0f7
In an application I'm working with I need to support application/merge-patch+json (from RFC 7386 The jsonBodyDecoder decoder should do the trick.
Since +json formats seem to propagate would it make sense to make JsonBodyDecoder as public, so that people can associate media-types in an ad hoc fashion?
I'm currently on an older kin-openapi version (for "reasons") so I will likely register my own duplicated decoder, but it occurred to me that something generic might be useful, so thought I'd put the idea up here for comments.
What do you think?