Fix AggregateCostModel's parsing of configured SharedOverhead #920
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
AjayTripathy
approved these changes
Sep 7, 2021
|
Thanks, let's get this merged for the upcoming release! |
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.
What does this PR change?
GetSharedOverheadCostPerMonthas a clear and safe way to access the configured shared overhead field.How does this PR impact users? (This is the kind of thing that goes in release notes!)
0.0instead of creating errors.How was this PR tested?
Before
After
Also confirmed that setting non-zero shared costs still works, then reset to $0.00 and confirmed that that still worked, too.
