Raising Exceptions with Non-Standard Body Messages
Reported by Matt Todd | June 17th, 2008 @ 07:06 PM | in Release 0.5.1
Currently, to raise an (HTTP Error) exception with non-standard error messages requires to supply the status code (as the first argument). This shouldn't be a required attribute.
For example:
raise NotFound.new(404, "Not found here, at all... sorry.")
instead of:
raise NotFound.new("Not found here, at all... sorry.")
Comments and changes to this ticket
-
Matt Todd June 19th, 2008 @ 05:56 PM
- State changed from “new” to “resolved”
(from [78a19edb784ab81e994b9f1c26e5662b21f8600f]) Made exceptions that inerit from Halcyon::Exceptions::Base not require the status code as the first parameter (and removes it completely, in fact). The only argument when raising these exceptions is the body text. [#49 state:resolved]
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Matt Todd