Arrow Functions – Environment Remembering

Arrow functions are mainly intended to resolve several common pain points of traditional Function Expression. it will provide Lexical this binding and Short hand notations with ‘=>’ arrow symbol.
Definition (ECMA6 Standard): Arrow functions bind this lexically, bind return in the Block body case so it returns from the immediately enclosing arrow function.
Syntax: ArrowParameters [no LineTerminator here] => ConciseBody
[table class=”table table-striped”]
Arrow Function Syntax,Arrow Function Examples
(parameters) -> expression,”(x,y) => x * y”
(parameters) -> statement,() => console.log(“Hello JS”);
(parameters) -> { statements },(s) => { n = s.length(); return n;}
[/table]
Simply: which provide a shorter notation of anonymous functions + which binds only lexical this, no dynamic this
Pros: 

  • Much easier for the compiler to optimize, because it doesn’t need to worry about variables escaping from their lexical context, and so doesn’t need to go for chaining lookup.
  • Scope safety, Compactness, and Readability
  • An arrow function expression has a shorter syntax compared to function expressions
    Lexically binds the this value
  • Arrow functions are always anonymous
  • Arrow functions cannot be used as constructors.
  • Arrow functions never have an arguments objects
  • “=>” has only lexical this, no dynamic this

Cons: Not fit when a dynamic context is required like defining methods and get the target from this when handling events.
Lexical (Static) VS Dynamic Scope:
Lexical: Creates a new copy of variable names and values, organized in a hierarchy called “the environment”.
Dynamic: All variable names and their values live in one global table.
Common mistakes of using Arrow Functions:

  • new (() => {}) throws TypeError: (intermediate value) is not a constructor
  • a = (() => {});a.arguments;
    Throws TypeError: ‘caller’ and ‘arguments’ are restricted function properties and cannot be accessed in this context.

JSA
 

Javascript Closures

Many people are looking for JavaScript learning experience simple and covering info without confusion. I thought to introduce a series of ‘SimpleCards’ to explain JavaScript concepts in effective and efficient way. To avoid confusion on JS Closure concept I made a simple card for it.
Definition (Mozilla Docs): Closures are functions whose inner functions refer to independent (free) variables (variables that are used locally, but defined in an enclosing scope). In other words, the functions defined in the closure ‘remember’ the environment in which they were created
Simply: A closure is a special kind of object that combines two things: a function + environment in which that function were created.
Pros:

  • Bind a variable to an execution context
  • Emulating private methods with closures

Cons: Unnecessarily create closures will affect script performance both in terms of

  • Processing speed and
  • Memory consumption
    JavaScript Closures
    JavaScript Closures

Promises/deferred objects – asynchronous computations

Definition: (ECMA-2015)
A Promise is an object that is used as a placeholder for the eventual results of a deferred (and possibly asynchronous) computation.
A Promise represents an operation that hasn’t completed yet, but is expected in the future, while it’s in execution. Promises are very useful for remote calls to overcome network latency, once network responded promise will resolve or reject based on returned data.
Promise Abstract Operations:
[table class=”table table-striped”]
Field Name,Value type,Meaning
[[Promise]], An object, An object that is usable as a promise.
[[Resolve]], A function object, The function that is used to resolve the given promise object.
[[Reject]], A function object, the function that is used to reject the given promise object.
[/table]
We are using angular 1.x $q service to illustrate promises. $q is a similar implementation of promises concept by Kris Kowal’s Q.js. we can generate a new instance of promise by calling $q.defer(), which is equals new Promise() in ES 6. Deferred object contains promise property which is responsible for callback function executions such as onFulfilled, onRejected and progressBack.
Flex frameworks Action Script 3.0 also have a similar implementation like Q.js as AsyncToken,AsyncResponder. The syntax looks like below

//Flex AsyncToken usage
var token:AsyncToken = service.send();
token.addResponder(new mx.rpc.Responder(result, fault));

