The Mastering the Arcane Art of JavaScript-mancy series are my humble attempt at bringing my love for JavaScript to all other C# developers that haven’t yet discovered how awesome this language and its whole ecosystem are. These articles are excerpts of the super duper awesome JavaScript-Mancy book a compendium of all things JavaScript for C# developers.
In the last couple of articles we learned some useful patterns with functions in JavaScript that helped us achieve default arguments and multiple arguments and we saw how ECMAScript 2015 (ES6) can simplify the way we can incorporate either of these in our code.
Today I will close this section - useful function patterns - with some tips on how you can achieve function overloading in JavaScript. Hope you like it!
If you are also interested in knowing about the process I used to prepare for the exam take a look at How I passed the 70-480 Certification Exam where I describe it (since I did the same things to prepare both exams).
Last week I watched a very interesting Pluralsight webinar where Joe Eames introduced Angular 2 and I wanted to share what I learned from it with you.
A couple (or four) weeks ago Angular 2 went into developer preview with a beautiful brand new documentation and distributions that you can start playing with today. I hadn’t even looked at it to be honest, busy with other stuff, but I had kept my ear out for news and when pluralsight announced a webinar on the topic I thought it was the perfect time to find out more.
This is what I learned:
Angular 2 is in a very early stage of the developer preview, very unstable and it is constantly changing not only in the form and shape of the API but also in its core concepts and naming.
With Angular 2 you get everything you know and love from Angular 1 with a highly improved performance, a simpler mental model with fewer moving pieces and better access to the DOM.
You can build Angular 2 applications in plain ES5 JavaScript but you also have the option to use transpilers and write your angular 2 apps with TypeScript, ES6/ES7 (traceur, babel…), CoffeeScript, etc.
The whole development story changes from using a standard MVC approach to a more componetized development where you have independent components and each has its template and underlying view model (like in aurelia). The components themselves are just ES6 classes that expose APIs to be bound to templates (no more $scope variable).
Angular 2 uses ES7 decorators to provide metadata to your components. They work sort of like attributes in C#. If you use ES5 to write your angular apps there’s alternative APIs to define this metadata. This is an example of a component from Joe Eames’ code sample on GitHub that can give you an idea about how the new component model looks like:
// ES 6 module importsimport{ Component, View, For, If, EventEmitter }from'angular2/angular2'import{ Inject, bind }from'angular2/di'import{ todoItems }from'services/todoItems'// component metadata (element and dependencies to inject)
@Component({
selector:'todo-list',
injectables:[bind('todoItems').toValue(todoItems)],})// view metadata (template and used directives)
@View({
templateUrl:'components/todo-list.html',
directives:[For, If],})// an ES6 classexportclassTodoList{constructor(@Inject('todoItems') todoItems){this.items = todoItems
}setCompleted(item, checked){
item.completed = checked
}completeAll(){var that =thisthis.items.forEach(function(item){
that.setCompleted(item,true)})}removeItem(item){this.items.splice(this.items.indexOf(item),1)}}
There is some interesting new notation for writing bindings within the html templates (*for instead of ng-repeat, *if instead of ng-if, binding with [attribute] and (event):
The IoC story looks like is more explicit and less convention-over-configuration based although I have no clue how it will look in the final version:
// extract from previous example with IoC fragments
@Component({
injectables:[bind('todoItems').toValue(todoItems)]})// an ES6 classexportclassTodoList{constructor(@Inject('todoItems') todoItems){this.items = todoItems;}//...
You can start testing the developer preview by downloading the source code at code.angularjs.org (look for the 2.0.x and alphas). In terms of good editor support, there is sublime text that has great plugins for ES6 and ES7, Web Storm, and even Visual Studio Code or Visual Studio if you want to try Angular 2 with TypeScript.
The Mastering the Arcane Art of JavaScript-mancy series are my humble attempt at bringing my love for JavaScript to all other C# developers that haven’t yet discovered how awesome this language and its whole ecosystem are. These articles are excerpts of the super duper awesome JavaScript-Mancy book a compendium of all things JavaScript for C# developers.
Time for some more useful function patterns in JavaScript!
In this article I’ll show you how to handle multiple parameters - the equivalent to params in C# - in the current version on JavaScript (ES5) and in the upcoming ECMAScript 2015 that brings great support for multiple parameters with the rest parameter syntax.
The Mastering the Arcane Art of JavaScript-mancy series are my humble attempt at bringing my love for JavaScript to all other C# developers that haven’t yet discovered how awesome this language and its whole ecosystem are. These articles are excerpts of the super duper awesome JavaScript-Mancy book a compendium of all things JavaScript for C# developers.
In the next few articles of the javascript-mancy series I will detail several patterns you can use in JavaScript to achieve default arguments, multiple arguments and function overloading.
We’ll start with how to use default arguments and values in JavaScript both with the current version on JavaScript (ES5) and the upcoming ECMAScript 2015 that brings native support for defaults.