Allow nested increment on undefined fields

[dplewis]

Calling increment on a field that doesn't exists (serverData stored in object state) gets ignored.

const obj = new TestObject();
obj.increment('a.b.c.d'); // ignored
await obj.save();

I believe this was ignored because the server doesn't support it and throws the following error

Unhandled promise rejection: TypeError: Cannot read property 'split' of undefined

[codecov]

Codecov Report

Merging #1303 (d83e8e8) into master (1abb841) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master     #1303   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           60        60           
  Lines         5837      5832    -5     
  Branches      1312      1310    -2     
=========================================
- Hits          5837      5832    -5     

Impacted Files	Coverage Δ
src/ParseObject.js	100.00% <ø> (ø)

---

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 1abb841...392d822. Read the comment docs.

[mtrezza]

What is the change? Is a new field with this PR incremented when saving?

[dplewis]

The change is that we are allowing this request to go to the server. The server doesn't support this request yet.

I'll try to do a PR on the server side. I would like this merged to test it on the server side.

[mtrezza]

Do we have enough integration test in this repo to ensure letting this go to the server has no detrimental effects?

[dplewis]

Technically the other SDK's don't prevent you from doing this. This also mean that a user can use the REST API and get the same results. Dot notation didn't exist in this SDK until I added it. #729

Since there is that unhandled promise rejection. We can't really test much.

[mtrezza]

LGTM!