[WIP] Add an associated AttachmentMetadata
type to Attachable
.
#824
+314
−88
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.
This PR adds a new associated type to
Attachable
that can be used to supply additional metadata to an attachment that is specific to that type. Metadata is always optional and the default type isNever
(i.e. by default there is no metadata.)The
Encodable
andNSSecureCoding
conformances in the Foundation cross-import overlay have been updated such that this type equals a new structure that describes the format to use as well as options to pass to the JSON encoder (if one is used) and user info to pass to the plist or JSON encoders (if used.) We must use this type even for types that conform only toNSSecureCoding
, otherwise we get compile-time errors about the type being ambiguous if a type conforms to both protocols and toAttachable
.Checklist: