Fix: Restored Access to Units Involved in Prior Scenarios #6942
Conversation
This file contains hidden or 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
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6942 +/- ##
=========================================
Coverage 12.03% 12.03%
Complexity 6889 6889
=========================================
Files 1103 1103
Lines 142284 142284
Branches 21991 21991
=========================================
+ Hits 17121 17125 +4
+ Misses 123328 123324 -4
Partials 1835 1835 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
The restoration of the ability to see what units were involved in prior scenarios was requested by QA. This PR restores it. However, while I have been unable to run into any exceptions through testing I recall #6796 was actually pretty hard to replicate so I'm going to mark this for 50.07 so we have time to run into any issues during a full development cycle.