#ember1.13

[pterofaur]

Developer Diary Week 51

Doings:

Ember 1.13 upgrade all day every day

Thoughts:

Feel a lot more confident with the new Ember workflow

I now hate the observers with a passion

I have reassessed how computed properties should work. There really shouldn't be multiple computed properties that recompute on the same property. Otherwise you run into weird race conditions if you have complex interactions.

[pterofaur]

Developer Diary Week 43

Doings:

Rails Girls mentoring

Ember 1.13 migration

Hating generating xlsx

Built a Ember 2.0 ready drag and drop prototype for giggles and edification

Thoughts:

Shout out to my incredible mentees at Rails Girls, the future is in good hands. Teaching is pretty tough. I'm going to work on explaining stuff. "They don't think it be like it is, but it do", thats what I sounded like explaining MVC. I promise I know what I'm talking about.

Ember 2.0 is a pretty cool guy, that doesn't afraid of anything. I'm starting to embrace data down actions up wholeheartedly now that I've used the new action currying. Some weirdness in the component life cycle hooks though.

[pterofaur]

Ember 1.12 to 1.13 Part 1

Introduction:

We are moving to 1.13 for Ember and bring some snacks because its going to be a long ride.

Lifecycle hooks:

Model hook in route - I haven't confirmed this behaviour I will ask on the official repository if this intended but now if you don't explicitly declare the model hook in a route, it returns a params object on hard load of the URL whereas previously you would have a model from a parent route.

Components - I have rewritten the base select component using the examples on the Ember docs with two way binding to provide drop in replacements for {{view "select"}}. The new component React-ish life cycle hooks are pretty cool but some of the use cases are still unknown to me.

One our components, a td in a table that communicates with a graph above and highlights when the mouse is over the data point in the table, rerenders a lot. This is because rerenders are now fired on any attribute change. I thought rerenders would be cheap. But this table seems to be performing badly so we will need to investigate.

I had a discussion with my CTO about the merits of two way data binding. I have come to the conclusion that sometimes its ok. If you have a form that is bound directly to data that seems reasonable and avoids propagating a bunch of unnecessary actions. I do like the new way of passing actions and contexts down into components.