api keyword without specifying the verb/path loads values from routes

[iNecas]

No description provided.

[mtparet]

Nice, thanks for the multiple routes additional feature!

[iNecas]

I've done more testing on our project, discovered and fixed some issues with more complex nesting of routes (with constraints, scopes etc).

We will probably want to be able to determine the way of processing of the route specs into
the path in documentation:

https://github.com/Pajk/apipie-rails/pull/194/files#diff-c252ba104efd0ecb906ad2edd58ce884R71

as folks might have different preferences on if to include the format, braces for optional params etc.
something like Apipie.configuration.routes_path_formatter = lambda { |spec| spec.gsub(/[()]/, '') }

What do you think?

[mtparet]

Yes, it would be nice having a configuration setting for the formatter of the route path, to have more flexibility.

[mtparet]

I added the functionality here ifeelgoods@624cbf3

(I reset my branch on yours #187 )

[komidore64]

does this allow you to still give a description for the route? like:

api :description => "This is the route description to the following controller action."

[mtparet]

@komidore64 Yes, it should keep all others previous behaviors. (otherwise it means there is a bug)

[mtparet]

We can close this PR @iNecas

[Pajk]

@iNecas Closing this PR as this feature is already in master through @mtparet PR if I understand it correctly:).