Closed alexanderbazhenoff closed 7 months ago
It seems console.warning
, which was deprecated, has finally been removed :)
PR on the way :)
@alexanderbazhenoff please can you check it's now ok with v14.2.2 https://github.com/nvuillam/npm-groovy-lint/releases/tag/v14.2.2 ? :)
please can you check it's now ok with v14.2.2
I'll try to do next week, need to finish my code refactoring first on super-linter, than replace it in CI. Thank you.
@nvuillam Hi, sorry for long waiting reply. I din't swtich to MegaLinter yet, but Super-Linter was updated and now includes npm-groovy-lint version 14.2.2 and CodeNarc version 3.3.0. The code pattern mentioned by me sucesfully pass, looks like you can close a bug. Thanks once again for quick reaction.
@alexanderbazhenoff thanks for your feedback :)
Hi, I have a working Jenkins scripted style pipeline with node selection before
node(){}
and the whole pipeline:pipeline.groovy:
but npm-groovy-lint fails:
My settings are:
It's funny how I tried to changed node selection part thinking the bug is here, but I have removed forgotten line
/* groovylint-enable UnnecessaryGetter */
and it's pass...Can you please make an ignore of enabling non-disabled rule in the future (instead of fail)? :) Or better add some warning that the rule is not disabled to enable them.