Styler: learning formatting conventions to repair Checkstyle violations
Open Access
- 6 August 2022
- journal article
- research article
- Published by Springer Nature in Empirical Software Engineering
- Vol. 27 (6) , 1-36
Abstract
Ensuring the consistent usage of formatting conventions is an important aspect of modern software quality assurance. To do so, the source code of a project should be checked against the formatting conventions (or rules) adopted by its development team, and then the detected violations should be repaired if any. While the former task can be automatically done by format checkers implemented in linters, there is no satisfactory solution for the latter. Manually fixing formatting convention violations is a waste of developer time and code formatters do not take into account the conventions adopted and configured by developers for the used linter. In this paper, we present Styler, a tool dedicated to fixing formatting rule violations raised by format checkers using a machine learning approach. For a given project, Styler first generates training data by injecting violations of the project-specific rules in violation-free source code files. Then, it learns fixes by feeding long short-term memory neural networks with the training data encoded into token sequences. Finally, it predicts fixes for real formatting violations with the trained models. Currently, Styler supports a single checker, Checkstyle, which is a highly configurable and popular format checker for Java. In an empirical evaluation, Styler repaired 41% of 26,791 Checkstyle violations mined from 104 GitHub projects. Moreover, we compared Styler with the IntelliJ plugin CheckStyle-IDEA and the machine-learning-based code formatters Naturalize and CodeBuff. We found out that Styler fixes violations of a diverse set of Checkstyle rules (24/25 rules), generates smaller repairs in comparison to the other systems, and predicts repairs in seconds once trained on a project. Through a manual analysis, we identified cases in which Styler does not succeed to generate correct repairs, which can guide further improvements in Styler. Finally, the results suggest that Styler can be useful to help developers repair Checkstyle formatting violations.Keywords
All Related Versions
Funding Information
- Royal Institute of Technology
This publication has 24 references indexed in Scilit:
- How Open Source Projects Use Static Code Analysis Tools in Continuous Integration Pipelines2017
- Oops, My Tests Broke the Build: An Explorative Analysis of Travis CI with GitHub2017
- Analyzing the State of Static Analysis: A Large-Scale Evaluation in Open Source Software2016
- Gamification for enforcing coding conventions2015
- Moving Fast with Software Verification2015
- Defects4J: a database of existing faults to enable controlled testing studies for Java programs2014
- Building Useful Program Analysis Tools Using an Extensible Java Compiler2012
- elytS edoCIEEE Software, 2011
- Using Static Analysis to Find BugsIEEE Software, 2008
- Automatic code stylizing2007