Get transforms to Post if params given

[rodrieiz]

I have the same issue that is mentioned here.
I think this is a possible solution that worked for me.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.08%. Comparing base (53ad9b1) to head (5cccb81).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #230   +/-   ##
=======================================
  Coverage   97.08%   97.08%           
=======================================
  Files          20       20           
  Lines         618      618           
  Branches      142      142           
=======================================
  Hits          600      600           
  Misses         18       18           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[exoego]

I don't get the issue.
Why you need to specify as: :json for get HTTP method?

[exoego]

As the rspec-rails issue said,

      get "/users/1/billing_addresses",
          as: :json,
          headers: {},
          params: { some_param: {} } 

actually fails with No route matched for POST /users/1/billing_addresses, but it still fails even with this PR.

Please add a failing test first then change codes to fix the test.

[rodrieiz]

I don't get the issue. Why you need to specify as: :json for get HTTP method?

Looking for an answer to your question about why I have to use as: :json, I think that's the issue. I shouldn't use it in GET requests. But since it was like that throughout the entire project, I kept using it. Thanks.

[rodrieiz]

As the rspec-rails issue said,

      get "/users/1/billing_addresses",
          as: :json,
          headers: {},
          params: { some_param: {} } 

actually fails with No route matched for POST /users/1/billing_addresses, but it still fails even with this PR.

Please add a failing test first then change codes to fix the test.

In my case, the tests don't fail neither before nor after the PR. It's just that before, the documentation documented the endpoint as POST instead of GET. But as I mentioned in the previous comment, I think the issue lies in using as: :json