|
|
|
|
|
by zacharyvoase
5842 days ago
|
|
It’s quite a nice solution actually, but I’m afraid it’s far too coupled with the Django models for many of my use cases. A lot of the time you’ll create a Resource without any model to back it—for example, most Rails projects use a UserSession resource for logging in/out, with logging in => new/create, and logging out => edit/destroy. |
|