Skip to content

Conversation

@kylebrowning
Copy link
Member

@kylebrowning kylebrowning commented Feb 14, 2023

This is the first PR among probably many to break out APNS into APNSCore, APNSAHC, APNSUrlSession, and APNS(a hyper optimized h2 client)

@vojtarylko
Copy link
Contributor

@kylebrowning Why APNSError.reason became private? The reason is vital for processing APNs' responses – for example sender may want to perform cleanup upon receiving Unregistered reason.

@kylebrowning
Copy link
Member Author

@vojtarylko Im trying to remind myself why we did, but I can't think of it atm, do you wanna open a PR?

@vojtarylko
Copy link
Contributor

@kylebrowning Thanks for the reply. I'll open PR.

vojtarylko added a commit to vojtarylko/APNSwift that referenced this pull request Apr 10, 2023
This commit restores public access to the `APNSError.reason` property,
because it's needed for library users handling APNs errors.  (The status
code is not an viable alternative, as there are multiple different error
reasons for one status code.)

The `reason` property was unintentionally set to private in commit
ecf0f44 (Breakout APNSwift into packages (swift-server-community#170)). Notably, the
associated type ErrorReason remained public.
kylebrowning pushed a commit that referenced this pull request Apr 11, 2023
This commit restores public access to the `APNSError.reason` property,
because it's needed for library users handling APNs errors.  (The status
code is not an viable alternative, as there are multiple different error
reasons for one status code.)

The `reason` property was unintentionally set to private in commit
ecf0f44 (Breakout APNSwift into packages (#170)). Notably, the
associated type ErrorReason remained public.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants