This is a follow up to #396, that corrects the full flow to work correctly.
Description
A deprecation message exists for passing in a Number object, but still relies on it's setter methods for the body that is passed in the API Request. This PR fixes that.
How Has This Been Tested?
Tests fixed to reflect correct behaviour
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
This is a follow up to #396, that corrects the full flow to work correctly.
Description
A deprecation message exists for passing in a Number object, but still relies on it's setter methods for the body that is passed in the API Request. This PR fixes that.
How Has This Been Tested?
Tests fixed to reflect correct behaviour
Types of changes
Checklist: