user params instead of query_parameters for nicer route paths

[elfassy]

support for both (right now only the second is supported)

/api/v1/route
/api/route?api_version=1

Example routes file

namespace :api, defaults: {format: :json} do
      scope "(v:api_version)" do
          get 'route' ...
     end
end

[coveralls]

Coverage remained the same when pulling 81d1bfe on elfassy:master into 8ca3091 on bwillis:master.

[coveralls]

Coverage remained the same when pulling 9c76f3c on elfassy:master into 8ca3091 on bwillis:master.

[bwillis]

Thanks for the pull request @elfassy. I remember using params originally and found that it was very overloaded. As I understand, params is the amalgamation of url params, query params as well as request params and Rails dictates what takes priority.

My intent was to allow the user, through configuration, to specify the priority, for example:

config.view_version_extraction_strategy = [:request_parameter, :query_parameter]

So, what you have found is that we are not addressing the url params. Can you see a way we can add the url params into this strategy and preserve priority?

[elfassy]

Hi @bwillis. Thanks for this gem!
We can add a path_parameters strategy. I'll give it a shot, let me know what you think.

[bwillis]

That sounds like a great idea, looking forward to the update 👍

[elfassy]

#18