0.9: Per-controller blueprint config

[mikermcneil]

ability to selectively disable/enable blueprints on certain controllers.

NtHs: [ apiPrefix, expectIntegerId ]

[mikermcneil]

pushing to point release

[stevesims]

+1

I'm just getting started with sails and I really like the CRUD blueprint stuff, but I know that I won't want that functionality for many of my controllers. I realise that I can work around this by overriding all the CRUD actions, but doing that feels cumbersome, and I know I'll probably forget. It would be really nice if I could just add a line to say "blueprint: false" to a controller definition to disable them.

Conversely having the ability to globally disable blueprints, but then selectively enable them on individual controllers would be cool too.

[mikermcneil]

Conversely having the ability to globally disable blueprints, but then selectively enable them on individual controllers would be cool too.

This is covered by the _config property in blueprints in the latest stable release on npm- best docs on it for now are here, when you generate a new controller: https://github.com/balderdashy/sails/blob/master/bin/boilerplates/config/controllers.js#L7

More/better documentation coming soon in general-- I'll make sure we cover this!

[stevesims]

Thanks Mike - that's exactly what I'd been hoping to find.