Skip to content
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

Change recommendation for Alamofire integration #92

Conversation

JonathanPorta
Copy link
Contributor

Issues with recommending Alamofire-SwiftyJSON:

  • Not updated for Xcode 6.1.
  • No longer necessary as a shim to integrate Alamofire and SwiftyJSON.
  • Adds another dependency that needs to be manually included and managed.

I feel that recommending a third, separate dependency is confusing and unnecessary to new users. It's only one line to have SwiftyJSON wrap the JSON returned by Alamofire.

Issues with recommending Alamofire-SwiftyJSON:
-  Not updated for Xcode 6.1.
-  No longer necessary as a shim to integrate Alamofire and SwiftyJSON.
- Adds another dependency that needs to be manually included and managed.
@LukeTangPL
Copy link
Member

@JonathanPorta you're right! But the pr should handle the error from Alamofire. Can you please add some error handling description?

@LukeTangPL LukeTangPL closed this Nov 12, 2014
@LukeTangPL LukeTangPL reopened this Nov 12, 2014
@JonathanPorta
Copy link
Contributor Author

@tangplin I added a simple example where the error object is checked first. I am not sure exactly if this is the best way to check the error. I am still new to Swift. :)

LukeTangPL added a commit that referenced this pull request Dec 11, 2014
…n-recomendation

Change recommendation for Alamofire integration
@LukeTangPL LukeTangPL merged commit b05c10b into SwiftyJSON:master Dec 11, 2014
@JonathanPorta JonathanPorta deleted the update-alamofire-integration-recomendation branch December 12, 2014 18:50
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