Rename policy parameters to more consistent #1051
Merged
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
Current coverage is 98.73% (diff: 100%)@@ master #1051 diff @@
==========================================
Files 38 38
Lines 2695 2695
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
Hits 2661 2661
Misses 34 34
Partials 0 0
|
Closed
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.
This pull request changes the names of several policy parameters in order to make them more consistent and to make them conform to the project's policy parameter naming conventions. This pull request combines the content of five closed pull requests: #1040, #1045, #1046, #1047 and #1049.
This pull request does not change any tax-calculation logic, and therefore, does not change any tax results.
@MattHJensen @talumbau @jdebacker @Amy-Xu @GoFroggyRun @andersonfrailey @codykallen