Method Swizzling is the process of changing the implementation of methods of a class at runtime.
Let’s see some use cases of Method Swizzling.
I want to do something before all of my ViewController’s ViewWillAppear,
Like,
- I need to display an alert to the user If the auth token expires and user has to Re-Login
- I need to display an offer to the user as a Banner whatever may be the screen that user presently is in.
In these cases, Actually we can go with a Base class and write our logic in the Base class.
But this is not the correct approach.
Because, We need to write Base classes for not only UIViewController, But also for UITableViewController, UINavigationController, UITabBarController and all which we use in our app.
If we go with Base classes, Our code will be redundant and there will be multiple base classes for the same piece of code.
Let’s see a code example of Base class approach, And then we will see the how Method Swizzling solves that without code redundancy.
I have two View Controllers.
------------------------------------------------------------------------
class ViewController: BaseViewController {
override func viewWillAppear(_ animated: Bool) {
super.viewWillAppear(animated)
}
}
class ViewController2: BaseViewController {
override func viewWillAppear(_ animated: Bool) {
super.viewWillAppear(animated)
}
}
------------------------------------------------------------------------
In my Base class I will just write the log and consider that as my logic I needed to get executed before my ViewWillAppear.
------------------------------------------------------------------------
class BaseViewController: UIViewController {
override func viewWillAppear(_ animated: Bool) {
super.viewWillAppear(animated)
print("UIViewController - Display Notification!")
}
}
------------------------------------------------------------------------
We are good here, As both View Controllers are Inherited from BaseViewController, Our notification will get fired at the time of these controllers viewWillAppear.
Now, There is a TableViewController.
------------------------------------------------------------------------
class TableViewController: UITableViewController {
let users = ["user1", "user2", "user3", "user4"]
// MARK: - Table view data source
override func numberOfSections(in tableView: UITableView) -> Int {
// #warning Incomplete implementation, return the number of sections
return 1
}
override func tableView(_ tableView: UITableView, numberOfRowsInSection section: Int) -> Int {
// #warning Incomplete implementation, return the number of rows
return users.count
}
override func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell {
let cell = tableView.dequeueReusableCell(withIdentifier: "cellID", for: indexPath)
cell.textLabel?.text = users[indexPath.row]
return cell
}
}
------------------------------------------------------------------------
Obviously, I can not extend it from BaseViewController, Cause, If I do, We will end up with errors like shown below.
That means, UITableViewController will lose it’s characteristics If we go with BaseViewController as a base class and there is no point in taking a UITableViewController
Same applies to UINavigationController.
------------------------------------------------------------------------
class NavigationController: UINavigationController {
override func viewWillAppear(_ animated: Bool) {
super.viewWillAppear(animated)
}
}
------------------------------------------------------------------------
If we take BaseViewController as base class, UINavigationController loses it’s characteristics and your push and pop will not work.
So for UITableViewController and UINavigationControllers also, We need to take Base Classes.
------------------------------------------------------------------------
class BaseTableViewController: UITableViewController {
override func viewWillAppear(_ animated: Bool) {
super.viewWillAppear(animated)
print("UITableViewController - Display Notification")
}
}
------------------------------------------------------------------------
Such a bad approach with such a code redundancy.
In the next tutorial, Let’s see how this can be solved using Method Swizzling.
Hope this post is useful. Feel free to comment incase of any queries.
| Swift Protocols & Extensions |
|---|
| Swift Comparable Protocol |
| Swift Equatable Protocol |
| Protocol Extensions for Default and Convenient API |
| Protocols vs Base classes |
| Multiple Inheritance using protocols |
| Swift Protocol Extensions |
| Swift Constrained Extensions |
| Multiple Inheritance, Diamond problem |
| Multiple Inheritance using protocols, Diamond Problem |
| Swift - Preserving Structure Default Initializer using Extensions |
| Swift Closures |
|---|
| Swift Closures Capture List |
| Swift Escaping Closures (@escaping) |
| Swift - weak and unowned references |
| Swift 4 Tutorials |
|---|
| Swift 4 NEW Tutorial-1 (One Sided Ranges) |
| Swift 4 NEW Tutorial-2 (Strings are Collections Again) |
| Swift 4 NEW Tutorial-3 (private instead fileprivate) |
| Swift 4 NEW Tutorial-4 (fileprivate to private) |
| Swift CoreData Tutorials |
|---|
| Swift - CoreData - CRUD Operations (Tutorial-1) |
| Swift - CoreData - Validations (Tutorial-2) |
| Swift - CoreData - To One Relationship (Tutorial-3) |
| Swift - CoreData - To One - Inverse Relationship (Tutorial-4) |
| Swift - CoreData - To Many - Inverse Relationship (Tutorial-5) |
| Method Swizzling Tutorials |
|---|
| Swift 4, Method initailize defines Objective-C class method initialize(), which is not guaranteed to be invoked by Swift and will be disallowed in future versions |
| Swift 4 Method Swizzling (Part 2/2) |
| Swift 4 Method Swizzling (Part 1/2) |
| NSPredicate Tutorials |
|---|
| Objective C NSPredicate Part 1/4 |
| Objective C NSPredicate Part 2/4 |
| Objective C NSPredicate Part 3/4 |
| Objective C NSPredicate Part 4/4 |
| iOS Fixing Security Vulerabilities Tutorials |
|---|
| iOS Format String Attacks |
| iOS Jailbreak Unchecked File Operation Result Code |
| iOS Screen Caching Security Vulnerability |
| XMPP Chat Framework Tutorials |
|---|
| Encoding & Decoding emoji characters In the chat applications using Objective C |
| Objective C methods for new user registration in xmpp framework |
| Objective-C XMPP search users by username |
| Retrieving chat history from Openfire using XMPP |
| Displaying emoji characters in UILabel |
| Getting old messages or chat history from XMPP |
| XMPP searching users by username |
| XMPP framework User Registration Methods |
| XMPP user change password using Objective C |
| Change XMPP registered user password |
| Blog Archive |
|---|
| Custom cell class data source in MVVM design pattern |
| Swift - Multiple levels of Optional Binding |
| Swift - App is currently in Main Thread or not |
| Swift Nil-Coalescing Operator for Optionals |
| Enum raw value comparisons |
| guard statement return/break/continue |
| Case-sensitive and Case-Insensitive sorting |
| valueForKey (vs) objectForKey |
| If-Let & Guard-Let Multiple Optional Bindings |
| Color and Image Literals |
| Swift Enums as Models |
| Swift convenience initializers |
| Tappable links in UITextView |
| UITableView Scrolling issue for cells having UITextField/UITextView as subviews |
| illegal Configuration Safe Area Layout Guide before iOS 9.0 |
| iOS Checking device is in 24 hour format or not |
| Displaying URL loading error in WebView in HTML format |
| Checking whether iOS app is running in a device having safe area (iPhoneX) or not |
| xcodebuild: error: invalid option '-exportFormat' |
| Interface Segregation Principle in SOLID (Object-Oriented Design) |
| Swift - Handling web links in dynamic content |
| Swift - Class and Static Methods |
| Swift - MVVM - RXSwift Instead of didSet() |
| Swift Failable Initializers |
| Objective-C/Swift avoid crashes in iPad in an iPhone Application |
No comments:
Post a Comment