The code example used to demonstrate disallowed code was correctly formatted (i.e., there were blank lines before declarations). This change corrects the example to properly reflect code that violates the rule.
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
[x] KtLint format has been applied on source code itself and violations are fixed
[x] PR title is short and clear (it is used as description in the release changelog)
[x] Snapshot documentation in case documentation is to be released together with a code change
[x] Release documentation 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
k-taro56
commented
1 month ago
Description
The code example used to demonstrate disallowed code was correctly formatted (i.e., there were blank lines before declarations). This change corrects the example to properly reflect code that violates the rule.
Checklist
Before submitting the PR, please check following (checks which are not relevant may be ignored):
Closes #<xxx>orFixes #<xxx>(replace<xxx>with issue number)Documentation is updated. See difference between snapshot and release documentation