Fix repeatables buying more than intended when cumulativeCost
is false
#18
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: profectus/Profectus#18
Loading…
Reference in a new issue
No description provided.
Delete branch "ducdat0507/patch-1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The logic for
calculateMaxAffordable
didn't account for how much of a repeatable you already bought so it ended up overshooting by a lotI'm sorry I haven't looked at your PR for fixing calculateMaxAffordable in so long. I don't remember why I didn't merge it earlier, but I think I'd just wanted to see why the current tests didn't fail. I've run them with and without your changes and actually I think the existing behavior is correct. I was wondering if you could give me a test case where you were getting the wrong result using the current implementation
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.