[philstu]

It truly blows my mind that any further explanation would be required.

If you want a data store that exposes your database over HTTP then use on of the billion data stores that is designed to do that. None of those are meant to be a public API, and doing this is so incredibly wreckless and short sighted I could write at least a chapter in a book about it.

Actually, I did write a chapter in a book about it.

https://leanpub.com/build-apis-you-wont-hate

A RESTful API is about so many more things than just shoving a generic CRUD interface on top of your data schema.

[glibgil]

API developer and authur who handcrafts via middleware (PHP) hates framework that automatically generates APIs from database features? Quelle f'ing surprise.

[philstu]

A developer who has been invited into the USA twice because of his skills at building complex APIs for complex companies suggests that automated solutions are a cancer on the API building industry?

Quelle f'ing surprise.

[michaelchisari]

> A RESTful API is about so many more things than just shoving a generic CRUD interface on top of your data schema.

Am I mistaken in thinking that this project offers much more control than shoving a generic CRUD interface on top of a data schema?

Obviously, something like this would provide a great way to bootstrap a REST api for the basics you need. Sure, it may run into limits when more specificity is necessary, but that's the trap that all autogen frameworks run into.

[joevandyk]

You can use this for CRUD api's, and then move to something else when you need to. Clients won't care.