Deprecation notices not always include the caller
Reported by Simon Rozet | July 17th, 2009 @ 02:34 PM | in 0.10.0
For example, the #update_attributes -> #update deprecation notice. I'll try to write a patch for this.
Comments and changes to this ticket
-
Dan Kubb (dkubb) July 22nd, 2009 @ 03:51 PM
- Assigned user set to “Dan Kubb (dkubb)”
- State changed from “new” to “confirmed”
-
Dan Kubb (dkubb) July 22nd, 2009 @ 03:55 PM
- State changed from “confirmed” to “accepted”
-
Dan Kubb (dkubb) August 18th, 2009 @ 10:17 PM
- State changed from “accepted” to “resolved”
(from [88612ef4d69acfee14d06845ca2bbe4311f35155]) Add caller information to all deprecation warnings
[#979 state:resolved] http://github.com/datamapper/dm-core/commit/88612ef4d69acfee14d0684...
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 »
People watching this ticket
Dan Kubb (dkubb)
Simon Rozet
Referenced by
-
979
Deprecation notices not always include the caller
[#979 state:resolved]
http://github.com/datamapper/dm-co...