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
If we make a change to them, we need to run regression on the modules that rely on them.
First we need to identify which methods in the utilities were changed.
Then we need to identify which modules are affected. We can do this by looking at import statements and then looking for those methods to be called in the module.
We have to beware of utilities that call other utilities as we need to be able to trace all of them back to their modules that use them.
I think anything that is not a module, grammar/antlr, or test should be considered a possible utility.
We have many utilities that our modules rely on.
Example: https://github.com/checkstyle/checkstyle/tree/master/src/main/java/com/puppycrawl/tools/checkstyle/utils
If we make a change to them, we need to run regression on the modules that rely on them.
First we need to identify which methods in the utilities were changed.
Then we need to identify which modules are affected. We can do this by looking at import statements and then looking for those methods to be called in the module.
We have to beware of utilities that call other utilities as we need to be able to trace all of them back to their modules that use them.
I think anything that is not a module, grammar/antlr, or test should be considered a possible utility.
This is blocked by #5 .
The text was updated successfully, but these errors were encountered: