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 ModuleCheck is configured to remove dependencies via a comment instead of just deleting, then build file dependencies blocks are left looking like this:
When first introducing ModuleCheck to a codebase, it can be a good idea to start out with comments instead of deletion. This way, there are breadcrumbs everywhere to help in debugging any build issues.
In a big project, this can be a pain to clean up -- especially for people not comfortable with regex.
It may be a good idea to add a task -- moduleCheckCleanUpComments -- which goes through all the build files and removes all the comments which were created by the plugin.
The text was updated successfully, but these errors were encountered:
If ModuleCheck is configured to remove dependencies via a comment instead of just deleting, then build file
dependencies
blocks are left looking like this:When first introducing ModuleCheck to a codebase, it can be a good idea to start out with comments instead of deletion. This way, there are breadcrumbs everywhere to help in debugging any build issues.
In a big project, this can be a pain to clean up -- especially for people not comfortable with regex.
It may be a good idea to add a task --
moduleCheckCleanUpComments
-- which goes through all the build files and removes all the comments which were created by the plugin.The text was updated successfully, but these errors were encountered: