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 SAD detects lazy class, RefGen proposes to inline the class to the class that makes use of it. However, there are some cases where the classes do not implement any method, but extend a parent class with the functionality used in the target class to inline the supposedly "lazy class" (source class). This is a case of false positive that could be fixed directly in SAD from PtiDej, (a.k.a, DECOR). From the refactoring suggestion engine (a.k.a, SACO) it could be validated if source class extends another class do not propose the refactoring.
###Affects
Eclipse Plug-in, Simulation mode (command line), SAD (PtiDej)
###Reproducibility
at-robotsj, forked from sourceforge in my github account.
Check the following commit moar82/at-robots@522a07e the refactored was applied using RefGen, broken the build.
The text was updated successfully, but these errors were encountered:
Description
When SAD detects lazy class, RefGen proposes to inline the class to the class that makes use of it. However, there are some cases where the classes do not implement any method, but extend a parent class with the functionality used in the target class to inline the supposedly "lazy class" (source class). This is a case of false positive that could be fixed directly in SAD from PtiDej, (a.k.a, DECOR). From the refactoring suggestion engine (a.k.a, SACO) it could be validated if source class extends another class do not propose the refactoring.
###Affects
Eclipse Plug-in, Simulation mode (command line), SAD (PtiDej)
###Reproducibility
at-robotsj, forked from sourceforge in my github account.
Check the following commit moar82/at-robots@522a07e the refactored was applied using RefGen, broken the build.
The text was updated successfully, but these errors were encountered: