Timeline for Fixing a spelling mistake in a method name
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2014 at 11:40 | history | edited | Rémi | CC BY-SA 3.0 | added a comment suggestion |
| Jun 13, 2014 at 11:36 | comment | added | Rémi | @IvoLimmen That's a really good suggestion. This way people get even more their head around using the new method and this would remove a warning from the obsolete call to the old method from within the new one. I will add this to my answer. | |
| Jun 13, 2014 at 9:07 | comment | added | Ivo Limmen | I agree with your method; I would do the same. It's the most sane, clear and secure method of refactoring. What also might be a nice way is to move the code from the old method into the new method and make the old one use the new method. When the codebase is a few iterations down the timeline you only need to remove the old deprecated method. | |
| Jun 12, 2014 at 14:05 | history | answered | Rémi | CC BY-SA 3.0 |