Add list as base method and allowed_methods decorator

[toast38coza]

Hey, me again:

I added list() to the ModelEndpoint base class so that it is now automatically available at:

/ajax/{app}/{model}/list.json

I also added a decorator called allowed_methods which can be used to limit the methods that can be accessed on a ModelEndpoint.

The idea is that you decorate your ModelEndpoint's authenticate model with it.

Something like:

class CategoryEndpoint(ajax.endpoints.ModelEndpoint):

@allowed_methods(['get','list'])
def authenticate(self, request, application, method):        
    return True

    ...

I also updated the README to reflect these changes.

As before .. feel free to use or discard as you like :)

[joestump]

This is a really awesome pull request. If you want to rejigger it a bit, I'm ready to merge. :)

[toast38coza]

Re-jiggering done. Had some questions re: #r488266. Let me know what you think about those, and I will make any appropriate changes, then we should be good to go :).

[joestump]

Shit. I waited far too long to followup on this. To answer your questions:

• I think it'd be a good idea to add support for Meta which would allow you to add per-Model limits, etc.
• I see your point on the pagination class. Let's just roll with what you have there and let the next person add slicing support. Personally, I find limit/offset more flexible, but this is a great first step and pretty flexible as-is.

[lgfausak]

I think the list is a fantastic addition to an already great piece of code. I am new to python, django and github, I don't know what the correct etiquette is for voting for this, or for using it? I have tried the patch provided by toast38coza and it works great for me. It looks like joestump approves as well, is it already part of the master branch? Also, I'd like to use this addition to the code. What's the correct way to do that, from what I can tell I can:

1. copy the code in to my directory (this is what I did).
2. fork the code and apply toast38coza's changes to my fork of the master branch.
3. fork toast38coza's branch (but it seems to be sort of out of date). Anyway, sorry if I'm going about this the wrong way. I'm looking for the correct way to use the changes introduced by toast38coza. Thanks a lot guys, this is a great piece of work.

-g

[joestump]

@toast38coza Any updates on your end? I might give this a shot this weekend on merging things in and refactoring the Meta thing I mentioned.

[toast38coza]

Hey @joestump. My bad .. just noticed that I somehow missed your reply 11 months ago!

No updates this side. Let me know if you you need anything!

[lgfausak]

Hi Toast, I have been using the list method a bit. I had some questions about the 'qual' and 'order' variables. How does that work? The order should result in something like 'order by employee_name ascending, birthdate descending' and the qual needs to be 'birthdate > 'February 21, 2013' and employee_name = 'Toast''. Looking and the qual and order variables I can't see what to pass them to get this sort of query response. Are they documented somewhere?

[justinabrahms]

This has been merged with a few additions. See commit f1d117cf9045cf461e8165fc901bd55dff2f812e for information.