feat: Add invalid struct error

[dblythy]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

Invalid structs are really hard to isolate the cause of the problem, especially with larger classes

Related issue: #237

Approach

Checks if error code is 4865 and returns error .invalidStruct if so

TODOs before merging

• Add tests
• Add entry to changelog

[parse-github-assistant]

Thanks for opening this pull request!

• 🎉 We are excited about your hands-on contribution!

[codecov]

Codecov Report

Merging #238 (f9b27f8) into main (7aeef06) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #238      +/-   ##
==========================================
- Coverage   76.72%   76.70%   -0.02%     
==========================================
  Files          99       99              
  Lines       10374    10382       +8     
==========================================
+ Hits         7959     7964       +5     
- Misses       2415     2418       +3     

Impacted Files	Coverage Δ
Sources/ParseSwift/API/URLSession+extensions.swift	73.12% <100.00%> (+0.86%)	⬆️
Sources/ParseSwift/Types/ParseError.swift	100.00% <100.00%> (ø)
Sources/ParseSwift/Coding/ParseEncoder.swift	73.25% <0.00%> (-0.36%)	⬇️

---

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 7aeef06...f9b27f8. Read the comment docs.

[cbaker6]

It also looks like you broke some Linux tests as well. Those will need to be fixed before the PR can be approved.

[dblythy]

The test that is failing on Linux is the one that I added (the different response for the .invalidStruct error). Does linux handle swift json decoding differently?

[cbaker6]

The test that is failing on Linux is the one that I added (the different response for the .invalidStruct error). Does linux handle swift json decoding differently?

Yes, there are some differences with key order and it's possible linux throws a different NSError as the error code you are using might come from obj-c. If you want to see the exact error code, you probably will need to add a print statement and then check the linux CI for the value of the code

[cbaker6]

Let me know if you need any help with finishing this. After this PR is merged, I'll release a new version.

[dblythy]

Sorry I’ll try wrap this up today!

[vdkdamian]

@dblythy Will this also show better error logging for when a certain key that is required in the database isn't filled in?

[dblythy]

Still testing locally to make sure this doesn't clash with other error codes

[dblythy]

@novemTeam I'm not sure to be honest, what error do you currently get when that happens?