I would like to map actions on collections of resources using
Mapper.resource, not just for a single method (POST, GET, etc.), but
for any. I noticed there is a check for this in mapper.py line 679,
which does not add method requirements if the method name is 'any'.
However if seems to be checking the wrong case. For example:
mapper.resource('user', 'users', collection={'login': 'any'})
should match all of:
POST, GET, PUT, DELETE /users/login
But instead matches none of these. In mapper.py line 679, it skips
adding a method requirement to the route if the method is 'any'
(lowercase). However by this stage all of the method names have been
uppercased (by swap, line 641), so we end up with a requirement of the
method literally being "ANY".
Assuming this is the desired behavior, it might be as easy to fix as
ignoring the case when performing this check.
Stephen Emslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
