Problem
The user has to always do a bal scan to view the code report. This is okay in the build pipeline, but cumbersome in the development environment.
Proposed Solution
We have the capability to integrate the scan tool with the package build. With that, a user will be able to do a bal build, and the scan tool will be engaged as a pre-build task.
This way, the user doesn't have to manually do a bal scan each time to verify the code quality.
Alternatives
Providing linting capability.
Version
No response