New Feature: Add support for parsing JSON-like Content-types

[diosney]

For instance, the ability to parse Content-types === 'xxx+json', like application/vnd.api+json, fi.

Currently bodyParser.json() only parses Content-types === 'application/json', which is very limited.

Thanks

Related: #13

[dougwilson]

I think we can easily add this as the option to accept a string in the options object and just provide that string to type-is.

[Fishrock123]

I'm not 100% sure how type-is works, but I think that would mean the new string would become the only correct JSON type.

Imo, the easiest and best way to fix this is just like /json/.test(req.headers['content-type']).

[dougwilson]

That is how type-is works, but it's perfectly fine. If you want to parse both application/json and application/vnd.api+json you would just do:

app.use(bodyParser.json())
app.use(bodyParser.json({type: 'application/vnd.api+json'}))

Using a parser for each type also would let the user do stuff like giving a different reviver per type.

[Fishrock123]

+1 didn't really know you could do that.

[diosney]

@dougwilson: Neat! I like the new way :) Thanks!

When this feature will be get published in the npm registry?

[dougwilson]

When this feature will be get published in the npm registry?

As soon as I can, so probably today some time. I like to let the potential release sit a bit before hitting "publish" so I can think on it and prevent some dumb mistake :)

[Fishrock123]

Also gives time for people (read: me) to land doc nits before the next release hah. :P

[dougwilson]

@Fishrock123 I saw that commit, haha.

[dougwilson]

@diosney published as 1.1.0

[diosney]

@dougwilson Thanks! I already tested it and worked like a charm. :)

Thanks again for your hard work :)