You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to an issue that you encountered with Salesforce Code Analyzer?
I would like to have the ability to specify multiple file formats in one command, rather than having to run the command multiple times.
Describe the solution that you want:
Currently, I would have to run a command like this: sf scanner:run --format 'json' --engine 'eslint' --outfile 'build/reports/codeanalyzer.json' --target ./test/resources/force-app/ sf scanner:run --format 'html' --engine 'eslint' --outfile 'build/reports/codeanalyzer.html' --target ./test/resources/force-app/
I don't want to run the engine multiple times for file formats. Ideally, I could do something like the following:
Is your feature request related to an issue that you encountered with Salesforce Code Analyzer?
I would like to have the ability to specify multiple file formats in one command, rather than having to run the command multiple times.
Describe the solution that you want:
Currently, I would have to run a command like this:
sf scanner:run --format 'json' --engine 'eslint' --outfile 'build/reports/codeanalyzer.json' --target ./test/resources/force-app/
sf scanner:run --format 'html' --engine 'eslint' --outfile 'build/reports/codeanalyzer.html' --target ./test/resources/force-app/
I don't want to run the engine multiple times for file formats. Ideally, I could do something like the following:
sf scanner:run --format 'json, html' --engine 'eslint' --outfile 'build/reports/codeanalyzer.json, 'build/reports/codeanalyzer.html' --target ./test/resources/force-app/
Describe alternatives that you've considered:
For now, I would have to either run the command multiple times or do the additional formatting myself.
Additional Context:
N/A
Workaround:
As far as I'm aware, I would have to implement the multi-format manually.
Urgency:
Highly Beneficial
The text was updated successfully, but these errors were encountered: