Implementing Parcelable in ParseGeoPoint

[natario1]

As per title. It’s the easiest step in bringing Parcelable into the SDK.

[facebook-github-bot]

@natario1 updated the pull request - view changes

[rogerhu]

Can I ask though what's the overall plan? #122

[natario1]

@rogerhu from #122 I think it’s common wish to eventually implement Parcelable to ParseObject, no?
But since ParseObject hosts other objects, we must first make these Parcelable (e.g. ParseGeoPoint, ParseFile).

I have it working for ParseFile as well and can PR.

I’ll open up an issue with some thoughts now.

[rogerhu]

See also #557

[rogerhu]

rebase

[codecov]

Codecov Report

Merging #619 into master will increase coverage by 0.05%.
The diff coverage is 77.77%.

@@             Coverage Diff              @@
##             master     #619      +/-   ##
============================================
+ Coverage     52.52%   52.58%   +0.05%     
- Complexity     1659     1664       +5     
============================================
  Files           131      131              
  Lines         10121    10138      +17     
  Branches       1407     1407              
============================================
+ Hits           5316     5331      +15     
- Misses         4365     4368       +3     
+ Partials        440      439       -1

Impacted Files	Coverage Δ	Complexity Δ
Parse/src/main/java/com/parse/ParseFile.java	77.77% <ø> (ø)	43 <0> (ø)	⬇️
...se/src/main/java/com/parse/ParseParcelEncoder.java	87.69% <100%> (+3.31%)	20 <0> (+1)	⬆️
...se/src/main/java/com/parse/ParseParcelDecoder.java	87.87% <100%> (+0.37%)	31 <0> (+2)	⬆️
Parse/src/main/java/com/parse/ParseGeoPoint.java	63.23% <73.33%> (+2.85%)	11 <2> (+2)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 46a0233...9ac8589. Read the comment docs.

[natario1]

@rogerhu this is ready as well. I think we can close #122