Currently, Nebula Logger runs some slightly custom PMD rules within the pipeline. This is currently done using v4 of sfdx scanner/sf code analyzer. I'd like to....
- Upgrade the repo to use to the new v5 release of code analyzer
- For Apex...
- For JavaScript...
- Delete
config/linters/.eslintrc.json & migrate to the code-anaylzer.yml file used in v5
- Migrate
npm scripts in package.json (scan:lwc) to use sf code-analyzer run --rule-selector eslint for JS linting, instead of calling eslint directly
- There will probably also be some
devDependencies in package.json for eslint that can be deleted
Currently, Nebula Logger runs some slightly custom PMD rules within the pipeline. This is currently done using
v4of sfdx scanner/sf code analyzer. I'd like to....config/linters/pmd-ruleset.xml& migrate to thecode-anaylzer.ymlfile used in v5AppExchangerules, and revisit other existing & new rules to see if any others should be addedconfig/linters/.eslintrc.json& migrate to thecode-anaylzer.ymlfile used in v5npmscripts inpackage.json(scan:lwc) to usesf code-analyzer run --rule-selector eslintfor JS linting, instead of callingeslintdirectlydevDependenciesinpackage.jsonforeslintthat can be deleted