5.9.2-alpha.1

What's Changed

• ci: fix repo documentation deployment by @cbaker6 in #161

Full Changelog: 5.9.1...5.9.2-alpha.1

5.9.1

Full Changelog, Documentation

Fixes

• Build for visionOS properly (#160), thanks to @cbaker6.
• Cocoapods now defaults to Swift 5.10 (#159), thanks to @cbaker6.

5.9.0

Full Changelog, Documentation

New features

• Cocoapods now defaults to Swift 5.9 (#146), thanks to @cbaker6.
• Add support for visionOS (#143), thanks to @cbaker6.
• Add fetchAll method to array of Parse Pointer Object's (#141), thanks to @cbaker6.

Fixes

• Improve mutiple types conformance to Equatable and Hashable (#148), thanks to @cbaker6.
• Updates to ParseUser password now persists the updated sessionToken from the server to the client Keychain (#147), thanks to @cbaker6.

5.8.2

Full Changelog, Documentation

Fixes

• Expose isSaved method on ParseFile and ParseOperation (#135), thanks to @cbaker6.

5.8.1

Full Changelog, Documentation

Fixes

• There was an issue where Parse pointers were not sending includeKeys to the server (#133), thanks to @proj-sashido.

5.8.0

Full Changelog, Documentation

New features

• Add concrete types: ParseHookTrigger and ParseHookFunction to reduce code developers need to write. Deprecate triggerName in favor of trigger where possible. The SDK also yields for 0.5 second as oppose to 1 second, which can lead to faster app starts (#122), thanks to @cbaker6.

Fixes

• There was a problem when the developer did not implement merge() on a ParseObject and depended on the internal mergeAutomatically() to merge. If the developer used mergeAutomatically() indirectly for objects with different objectId's, the method allowed the merge. Now the method throws the proper error (#122), thanks to @cbaker6.

5.7.4

Full Changelog, Documentation

Fixes

• hydrateUser() should not replace the options passed in (#121), thanks to @cbaker6.

5.7.3

Full Changelog, Documentation

Fixes

• Remove all generic shadow warnings in Swift 5.9 (#120), thanks to @cbaker6.

5.7.2

Full Changelog, Documentation

Fixes

• ParsePolygon encoding during a save and decoding resulted in (longitude, latitude) when it should be (latitude, longitude). If a developer used ParseSwift <= 5.7.1 to save/update ParsePolygon's, they will need to update the respective ParseObjects by swapping the latitude and longitude manually. Deprecated withinPolygon() query constraint for geoPoint() and polygonContains() for polygon() (#118), thanks to @cbaker6.

5.7.1

Full Changelog, Documentation

• ParseACL.defaultACL() calls should yield until SDK has finished configuration (#117), thanks to @cbaker6.
• ParsePolygon.containsPoint() correctly uses longitude and latitude (#116), thanks to @cbaker6.