Format JavaScript files with Prettier #123
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These files were difficult to read and edit due to inconsistent indentation within the same file (spaces and tabs within the same file) as well as odd-numbered indentation (3 spaces), which isn't supported by Prettier (the code formatting tool for JavaScript used in the Jenkins project). This PR uses Prettier to format these source files using the same configuration used for Jenkins core. This makes it easier to read and edit the files, especially for developers who are used to the coding style used in Jenkins core. No other changes were made to the files other than running Prettier.