Feature: Reforge helper #31
Annotations
10 errors and 1 warning
Check Style:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt#L77
[ktlint] reported by reviewdog 🐶
Argument should be on a separate line (unless all arguments can fit a single line)
Raw Output:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:77:37: error: Argument should be on a separate line (unless all arguments can fit a single line) (standard:argument-list-wrapping)
|
Check Style:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt#L77
[ktlint] reported by reviewdog 🐶
Argument should be on a separate line (unless all arguments can fit a single line)
Raw Output:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:77:60: error: Argument should be on a separate line (unless all arguments can fit a single line) (standard:argument-list-wrapping)
|
Check Style:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt#L77
[ktlint] reported by reviewdog 🐶
Argument should be on a separate line (unless all arguments can fit a single line)
Raw Output:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:77:84: error: Argument should be on a separate line (unless all arguments can fit a single line) (standard:argument-list-wrapping)
|
Check Style:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt#L82
[ktlint] reported by reviewdog 🐶
Argument should be on a separate line (unless all arguments can fit a single line)
Raw Output:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:82:38: error: Argument should be on a separate line (unless all arguments can fit a single line) (standard:argument-list-wrapping)
|
Check Style:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt#L82
[ktlint] reported by reviewdog 🐶
Argument should be on a separate line (unless all arguments can fit a single line)
Raw Output:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:82:63: error: Argument should be on a separate line (unless all arguments can fit a single line) (standard:argument-list-wrapping)
|
Check Style:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt#L82
[ktlint] reported by reviewdog 🐶
Argument should be on a separate line (unless all arguments can fit a single line)
Raw Output:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:82:86: error: Argument should be on a separate line (unless all arguments can fit a single line) (standard:argument-list-wrapping)
|
Check Style:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt#L91
[ktlint] reported by reviewdog 🐶
Line is exceeding max line length. Break line after '||' in binary expression
Raw Output:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:91:113: error: Line is exceeding max line length. Break line after '||' in binary expression (standard:binary-expression-wrapping)
|
Check Style:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt#L91
[ktlint] reported by reviewdog 🐶
Exceeded max line length (120)
Raw Output:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:91:121: error: Exceeded max line length (120) (standard:max-line-length)
|
Check Style:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt#L91
[ktlint] reported by reviewdog 🐶
Line is exceeding max line length. Break line after '==' in binary expression
Raw Output:
src/main/java/at/hannibal2/skyhanni/api/ReforgeAPI.kt:91:129: error: Line is exceeding max line length. Break line after '==' in binary expression (standard:binary-expression-wrapping)
|
Check Style
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
|
Check Style
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|