-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Xcode 15.0.1 #1377
Merged
Merged
Use Xcode 15.0.1 #1377
Changes from 3 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
746cb0b
Build with Xcode 15.0.1
jkmassel 4e32af6
Add additional string range bounds checking
jkmassel e73e1c8
Fix tests broken by iOS 14 pasteboard restrictions
jkmassel c076791
Test with iOS 17 and iPhone 15 Pro
jkmassel 39ebb60
Make Gutenpack renderer tests easier to debug
jkmassel 6f244bb
Fix snapshot tests
jkmassel 1539e7c
Disable podspec validation
jkmassel 5e4c974
Fix off-by-one issue with string indexes
jkmassel 71a459e
Fix linter issues
jkmassel 4436946
Apply Tony’s CocoaPods fix
jkmassel 1a00efb
Fix CocoaPods warnings
jkmassel 59f04a1
Bump iOS Min Version to 12.0
jkmassel 1dd0099
One more warning
jkmassel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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 file contains 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 file contains 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 file contains 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 file contains 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 file contains 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 file contains 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 file contains 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 file contains 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 file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that mean this line crashes if the selected attributed string contains an "attribute value" that doesn't conform to
NSCoding
? I don't really know anything about this library's implementation, not sure how likely that's going to happen...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good question, but also before the migration to Xcode 15 and newer Swift back when
archivedData
was not marked asthrows
, I'd expect the code would already crash (but maybe with an ObjC NSException rather than a Swift error being thrown)?That being said, it would be a nice improvement to use
let data = try? …
instead and then make the subsequent call tostoreInPasteboard(encoded: data)
conditional onif let data
; but not sure if that fix belongs in this PR or separate.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, looking at the deprecated vs new method signature for
NSKeyedArchiver.archivedData
, I'm wondering if the only case where it couldthrow
is if you passedrequiresSecureCoding: true
and the objects conformed toNSCoding
… but notNSSecureCoding
.But since here we use
requiresSecureCoding: false
in the implementation ofarchivedData
, maybe that means we'll never throw in practice? Or if we do, that would be under the same conditions as the ones the current version of the library already does, i.e. not related to Xcode 13->Xcode15 migration?