4 ms·
That's simple - change the method so all those invocations are invalid now. If you're using a compiled language, the compiler will tell you all the lines that
by anonymous 14y ago
That's simple - change the method so all those invocations are invalid now.
If you're using a compiled language, the compiler will tell you all the lines that need changing.
If you're using a dynamic language, you should have test coverage for all those methods and your tests will blow up with "no such method".
Or maybe, you could special-case the 'hasAttribute(name)' method so it logs a debug warning and checks the enum attribute.
Really, there are enough ways to deal with that and you're far from the first person to have had that problem.
- guard-of-terra 14y ago"you could special-case the 'hasAttribute(name)' method" Please don't do this never.
- jtheory 14y agoI believe "temporarily" was implied.
- guard-of-terra 14y agoAnd when are you going to take out that? If you leave, who will take care of this hack?
- jtheory 14y agoThis isn't my argument -- I've never taken this approach -- but if the need came up, it would never go into source control; it'd only be there long enough to run test suites locally and find the broken code that needed fixing.