Add as to encode a request as a specific mime type.

[kaspth]

Turns longish integration test setup like

post articles_path(format: :json), params: { article: { title: 'Ahoy!' } }.to_json,
  headers: { 'Content-Type' => 'application/json' }

into

post articles_path, params: { article: { title: 'Ahoy!' } }, as: :json

And removes the need to add helpers like post_json etc.

I'm not sure if encoder is the term to use internally. Perhaps interpreter would be better. Suggestions welcome.

Perhaps we'd need more mime types. Suggestions welcome.

[kaspth]

All right, added some tests and documentation.

[kaspth]

Am I right in making this claim? Definitely feels like it could use some shine, but don't have a fully formed idea of which direction to take it.

[rafaelfranca]

I don't think so. Try to test it in a controller with curl.

[arthurnn]

I like the idea behind this. 👍 I remember having to do those setups before, and indeed we could make that setup easier.

[arthurnn]

dont forget to add a changelog for it.

[kaspth]

Should probably do a test for how much of an impact this has on our integration test speed.

[rafaelfranca]

Can we defer the path parsing to append_format_to? If we don't need to append a format and if the paths is not a full path there is no need to parsing.

[kaspth]

@arthurnn cool 😁

[kaspth]

@rafaelfranca tried your suggestion to call a custom controller via curl, but couldn't get it to work.

When I byebug request_parameters it seems to fetch_header which calls @env.fetch which already seems to have an empty hash for that key. Would you have any ideas why? I'll keep digging 😁

[kaspth]

Reworked this to use Mime types as well, which simplified the tiny public API some more.

[dhh]

Lovely! We have one of those annoying post_json helpers as well.