As programmers, one of the most important skills to have is being able to learn quickly. It doesn’t
matter that you know frameworks X and Y, or languages Foo and Bar. what’s hot and what’s not will change
several times throughout our career, but the skill to learn new abilities will always be in demand.
In this post I want to explore the idea of using contexts in React to
implement dependency injection (DI)
in our application.
If you have not been developing using Flux yet I would strongly urge you to check it out.
In this post, I want to explore a different approach to writing directives in
Angular 1. As we know, building applications in Angular 2 is going to be
different from what we’re used to in Angular 1. For example,
be gone, and components will be the building blocks of applications.
In Angular 1, directives are a way for developers to extend HTML. This means
introducing new behaviours to the DOM via custom tags or attributes. You can
change what a directive matches by using the
restrict option. By default it
is set to
'EA', meaning it works on elements (tags) and attributes.
There’s been a lot of discussion on what Flux is, the different variations, and
how the pattern can be improved upon. I’ve even blogged about Flux
here on this blog!
Flux is an application
first introduced by Facebook in May 2014, and it has since
them and many ways to invoke them. Throw in
this, and things really starts to
Angular 1.3.0 (superluminal-fudge) has been released!
In a previous post, I presented a framework on top
of AngularJS 1.2 to handle asynchronous form validations and error message display concerns. This has been made
much easier in AngularJS 1.3!
One of the new features coming to ECMAScript 6 (ES6), the next version of
template strings are creating multiline strings, and doing string interpolation.