Halcyon Halcyon → Release 0.5.1

Currently, the easiest way to respond with anything other than a 200 OK response or a 404 Not Found response is to throw an exception. This is trivial, but it of course causes problems with flow control and isn't exactly the best API.

A better option would to provide some sort of lookup method similar to ok but including a symbolic version of the HTTP errors as well. (This will require some additional information included with the exceptions.rb file, but that is a trivial change.)

Here is an example:

class Foos < Application
  def create
    @foo = Foo.new
    # pre-save logic here
    if @foo.save
      status :created
    else
      error :unprocessable_entity
    end
  end
end

Of course, other method names may be better, but these were the first two I came up with. Technically, error and status could be aliases.