1.0 beta 4: Forget the Alamo (if you want)
Pre-release
Pre-release
- Alamofire is now truly optional when using Siesta as a
.framework
, thanks to Apple (apparently?) fixing problems with optional framework dependencies:- If you have not explicitly configure your Siesta
Service
to use Alamofire and you are using a binary version of Siesta, you can remove it from yourCartfile
. - If you are building Siesta from source (via Carthage or via Xcode), you still need Alamofire (for the build only).
- If you are using Alamofire with Carthage, you must include it in your
Cartfile
yourself. - If you are using Cocoapods, continue to use
pod 'Siesta/Alamofire'
to include Alamofire support.
- If you have not explicitly configure your Siesta
- Fixed: Configuration patterns match whole string instead of substring (e.g.
http://foo.com/**
no longer matcheshttp://bar.com/http://foo.com/
) - Fixed: Configuration patterns cause crash when
Service.baseURL
is nil - Fixed: Invalid request methods and unencodable JSON passed to the Objective-C API now cause request failures instead of crashes
- Code cleanup and refinement (There are now only two forced unwraps in the entire library)
- Clarifications & corrections throughout docs