The $q object:
[table class=”table table-striped”]
Method Name,Meaning
$q. defer(),new instance of promise will returns a deferred object
$q.all(ArrayOfPromises),Combines multiple promises into a single promise that is resolved when all of the input promises are resolved.
[/table]
The Deferred object:
$q.defer() will returns a deferred object, which have below methods:
[table class=”table table-striped”]
Method Name,Meaning
deferred.resolve(value),resolves the derived promise with the value.
deferred.reject(reason),rejects the derived promise with the reason.
deferred.notify(value),provides updates on the status of the promise’s execution. This may be called multiple times before the promise is either resolved or rejected.
deferred.promise{}, An object that is usable as a promise
[/table]
The Promise object:
[table class=”table table-striped”]
Method Name,Meaning
then:function(onFulfilled, onRejected, progressBack)“, “it will hook result,fault and progress methods to a promise. then calls one of the callback methods asynchronously as soon as the result is available.”
catch(errorCallback), “shorthand for promise.then(null, errorCallback).one more way to provide fault method.”
[/table]
Below example will illustrate promises usage,

//$q for promises
//create module
var myApp = angular.module("promisesApp",[]);
//get $q as global Q for better and simple analysis
angular.injector(['ng', 'promisesApp']).invoke(function ($q) {window.Q = $q;});
//promisesApp.controller("promisCtrl",["$q",function(Q){
function result(response){
 console.log("Resolved and Response is:"+response);
 }
function fault(reason){
 console.log("Rejected and Error info: "+reason);
 }
function notify(update){
 console.log("Notification: "+update);
 }
function asyncExecution(resultObj,isResolvable,atTime){
 var defered = Q.defer();
 var promise = defered.promise;
 //Simulating network latency
 setTimeout(function(isResolvable){
 if(isResolvable){
 defered.notify('resolving now...');
 defered.resolve(resultObj);
 defered.notify('resolved');//notify Never prints, once promise resolved or rejects
 }
 else{
 defered.notify('rejecting now...');
 defered.reject("Got an Error");
 defered.notify('rejected');//notify Never prints, once promise resolved or rejects
 }
 },atTime,isResolvable);
 return promise;
}
var p1 = asyncExecution('p1',true,2000);
p1.then(result,fault,notify);
var p2 = asyncExecution('p2',false,3000);
p2.then(result,fault,notify);
var p3 = asyncExecution('p3',true,4000);
p3.then(result,fault,notify);

Output as following:

Notification: resolving now...
Resolved and Response is:p1
Notification: rejecting now...
Rejected and Error info: Got an Error
Notification: resolving now...
Resolved and Response is:p3

Promises Chaining:
Chaining is useful when we need to make synchronous calls to server. always promises will look for failure handler, if not present in current then-able it will look for next available then-able. chaining will continue only if a success handler on returning a promise object.  below example will explain about chaining of multiple promises.

//Chaining
var p1 = asyncExecution('p1',true,2000);
var p2 = asyncExecution('p2',true,3000);
var p3 = asyncExecution('p3',true,4000);
//promises will look for failure handler, if not present
//in current then-able it will look for next available then-able
p1.then(function(a){result(a);return p2})
//return Promise to continue chaining
.then(function(a){result(a);return p3})
.then(result);

Output as following:

Resolved and Response is:p1
Resolved and Response is:p2
Resolved and Response is:p3

Combine Multiple promises as one promise:

//let combin and know all promises are done or not
var p1 = asyncExecution('p1',true,2000);
var p2 = asyncExecution('p2',true,3000);
var p3 = asyncExecution('p3',true,4000);
Q.all([p1,p2,p3])
.then(function(){console.log('All Async tasks done')},
     function(){console.log('Failed:Soming worng!!')})
.finally(function(){
     console.log('Finally: I will execute any way')});

Output as following:

All Async tasks done
Finally: I will execute any way

The this Keyword Runtime Semantics – Part 2

Every Function Object Has Methods apply(), call() and bind().
All these methods useful to call an arbitrary function as if this function was declared as a method on a target object.
[table class=”table table-striped”]
Function,Function invoke,Scope Change,How to call,Args passing
Apply(),Yes,Yes,”Function.prototype.apply ( thisArg, argArray )”,As Array[]
Call(),Yes,Yes,”Function.prototype.call (thisArg , …args)”,As comma separated
Bind(),No,Yes,”Function.prototype.bind ( thisArg , …args)”,As comma separated
[/table]

