MBNetwork is a network request framework based on Alamofire and ObjectMapper, aiming at making network request easier for business development.
MBNetwork has made advantages of protocol-oriented programming and abstracted everything that relevant to network request into protocol. Here is the protocol list:
MBRequestable
: Network request protocol, object conforms to this protocol can make network request.MBFormable
: Form protocol. Object conforms to this protocol can be used by therequest
,download
,upload
method inMBRequestable
protocol.MBUploadFormable
: Upload Form protocol, Base protocol for upload request form.MBUploadStreamFormable
: Conforming to this protocol to create an upload form that contains a stream object.MBUploadDataFormable
: Conforming to this protocol to create an upload form that contains a data object.MBUploadFileFormable
: Conforming to this protocol to create an upload form that contains a file.MBUploadMultiFormDataFormable
: Conforming to this protocol to create an upload form that contains multiformdata.
MBDownloadFormable
: Download Form protocol, Base protocol for download request form.MBDownloadResumeFormable
: Conforming to this protocol to create a download form that can resume a download task.
MBRequestFormable
: Conforming to this protocol to create a request form.
MBLoadable
: Protocol used for showing mask on specified container when requesting (such as addUIActivityIndicatorView
onUIViewcontroller
's view when request begins, and remove it when request ends). Object conforms to this protocol can be used byload
method ofDataRequest
.MBMaskable
: Mask protocol forMBLoadable
, View that conforms to this protocol will be treated as mask.MBContainable
: Container protocol forMBLoadable
, Objects conforms to this protocol can be used as container for the mask.MBProgressable
: Progress protocol for request, Objects conforms to this protocol can get the progress of the request. Object conforms to this protocol can be used byprogress
method ofDataRequest
.
MBMessageable
: Message protocol.MBWarnable
: Warn protocol. Conforming to this protocol to customize the way of warning messages displayed when error occured.MBInformable
: Inform protocol. Conforming to this protocol to customize the way of inform messages displayed when request done successfully
MBErrorable
: Error protocol. Conforming to this protocol to customize the error configuration.MBJSONErrorable
: Error protocol for JSON data. Conforming to this protocol to customize the error configuration for JSON data.
Mostly you don't need to care much about these protocols, because we already have many DEFAULT implementations for them. However if you want to customize something, you just need to conform to these protocols and do what you want. Here is some default implementations for these protcols:
MBLoadType
: Enum that conforms toMBLoadable
protocol, usingcase default(container:MBContainable)
case to showMBMaskView
on the container when requesting.MBMessageType
: Enum that conforms toMBMessageable
protocol, usingalertController(title: String, message: String? , actions: [UIAlertAction], container: MBContainable)
case to show alertController.UIButton+MBLoadable
: With this extension, you can pass a button directly into theload
method ofDataRequest
.UITableViewCell+MBLoadable
: With this extension, you can pass a cell directly into theload
method ofDataRequest
.UIRefreshControl+MBLoadable
: With this extension, you can pass a UIRefreshControl directly into theload
method ofDataRequest
.UIProgressView+MBProgressable
: With this extension, you can pass a UIProgressView directly into theprogress
method ofDataRequest
.UIScrollView+MBContainable
: Extending UIScrollView to conform toMBContainable
protocol.UITableViewCell+MBContainable
: Extending UITableViewCell to conform toMBContainable
protocol.UIViewController+MBContainable
: Extending UIViewController to conform toMBContainable
protocol.MBActivityIndicator
: Default mask for UITableViewCell and UIButtonMBMaskView
: Default mask for others.
- There is no need to inherit any object to get the features it has, and you can extend any features you want without changing the code of MBNetwork itself.
- We have Default extension for most of the protocol, so you can easily startup.
- And if you have special needs, extend or conform to it.
- The API was designed with the principles of Alamofire, So you can also extend it as MBNetwork already have done for you.
- Mainly focus on things between business development and Alamofire, not network request itself.
- Alamofire: Elegant HTTP Networking in Swift
- ObjectMapper: Simple JSON Object mapping written in Swift
- AlamofireObjectMapper: An Alamofire extension which converts JSON response data into swift objects using ObjectMapper
For business development, most of the requests' headers are the same, so you can extend it only for once.
extension MBFormable {
public func headers() -> [String: String] {
return ["accessToken":"xxx"];
}
}
And you can also have extension for specified protocol
extension MBFormable where Self: MBUploadFormable {
public func headers() -> [String: String] {
return ["accessToken":"xxx", "file":"xxx"];
}
}
And for other parameters such as url
, method
, parameters
etc.
Each request will has it's own value, So we create an object and make it conforms to the protocol
struct WeatherForm: MBRequestFormable {
var city = "shanghai"
public func parameters() -> [String: Any] {
return ["city": city]
}
var url = "https://raw.githubusercontent.com/tristanhimmelman/AlamofireObjectMapper/2ee8f34d21e8febfdefb2b3a403f18a43818d70a/sample_keypath_json"
var method = Alamofire.HTTPMethod.get
}
All you have to do is conforming to MBRequestable
protocol, in this protocol, we've already implement some methods for you:
func request(_ form: MBRequestFormable) -> DataRequest
func download(_ form: MBDownloadFormable) -> DownloadRequest
func download(_ form: MBDownloadResumeFormable) -> DownloadRequest
func upload(_ form: MBUploadDataFormable) -> UploadRequest
func upload(_ form: MBUploadFileFormable) -> UploadRequest
func upload(_ form: MBUploadStreamFormable) -> UploadRequest
func upload(_ form: MBUploadMultiFormDataFormable, completion: ((UploadRequest) -> Void)?)
Here is the usage of request method:
class LoadableViewController: UIViewController, MBRequestable {
override func viewDidLoad() {
super.viewDidLoad()
// Do any additional setup after loading the view.
request(WeatherForm())
}
}
We have extended DataRequest
class of Alamofire and added a load
method to it.
func load(load: MBLoadable = MBLoadType.none) -> Self
request(WeatherForm()).load(load: MBLoadType.default(container: self))
request(WeatherForm()).load(load: button)
Notice: The color of
UIActivityIndicatorView
is thetintColor
ofUIButton
Firstly, we create a LoadConfig
class conforms to MBLoadable
protocol.
class LoadConfig: MBLoadable {
init(container: MBContainable? = nil, mask: MBMaskable? = MBMaskView(), inset: UIEdgeInsets = UIEdgeInsets.zero) {
insetMine = inset
maskMine = mask
containerMine = container
}
func mask() -> MBMaskable? {
return maskMine
}
func inset() -> UIEdgeInsets {
return insetMine
}
func maskContainer() -> MBContainable? {
return containerMine
}
func begin() {
show()
}
func end() {
hide()
}
var insetMine: UIEdgeInsets
var maskMine: MBMaskable?
var containerMine: MBContainable?
}
Then we can use it as followed:
let load = LoadConfig(container: view, mask:MBEyeLoading(), inset: UIEdgeInsetsMake(30+64, 15, UIScreen.main.bounds.height-64-(44*4+30+15*3), 15))
request(WeatherForm()).load(load: load)
This is the most powerful usage of the MBLoadable
protocol. In this way you can customized everything the MBLoadable
protocol has.
let load = LoadConfig(container:self.tableView, mask: MBActivityIndicator(), inset: UIEdgeInsetsMake(UIScreen.main.bounds.width - self.tableView.contentOffset.y > 0 ? UIScreen.main.bounds.width - self.tableView.contentOffset.y : 0, 0, 0, 0))
request(WeatherForm()).load(load: load)
refresh.attributedTitle = NSAttributedString(string: "Loadable UIRefreshControl")
refresh.addTarget(self, action: #selector(LoadableTableViewController.refresh(refresh:)), for: .valueChanged)
tableView.addSubview(refresh)
func refresh(refresh: UIRefreshControl) {
request(WeatherForm()).load(load: refresh)
}
override func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
tableView .deselectRow(at: indexPath, animated: false)
let cell = tableView.cellForRow(at: indexPath)
request(WeatherForm()).load(load: cell!)
}
We can also support other refresh control such as MJRefresh
.
We have extended DownloadRequest
and UploadRequest
class of Alamofire and added a progress
method to it.
func progress(progress: MBProgressable) -> Self
And then we can use it as followed:
download(ImageDownloadForm()).progress(progress: progress)
We have extended DataRequest
class of Alamofire and added a warn
method to it.
func warn<T: MBJSONErrorable>(error: T, warn: MBWarnable = MBMessageType.none, completionHandler: ((MBJSONErrorable) -> Void)? = nil) -> Self
And then we can use it as followed:
request(WeatherForm()).warn(error: WeatherError(), warn: MBMessageType.alertController(title: "Warning", message: "Network unavailable", actions: [UIAlertAction(title: "Ok", style: UIAlertActionStyle.cancel, handler: nil)], container: self))
Notice: We only have
warn
for JSON format response now.
We have extended DataRequest
class of Alamofire and added a inform
method to it.
func inform<T: MBJSONErrorable>(error: T, inform: MBInformable = MBMessageType.none) -> Self
And then we can use it as followed:
request(WeatherForm()).inform(error: WeatherInformError(), inform: MBMessageType.alertController(title: "Notice", message: "Load successfully", actions: [UIAlertAction(title: "Ok", style: UIAlertActionStyle.cancel, handler: nil)], container: self))
Notice: We only have
inform
for JSON format response now.
request(WeatherForm()).responseObject(keyPath: "data") { (response: DataResponse<WeatherResponse>) in
if let value = response.result.value {
self.weatherResponse = value
self.tableView.reloadData()
}
}
For more information, see AlamofireObjectMapper.
All the method mentioned above can be called in a chained manner, such as followed:
let load = LoadConfig(container: view, mask:MBEyeLoading(), inset: UIEdgeInsetsMake(30+64, 15, UIScreen.main.bounds.height-64-(44*4+30+15*3), 15))
let warn = MBMessageType.alertController(title: "Warning", message: "Network unavailable", actions: [UIAlertAction(title: "Ok", style: UIAlertActionStyle.cancel, handler: nil)], container: self)
let inform = MBMessageType.alertController(title: "Notice", message: "Load successfully", actions: [UIAlertAction(title: "Ok", style: UIAlertActionStyle.cancel, handler: nil)], container: self)
request(WeatherForm()).load(load:load).progress(progress: progress).warn(error: WeatherError(), warn: warn).inform(error: WeatherInformError(), inform: inform)
We've written this motion effect when implementing the customized loading, and it's all implemented with CAAnimationGroup
.
If interested, you can check the file MBEyeloading
in example project.
To run the example project, clone the repo, and run pod install
from the Example directory first.
MBNetwork is available through CocoaPods. To install it, simply add the following line to your Podfile:
pod "MBNetwork"
mmoaay, mmoaay@sina.com
MBNetwork is available under the MIT license. See the LICENSE file for more info.