You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you rename an instance variable that has getter and setter methods, the refactor silently removes those methods and creates new ones with the new instance variable name.
This happens only if there are no current uses of the old methods in the current project. However, the old methods might still be used in other packages that aren't currently loaded.
This means the refactor could cause problems, making it more like a transformation than a simple rename because it can break code.
The text was updated successfully, but these errors were encountered:
When you rename an instance variable that has getter and setter methods, the refactor silently removes those methods and creates new ones with the new instance variable name.
This happens only if there are no current uses of the old methods in the current project. However, the old methods might still be used in other packages that aren't currently loaded.
This means the refactor could cause problems, making it more like a transformation than a simple rename because it can break code.
The text was updated successfully, but these errors were encountered: