I completely agree with your points. I constantly encounter the same problems when I use other frameworks so I want everything to be fully flexible.
At the moment the REST routes are generated for resources and available through the api/resources endpoint. (For example, /api/resources/users/) you can however add whatever other routes you like to /api/ using your own controllers.
I'm thinking about adding a simple query language to the REST route syntax to take care of some common requests. That may work something like this: /api/resources/users/$near/lat,lon
It's still early stages though so I'll probably go through a lot of ideas before I'm happy with it!
It'll be called Nails (or Nails Framework, Nails CMS, whatever sounds closest to the finished idea) - I have the domain nails.io which I'll be using for this project.
Cheers. I've used RailwayJS in the past but I switched to LocomotiveJS[1] which I find much nicer to work with and it's incredibly flexible too.
I'm using locomotive in this project on top of express to help with controllers and routing, though I'm thinking about using flatiron[2] which is a pretty solid looking set of modules for routing, middleware, etc.
I completely agree with your points. I constantly encounter the same problems when I use other frameworks so I want everything to be fully flexible.
At the moment the REST routes are generated for resources and available through the api/resources endpoint. (For example, /api/resources/users/) you can however add whatever other routes you like to /api/ using your own controllers.
I'm thinking about adding a simple query language to the REST route syntax to take care of some common requests. That may work something like this: /api/resources/users/$near/lat,lon
It's still early stages though so I'll probably go through a lot of ideas before I'm happy with it!
It'll be called Nails (or Nails Framework, Nails CMS, whatever sounds closest to the finished idea) - I have the domain nails.io which I'll be using for this project.
Cheers!