We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After some refactorings we ended up with an empty file.
It would be great if there was a rule that a completely empty kt file was an error as well as a file with only a package declaration:
package my.package
The text was updated successfully, but these errors were encountered:
Sounds reasonable rule to add 👍
Sorry, something went wrong.
no-empty-file
Fixed by #1963
Successfully merging a pull request may close this issue.
After some refactorings we ended up with an empty file.
It would be great if there was a rule that a completely empty kt file was an error as well as a file with only a package declaration:
The text was updated successfully, but these errors were encountered: