I've added a couple more features based on Rails resources: singular resources, where there isn't an id, and member and collection for adding extra non-standard routes.
If I had the choice, I would have used resource/resources instead of singular_resource/resource, but I didn't want to break backward compatibility unilaterally.
I've added a couple more features based on Rails resources: singular resources, where there isn't an id, and member and collection for adding extra non-standard routes.
If I had the choice, I would have used resource/resources instead of singular_resource/resource, but I didn't want to break backward compatibility unilaterally.