[ktlint] reported by reviewdog 🐶 Enum entry should start on a separate line Raw Output: src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:40:16: error: Enum entry should start on a separate line (standard:enum-wrapping)

[ktlint] reported by reviewdog 🐶 Enum entry should start on a separate line Raw Output: src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:40:21: error: Enum entry should start on a separate line (standard:enum-wrapping)

[ktlint] reported by reviewdog 🐶 Enum entry should start on a separate line Raw Output: src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:40:28: error: Enum entry should start on a separate line (standard:enum-wrapping)

[ktlint] reported by reviewdog 🐶 Enum entry should start on a separate line Raw Output: src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:40:40: error: Enum entry should start on a separate line (standard:enum-wrapping)

[ktlint] reported by reviewdog 🐶 Enum entry should start on a separate line Raw Output: src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:40:48: error: Enum entry should start on a separate line (standard:enum-wrapping)

[ktlint] reported by reviewdog 🐶 Enum entry should start on a separate line Raw Output: src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:40:55: error: Enum entry should start on a separate line (standard:enum-wrapping)

[ktlint] reported by reviewdog 🐶 Enum entry should start on a separate line Raw Output: src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:40:60: error: Enum entry should start on a separate line (standard:enum-wrapping)

[ktlint] reported by reviewdog 🐶 Enum entry should start on a separate line Raw Output: src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:40:65: error: Enum entry should start on a separate line (standard:enum-wrapping)

[ktlint] reported by reviewdog 🐶 Enum entry should start on a separate line Raw Output: src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:40:78: error: Enum entry should start on a separate line (standard:enum-wrapping)

reviewdog: Too many results (annotations) in diff. You may miss some annotations due to GitHub limitation for annotation created by logging command. Please check GitHub Actions log console to see all results. Limitation: - 10 warning annotations and 10 error annotations per step - 50 annotations per job (sum of annotations from all the steps) - 50 annotations per run (separate from the job annotations, these annotations aren't created by users) Source: https://github.com/orgs/community/discussions/26680#discussioncomment-3252835