This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
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.
For #26844: Update ktlint to 0.47.0. #26846
For #26844: Update ktlint to 0.47.0. #26846
Changes from all commits
925ebe8
b16e455
95b47a4
46a2875
d82cfa7
cbbd338
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an aside thought, but do we know why the ktlint in CI didn't complain and block the initial merge when the file name rule failed for this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the changelog it seems the rule has been added in 0.46.0. (It was later modified in 0.47.0 to allow different naming for files with just a single top-level declaration of type function - especially in the case of extension functions).
I do remember similar warnings about file names, but that could have been from lint or IDE (?)