-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
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
Formatting breaks code, converting else if
into elseif
in some cases
#127
Comments
That's nasty ^^ |
I fixed the issue and released it in a beta version of next major release, please can you confirm it's ok with your whole file ? :)
|
Addendum: i had an beta release issue, so the beta to use is [email protected] , not [email protected] |
Looks like it's fixed 👍 Thanks! |
Great :) |
- Upgrade to CodeNarc 2.0.0 - Upgrade jars - Adapt Indentation rule to new behaviour - Use codenarc --ruleset argument instead of temp ruleset file - Replace super-linter by [Mega-Linter](https://nvuillam.github.io/mega-linter/) - Fixes - [(#127)](#127) Formatting breaks code, converting `else if` into `elseif` in some cases - Apply formatting rules also for --fix mode - Fix Markdown dead links - CI - Migrate from CircleCI to GitHub Actions: now tests are on Linux, Windows & MacOs - Activate spelling linter of Mega-Linter (+ `.cspell.json` file) - Add test cases for format and fix using CLI
After running
npm-groovy-lint --format
on a project, I noticed it resulted in several compilation issues.I tried to whittle the problematic code down to a minimal-ish example:
I found that if I add a space, like
else if (b) {
it stops exhibiting this behavior, but I'm not sure if that's the whole story.The text was updated successfully, but these errors were encountered: