Make a Breaking Change

[connorhu]

Breaking Change is a thorn in the flesh. There will come a time when we will be forced to make a change that changes the class name/method sinature. What if we could go ahead and develop a process on how to communicate such a change in advance and provide a migration tool to help with the transition? To do this, it might be best to identify possible scenarios that could change:

• class name changes
• namespace changes
• add public|protected return type (without change)
• add public|protected method argument type (without change)

For now, I think a know-how collection with practical and working patterns is enough. When the time comes, we will have something to work with.