Dru Jensen

@faustinoaq Any chance you will have some time to work on this? We have the new exceptions page but if there is an error in compilation, the existing process is...

Any update on this issue?

@bararchy I was hoping you already had an example. ;-) I haven't done any reinforcement learning yet but always love a challenge. I will see if I can find one...

@crimson-knight Anyway to test this locally first? I'm getting a lot of emails asking for reviews.

The existing `amber generate api Post title:string body:text` will create a different pipeline: ``` pipeline :api do plug Amber::Pipe::Error.new plug Amber::Pipe::Logger.new plug Amber::Pipe::Session.new plug Amber::Pipe::CORS.new end ``` You can add...

@robacarp Ok, I am going to close this out. Thanks for providing the discussion about Redis. That will have impact on Amber for sure. We should open an issue to...

What about adding an `.import!` that throws an exception if there is an error and `.import` will return a boolean if there are any errors. You could check each model...

looks great! for the second one, you should skip invalid records since they should be able to easily find the ones that have an error by filtering the array of...

@notalex yes. @faustinoaq fixed this in his last [PR](https://github.com/amberframework/granite-orm/pull/118). 🥇 We removed the class var. I will release Granite soon or you can try the master branch.

Yeah, I agree. We should treat `params` as a serializer, similar to `json`, `yaml`, or `xml`. In Amber, we could initialize the object using `Class.from_params` method. Question: should serializers call...