Add conditional conformance to Hashable to Firestore property wrapper types #6249
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This turns out not to actually work because NSDate does not conform to Codable. Users can supply their own extensions that make NSDate conform to Codable and also supply an extension like this one to make NSDate conform to ServerTimestampWrappable. Add a test that verifies ServerTimestamps of Dates actually work. The equivalent test for NSDate does not compile.
FirebaseFirestoreSwift was already using synthesized Equatable and Hashable conformance which requires Swift 4.1.
… types Mark these types as conforming to Hashable if the underlying type itself conforms to hashable. This implementation relies on synthesized Equatable and Hashable conformance that shipped as a part of Swift 4.1.
wu-hui
approved these changes
Aug 12, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Mark these types as conforming to
Hashableif the underlying type itself conforms toHashable. This implementation relies on synthesizedEquatableandHashableconformance that shipped as a part of Swift 4.1.Fixes #6237.