You guys are right. It would be too much work that would only work (accurately) if the three models had strictly one relationship. We could find ways to ensure a greater accuracy but it wouldn’t be worth it. And like John said, it has the potential to be greatly misused and open a can of security worms. I’ll just stick to what I’m doing now. Thanks
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Nested Resource Route Helpers | 9 | 123 | June 5, 2012 | |
LH Ticket #1089: Feedback Please | 0 | 151 | August 8, 2009 | |
Ticket 7893: Adding the ability to remove collection and member route generation for Resources | 0 | 136 | March 23, 2007 | |
Multiple Nested RESTful Resources | 0 | 82 | January 25, 2007 | |
Nested Resource Route Helpers | 0 | 127 | June 5, 2012 |