| <!-- Thanks for opening a new PR! |
| |
| Before you click submit, please consult the Checklist below. Note, that you still can add new commits to your branch before submitting the PR. |
| --> |
| |
| ## Description |
| |
| <!--Describe what was done and why (mandatory). The description should help the reviewer to understand what the PR is about and which decisions have been made. |
| |
| If the PR solves an issue then provide a link to that issue using format `Closes #<xxx>` or `Fixes #<xxx>` (replace`<xxx>` with issue number) |
| --> |
| |
| ## Checklist |
| |
| Before submitting the PR, please check following (checks which are not relevant may be ignored): |
| - [ ] Commit message are well written. In addition to a short title, the commit message also explain why a change is made. |
| - [ ] At least one commit message contains a reference `Closes #<xxx>` or `Fixes #<xxx>` (replace`<xxx>` with issue number) |
| - [ ] Tests are added |
| - [ ] KtLint format has been applied on source code itself and violations are fixed |
| - [ ] PR title is short and clear (it is used as description in the release changelog) |
| - [ ] PR description added (background information) |
| |
| [Documentation](https://pinterest.github.io/ktlint/) is updated. See [difference between snapshot and release documentation](https://github.com/pinterest/ktlint/tree/master/documentation) |
| - [ ] [Snapshot documentation](https://github.com/pinterest/ktlint/tree/master/documentation/snapshot) in case documentation is to be released together with a code change |
| - [ ] [Release documentation](https://github.com/pinterest/ktlint/tree/master/documentation/release-latest) in case documentation is related to a released version of ktlint and has to be published as soon as the change is merged to master |
