This project is archived and is in readonly mode.
Ensure AR validation errors to be ordered in declared order
Reported by Akira Matsuda | March 20th, 2009 @ 01:56 AM | in 2.3.6
AR#errors sometimes returns error messages in unexpected order.
I wrote a patch to use OrderedHash for AR#errors in order to generate nicely ordered error messages even in good old Ruby 1.8.
Comments and changes to this ticket
-
-
-
Phil Misiowiec March 24th, 2009 @ 04:59 PM
+1 used it in a project - very useful.
Note: you'll need at least http://github.com/rails/rails/co... or else you'll get an undefined on each_key. I grabbed the latest 2.3 stable version of http://github.com/rails/rails/bl... and it works fine.
-
-
Dmitry Polushkin July 29th, 2009 @ 01:33 PM
Any news on this ticket? Please include this patch into 2.3.4. Thanks!
-
Repository September 12th, 2009 @ 03:02 AM
- Milestone changed from “2.x” to “2.3.6”
- State changed from “new” to “committed”
(from [44fbc86ab8975d9e254c7793d54996d2a9ce3f94]) Ensure validation errors to be ordered in declared order
[#2301 state:committed milestone:2.3.5]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net
http://github.com/rails/rails/commit/44fbc86ab8975d9e254c7793d54996... -
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Dmitry Polushkin
Jeremy Kemper
José Valim
Martin Andert
ysakaki
Attachments
Referenced by
-
2301
Ensure AR validation errors to be ordered in declared order
[#2301 state:committed milestone:2.3.5]