Ember Closure Actions

Brief history of passing actions in components

The ability to pass actions to components is not a new feature for component use. The previous action system used bubbling to pass user behavior to a parent scope. For example, a user clicks a button within a component, this then triggers an action which bubbles through several controllers to finally be handled on a route. This way of bubbling actions was challenging to debug and required a good amount of boilerplate code. Looking forward, Ember was geared to become more component-driven and delivered a cleaner and more flexible way to pass functions with the Ember 1.13.0 Closure Actions.

Continue reading »

A Year-ish in Ember

According to commit logs, it’s been around 10 months since the team first began fiddling with Ember JS, a Javascript framework for web applications. I bought a copy of Rock and Roll with Ember JS 2 months prior, to begin getting a hang of it, and so a year later, these are my thoughts on the framework.

Continue reading »

What's Lurking In Your Code

Have you ever been working on a feature and come to a point where you just feel barricaded in on all sides? This recently happened to me. Trying to force the implementation with the current structure of our schema felt dirty. The code I was writing became increasingly hard to follow. Not to mention, if and when a bug were to rear its ugly head, how difficult solving this conglomerate hodgepodge of spaghetti code would be. We needed to restructure parts of our schema with the added complexity of zero downtime to our production environment.

Continue reading »

One SPA to rule them all

This is part 2 of the series about scaleable architecture for SPAs. Part 1 discussed the benefits of SPAs. But what if you are building a multi-product solution with a large development team? This post will compare a single-SPA architecture with a multiple-SPA approach.

Continue reading »