Understanding Property Wrappers Swift

-

Property Wrappers


Property wrappers in swift help us to separate the code that manages the validation and the code that actually defines it.


Code that defines the property


var userId: Int

Code that manages the storage

@UserIdentifier var userId: Int



@UserIdentifier is a custom way to manage the storage. Don't worry it will be more clear in some time, but my whole point was to clear the understanding on the difference between defining and managing a property (with the help of Property Wrapper). 


Consider a use case of UserIdentifier:


  1. We want to have a userId which can take maximum up to 100 ids.
  2. If a user tries to set it to a value more than 100, it won't allow
  3. Provide a validation flag if value exceeds then 100. i.e true if any adjustments made or else false. 


Think of this validation to be added at 5 different properties of different class. It would be very difficult to manage , may be write extension to handle this. 


extension Int {

    func validateMax() -> Int {

        if self > 100 {

            return 100

        }

        return self

    }

}


Probably not the best way. Also it does not tell us the property was modified or not.


Let's try with a different approach , using Property Wrapper. Here we write the management code once and apply it to multiple properties.


Writing the management code will be bit extensive but using it will be a piece of cake  ( by using just the attribute @UserIdentifier)


import Foundation



@propertyWrapper

struct UserIdentifier {

    private var userId: Int

    

    /// Second functionality of Property Wrapper - Projected Value

    var projectedValue: Bool

    

    init() {

        projectedValue = false

        userId = 0

    }

    

    /// First functionality of Property wrapper - Wrapped Value

    var wrappedValue: Int {

        get {

            return userId

        }

        

        set {

            if newValue > 100 {

                userId = 100

                projectedValue = true

            } else {

                userId = newValue

                projectedValue = false

            }

        }

    }

}



struct UserDetails {

    @UserIdentifier var userId: Int

}


        var userDetails = UserDetails()

        userDetails.userId = 2

        print("Projected Value => \(userDetails.$userId)")

        print("Wrapped Value => \(userDetails.userId)")


What is Wrapper Name ?


Wrapper name is "UserIdentifier" .

How to apply Property Wrapper to a Property?

We user the property Wrapper name i.e "UserIdentifier" before a property as an attribute


(@) => attribute

(wrapper name) => UserIdentifier

var userId: Int => property name


Combining all of them together , we apply Property Wrapper to a property.


 @UserIdentifier var userId: Int


Wrapped Value


UserIdentifier structure makes sure's the number it wraps always has number less than or equal to 100.

Any attempt to set a value more than 100, will limit to 100.


How to access wrapped Value?

Accessing the wrapped value is same as accessing the property no special syntax.


So if the structure "UserDetails" uses property wrapper for "userId" , we access it like "userDetails.userId"



Projected Value


Projected value can be of any type , in case of above example we are using it as Bool. 


The projected value provides additional details of an instance in case any value being set is out of the range i.e more than 100 or less than 100 in the above case.


How to access projected Value?


Simple, just add "$" before the value being accessed. In case of above example it will be userDetails.$userId


In the example above it will print false , when we try to set the value of "userId" to 2.


If we try to set value for example 102. It will print true.


userDetails.userId = 102


It will print true for projected value.



userDetails.$userId 









Comments

Post a Comment

Popular posts from this blog

hitTest on iOS to identify the view being hit

-
Image
HitTest on iOS Use hitTest, to identify the view being tapped. The below method allows us to identify the view being selected. We can use it, to identify the view from which we would like to hide the touch events or identify the view we are interested into. Example: In the below case when we tap on Black View we can show an alert like "Black View tapped!" , if we tap on Red View , we can show an alert  "You are not allowed to tap on Red View" .  override func hitTest ( _ point: CGPoint , with event: UIEvent ?) -> UIView ? { } Here is a simple implementation of the method, to identify the view being hit. View hierarchy being used is listed below:- Blue(parent) - Red(child) - Green(child) - Yellow (child) - Orange (child) - Black (child) - White (child) So lets' start with override of hitTest method.      override func hitTest ( _ point: CGPoint , with event: UIEvent ?) -> UIView ? {         //1       ...
Read more

CMTimeMakeWithSeconds explained

-
Image
CMTime  is structure which has two main components,  timeScale  and  value. CMTIME = VALUE  / TIMESCALE where, TimeScale =  fraction of a second each unit in numerator occupies. CMTIME = Value / TimeScale 1)  public   func  CMTimeMake( _  value:  Int64 ,  _  timescale:  Int32 ) ->  CMTime CMTimeMake ( 6000 ,  10 ) Means, there are 6000 units , each unit occupies 1/10 of a second 2)  public   func  CMTimeMakeWithSeconds( _  seconds:  Float64 ,  _  preferredTimescale:  Int32 ) ->  CMTime CMTimeMakeWithSeconds(10.0,500) 10.0 = VALUE /500 Therefore VALUE = 5000 So, there are 5000 units, each occupy 1/500 of a second
Read more

How to set Custom Section Header in UITableView for ios sdk version greater than 6

-
Image
Dear Friends, As we know, that to set a custom Section Header in a TableView we need to call the following. Here we pass our own custom View. But, remember the view which we returned was never reusable, hence not memory efficient. -( UIView *) tableView:( UITableView *)tableView viewForHeaderInSection:( NSInteger )section Later version of iOS , starting from iOS 6, helps to make our code Memory efficient with few lines of code. Still here the delegate method remains the same. With the help of this tutorial we will be able achieve a Custom Header implementation using iOS 6 or greater sdk. We will be creating a app. which would look like as shown below. Please use the following steps to achieve this: Step 1: Create a .xib file for the custom header 1. Press command + N 2. Select User Interface in Left Pane. 3. Then Select a View and name it as TableHeader. Step 2: Create a Custom class for the custom header in Step 1 1. Press command...
Read more