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
Checkstyle does not automatically take the nearest configuration file for different modules. We need to explicitly specify the configuration file for each module in your build tool configuration.
Describe the feature
checkstyle could handle different configuration files for different modules in one repo.
The text was updated successfully, but these errors were encountered:
Hey @alexeagle , after talked with @fzakaria, we have an initial thought about this request.
To apply different Checkstyle configuration files to different modules, we could modify the checkstyle_action to accept a configuration map (key: module name, value: configuration file) instead of a single configuration file. Then, we can parse the source file prefixes to determine the module name and retrieve the corresponding configuration file. We have not tested this approach yet and would appreciate your suggestions.
What is the current behavior?
Checkstyle does not automatically take the nearest configuration file for different modules. We need to explicitly specify the configuration file for each module in your build tool configuration.
Describe the feature
checkstyle could handle different configuration files for different modules in one repo.
The text was updated successfully, but these errors were encountered: