Matt Carvin

@codefriar - I'm not affiliated with Salesforce, but this is consistent with what I've seen developing a plugin to convert the code coverage output for SonarQube and what I've listed...

Is there any solution for this yet @AllanOricil ? This would affect this plugin I just made which deals with converting the code coverage JSON into a XML that SonarQube...

Should we keep this issue open @shetzel or just close it since this seems out of the CLI team's responsibility? Seems like once the API team updates the API response...

@jfaderanga - Per @shetzel , this issue needs to be fixed by the team that manages the API first. I agree with you that this is a blocker for anyone...

> it is a blocker for pipeline with Quality Gates. I've been struggling with this issue for few months now. One thing I noticed is the code should be modularized...

@jfaderanga - My [plugin](https://github.com/mcarvin8/apex-code-coverage-transformer/blob/main/README.md) essentially just converts the JSON output from the deploy command into a XML file containing the uncovered lines/covered lines. The `latest` build of my plugin just...

Currently it just supports one directory via the `--dx-directory` flag. That flag defaults to `force-app/main/default` if you don't provide the flag a different path. I can look into supporting multiple...

@jfaderanga - I just released a new version of the plugin which supports multiple package directories as listed in your project's `sfdx-project.json` file. If you run this plugin in the...

@jfaderanga - Awesome! I just released a new `beta` pre-release build which will add `covered` lines to the final XML file. Big catch like I've stated previously is that the...

@jfaderanga - Thank you for testing this out and letting me know! I have released the `1.6.0` tag which adds support for `covered` lines by re-numbering out-of-range lines. Once this...