hotfix – DataObject->setContentLength : Ensure int #607
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.
The type returned from
DataObject.contentLength
varies based on how the objectis populated. This change ensures that when 'setContentLength' is called
the property is set to the expected type (int).
It seems like this could be solved a number of ways, but this seemed like the "silver bullet". At first glance it seems the problematic code is in the two
populate*
methods on the object.populate
seems to be given a string for the$info->bytes
andpopulateFromResponse
is explicitly cast to a string. These could be updated to cast to an integer but I thought I'd let someone more familiar with the library make the call.Just let me know, and I would be happy to amend this pull request.