This repository has been archived by the owner on Jan 26, 2021. It is now read-only.
Fix compatability with 0.24.0 #16
Open
Conversation
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
Swap Operation to Operation.Data in two places I know you said you're deprecating this, but I don't know how to migrate to use the new features you mentioned, so for now we're maintaining it this way.
gsbernstein
changed the title
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.
Change
OperationtoOperation.Datain two places, and update the version in the podspecI think this is the change that broke it, or simultaneous with it.
I know you said you're deprecating this, but I don't know how to migrate to use the new equivalent features, so for now we're maintaining it this way, and I thought other people might be interested. If you know of a migration guide I'd love to see it so we can remove Alamofire in some places!