Update project_allocation API scale/precision #1370
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
added 7 commits
October 7, 2021 09:02
Attempt to handle FY boundaries in utilization tests
…om/18F/tock into caleywoods/api-proj-allocation-fix
Codecov Report
@@ Coverage Diff @@
## main #1370 +/- ##
=======================================
Coverage 89.91% 89.91%
=======================================
Files 51 51
Lines 2242 2242
=======================================
Hits 2016 2016
Misses 226 226
Continue to review full report at Codecov.
|
caleywoods
changed the title
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.
Description
Addresses #1369. Update the scale/precision of the
project_allocationfield in the API return for Timecards. TheTimecardSerializerjust needed updated to reflect the scale and precision change that was made to support 12.5% (0.125) project allocation.