This project is archived and is in readonly mode.
Metal names conflict with models
Reported by Damien MATHIEU | August 26th, 2009 @ 02:45 PM
Hello,
By default, the metals are named only with their name.
Because of that, there's a possible conflict if we have a metal
using the same name than a model.
If we have a metal "Example" and a model with the same name, we
won't be able to call the model Example inside our metal because of
this conflict name.
My suggestion would be to append "_metal" to the filename and "Metal" to the classname.
Comments and changes to this ticket
-
-
Francesc Esplugas September 14th, 2009 @ 10:25 PM
Still not had this kind of problems but think it's a problem some people might find in the future.
+1
-
Damien MATHIEU September 17th, 2009 @ 01:12 PM
- Tag changed from “metal” to “2.3, metal, patch”
-
Damien MATHIEU September 21st, 2009 @ 02:57 PM
Bump again. To bad to see that nobody (except Francesc. Thanks) is interested.
-
CancelProfileIsBroken September 25th, 2009 @ 12:42 PM
- Tag changed from “2.3, metal, patch” to “2.3, bugmash, metal, patch”
-
Elad Meidar September 26th, 2009 @ 02:08 AM
+1 verified. not sure that this is the right solution thu, maybe there's a way to scope the metal models under
Metal::? -
Yehuda Katz (wycats) September 26th, 2009 @ 02:16 AM
- Tag changed from “2.3, bugmash, metal, patch” to “2.3, metal, patch”
-
Yehuda Katz (wycats) September 26th, 2009 @ 02:17 AM
- State changed from “new” to “invalid”
This would be a potentially confusing change in 2.3 and is moot in 3.0.
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>
Damien MATHIEU
José Valim
Yehuda Katz (wycats)