share = {
 a52WeekHigh:100,
 a52WeekLow:55,
 publishValue:function (demandIncrease){
 var d = demandIncrease? '. Demand Increase By:'+demandIncrease+'%' : ''
 console.log("52 week High and Low:"+ this.a52WeekHigh+'-'+this.a52WeekLow + d);
 }
}
pqrShare={
 a52WeekHigh:99,
 a52WeekLow:17
}
share.publishValue(); //52 week High and Low:100-55
share.publishValue.apply(pqrShare); //52 week High and Low:99-17
share.publishValue.apply(pqrShare,[12]);
share.publishValue.call(pqrShare,13);
var bond = share.publishValue.bind(pqrShare,14);//function won't invoke
bond(); //52 week High and Low:99-17. Demand Increase By:14%

Output will come as following:

52 week High and Low:100-55
52 week High and Low:99-17
52 week High and Low:99-17. Demand Increase By:12%
52 week High and Low:99-17. Demand Increase By:13%
52 week High and Low:99-17. Demand Increase By:14%

The this Keyword Runtime Semantics

A function’s this keyword in JavaScript have a different behavior than other languages, even it will represent different behavior between strict mode and non-strict mode. In JavaScript while executing a function this keyword plays a vital role.
Global Ref:
If there is no parent/owner for a function, it will execute as global function.

var noParentFunction = function () {
console.log(toString.call(this)); // [object Window]
};
//Call Method
noParentFunction();

When we execute noParentFunction function it will yield this object reference as window(global ref). As per JavaScript lexical rules if there is no specific parent of a function it will fall under window. There is no deference between below two statements:

noParentFunction();
Window.noParentFunction();

Object Ref:
Whenever we call parent.child() child function always get this scope as parent’s. now we create a parent, it will have function child:

var parentClass = {
name:'parent',
childMethod: function (){console.log(this === parentClass);} //->true
};
// call the method
parentClass.childMethod();//->true

Inherited Function:
when we create parent function, use this keyword inside to transfer your properties when object inherited.

var parentClass = function(){
//attach childMethod to parentClass scope by using this keyword
this.childMethod= function (){console.log(this);};
};
// Inherited parent1
var parent1 = new parentClass();
// call the method
parent1.childMethod();//->parentClass

Inherited function with prototype:
Same as above inherited prototype methods this scope works.

var parentClass = function(){
//attache childMethod to parentClass scope by using this keyword
this.childMethod= function (){console.log(this);};
};
//add prototype methode
parentClass.prototype.parentPrototype = function ()
{
console.log(this);
}
// call the method
var parent1 = new parentClass();
parent1.childMethod();//->parentClass
parent1.parentPrototype();//->parentClass

Directives scope in AngularJS

Scope is context where the model is stored so that controllers, directives and expressions can access it. By default, each directive inherits its parent’s scope, which is passed to it in the link function. below three options are described scope creation in angularjs,

Scope:false (default) which basically tells AngularJS that the directive scope is the same as the parent scope.
Example: If scope:false means it will simply return same address location of parent scope.
working Fiddle.

return {
    restrict: 'A',
      scope:false,
    template: '',
    link: function(scope, element, attrs) {
        console.log(scope);
        scope.data = scope.data + " + directive postfix";
        child = scope;
    }

Result:

 image01

Scope:true creates new scope object but never override parent properties. The directive thus gets access to all the variables and functions from the parent scope, but any modifications it makes are not available in the parent.
Example: create a child scope prototypically inherited with scope: true.
working Fiddle.

return {
    restrict: ‘A’,
      scope:true,
    template: ”,
    link: function(scope, element, attrs) {
        console.log(scope);
        scope.data = scope.data + ” + directive postfix”;
        child = scope;
    }

Result:

image00

Scope:{} (isolated scope) This scope does not inherit anything from the parent, and any data that the parent scope needs to share with this directive needs to be passed in through HTML attributes
Example: create an isolated scope with scope: {} then you can bind some property to parent scopes with ‘@’, ‘&’, ‘=’.
working Fiddle.

return {
    restrict: ‘A’,
      scope:{},
    template: ”,
    link: function(scope, element, attrs) {
        console.log(scope);
        scope.data = scope.data + ” + directive postfix”;
        child = scope;
    }

Result:

image02