fix(serialize): add true as an accepted value for bool #131
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.
When I was working on
getUsersFollowingMe, I noticed thatshouldMapToBooleanswas not properly mappingtrueorfalsewhen the API responds with those values. This bug remained undetected since almost all responses from RA's API return either a "1" or "0" for a Boolean field. SinceAPI_GetUsersIFollow.phpandAPI_GetUsersFollowingMe.phpreturn eithertrueorfalsefor their Boolean fields, the serializer function will always map the value asfalsedue to the missing check fortrue. This PR fixes this issue by adding a check for the stringified version oftrue.