Why enforcing content-type? about mappersmith HOT 3 CLOSED

Hi @ericholiveira, thanks for opening this issue. I agree with you, Mappersmith should always follow the user defined content-type. Currently, you can prevent Mappersmith from guessing the content type by setting the body attribute to something different than an object, example:

Client.Photo.save({
  category: 'family',
  body: JSON.stringify({year: 2015, tags: ['party', 'family']})
})

I will fix this and release a new version. Thanks for your input!

from mappersmith.

Great... ive tried like you said before opening this issue and what i got was a request with content-type "application/x-www-form-urlencoded; charset=UTF-8; application/json" , the body was sent correctly, as a json string, but the server could read because this wasnt an explicit application/json header.

Anyway, thx for the help :)

from mappersmith.

I released version 0.13.2 with this fix. Thanks for your input.

from mappersmith.