Should rapid have a tag for error pages?
Reported by Iain | November 10th, 2009 @ 04:46 AM
Currently there are tags in rapid for and (which are great), but should there be a tag for error pages as well? For example, http status code 500? It seems inconsistent (and un-hobo-ish) to write a page in /public/ for errors - is it worth creating a default tag for error handling instead?
Comments and changes to this ticket
-
Matt Jones November 15th, 2009 @ 09:20 PM
The problem with this is that 500 errors can come from things that much earlier in the stack. For example, syntax errors in application.dryml will give a 500 for every request. At that point, it's probably a bad idea to try to parse DRYML.
-
Tom Locke November 17th, 2009 @ 03:56 PM
- State changed from “new” to “wontfix”
I agree with Matt's take on this. I think it'll cause more trouble that it's worth.
Marking as wontfix for now.
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 Jones
Tom Locke