fix!: remove covered line adjustment in deploy coverage reports #52
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mcarvin8
force-pushed
the
remove-covered-line-adjustment
branch
4 times, most recently
from
e0a3b86 to
84e40c4
Compare
mcarvin8
force-pushed
the
remove-covered-line-adjustment
branch
2 times, most recently
from
0bf5e1e to
16db162
Compare
mcarvin8
force-pushed
the
remove-covered-line-adjustment
branch
3 times, most recently
from
654668b to
e9702f3
Compare
mcarvin8
force-pushed
the
remove-covered-line-adjustment
branch
from
e9702f3 to
61294a9
Compare
|
Closing due to age of PR. Will reopen when issue is corrected by Salesforce Apex team. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#2
Once Salesforce fixes the server response to correctly report coverage in deploy commands, this PR should be rebased and merged.
The Salesforce CLI update via version 2.62.6 was a workaround, total solution needs to be completed by the Apex Team on the server-side.
The Apex Team works based on # of support cases created for issue. Currently I do not have the time to create a support case and track this issue to completion by Salesforce. If other users of this plugin can create support cases, I can provide comments on it to support it.