Skip to main content

underscore.js extend


underscore.js is a javascript utility library.

Let us understand the extend method of this very useful library.
_.extend is for extending a given object with all the properties of the passed-in object(s)

Here is an example, we have three objects aObj, bObj, cObj and we want to combine them into single object.


















Using _.extend is a simple way of combining these objects. And before trying out the example don't forget to import the underscore.js library

Now access the source code of underscore.js and look for the extend method. This is how it looks like

This uses functional programming style. 
createAssigner takes two inputs and returns a function. The two inputs are
(1) keysFunc 
(2) defaults

Since it is returning a function, so a closure is formed, and the returned function remembers the two inputs
Looking at the source code from the line (keys = keysFunc(source)) it is evident that keysFunc is a function itself.
And from the line _.extend = createAssigner(_.allKeys) we can understand that allKeys is the function that is passed as input for keysFunc. Here is the allKeys function from underscore.js



To the function that is returned by createAssigner, we pass the objects whose properties have to be combined as the inputs. In our example aObj, bObj and cObj are passed to the return function of createAssigner function.

aObj is the source object, bObj and cObj are the objects that have to be merged with aObj.
Note that extend mutates the aObj. The resultant aObj has the properties from all the objects passed for merging with aObj







Labels:

Comments

Post a Comment

Popular posts from this blog

Kubernetes: 6. Imperative Commands

Imperative commands are useful in quickly creating the resources on Kubernetes kubectl --dry-run -> When created with this option, Kubernetes just validates the definition and does not actually create the resource -o=yaml -> Gets the output in YAML format kubectl run nginx-pod --image=nginx:alpine  -> Create a pod with name nginx-pod and image nginx:alpine kubectl run httpd --image=httpd:alpine  -> By default, run implies run-a-pod kubectl run redis --image=redis:alpine --labels=tier=db  -> Create a pod with name redis and image redis:alpine and labels set to tier=db kubectl run custom-nginx --image=nginx --port=8080  -> Create a pod with name custom-nginx and image nginx to run on port 8080 kubectl expose pod redis --port=6379 --name=redis-service  -> Create a service with name redis-service to expose pod named redis on service-port 6379 kubectl create deployment webapp --image=kodekloud/webapp-color --replicas=3  -> Create a depl...
Post a Comment
Read more

Kubernetes: 21. Secrets

Passwords In the webapps we store the properties file for storing and retrieving the data required by application But we never store the application passwords, truststore, keystore passwords etc here We might store them in an encrypted format, but storing them as plain text is not the correct way In Kubernetes we store these sensitive information in Secrets https://medium.com/avmconsulting-blog/secrets-management-in-kubernetes-378cbf8171d0 Secrets Secrets are used to store the sensitive information They are similar to ConfigMaps, except that they are stored in hashed or encoded format Note that they are only encoded (using base64) but are not encrypted So secrets are a safe option to store sensitive information but infact they are not the safest option As such secret objects should be not checked into source code tools, its best to store them encrypted at REST in ETCD Again as in ConfigMaps, we have to create the secrets object first and then inject them into the pods There are 2 ways ...
Post a Comment
Read more

Kubernetes: 19. Configure Application

Configuring application consists of Configuring commands and arguments on applications Configuring environment variables Configuring secrets Docker Commands docker run ubuntu  -> Runs ubuntu container and exit, container CMD is set to [bash], so the container quitely exits docker run ubuntu echo "Hello World" -> Runs ubuntu container, prints "Hello World" exits quitely. To update the default settings, create your own image from the base image lets call this ubuntu-sleeper image FROM ubuntu CMD sleep 5 CMD can also be mentioned in the JSON format like CMD ["sleep", "5"] Note that with JSON format the first element should always be the command to execute,  for eg, it CANNOT be ["sleep 5"] Run build the new ubuntu-sleeper image and run the new image docker build -t ubuntu-sleeper .  -> Build the image docker run ubuntu-sleeper -> Run the new image So the new image will launch ubuntu container, sleep for 5 seconds and quitely ex...
Post a Comment
Read more