Ilija Pavlic

@sirLisko Yes, that's why the commit message says "at the expense of `$element` injection"

The way it's implemented now, it's clearly wrong. Suppose your template contains a directive `foo` which uses an input value from the controller ``. Currently, the directive's controller is constructed...

@dwmkerr I've checked what tests are broken, and it's just the single test that explicitly checks whether the `$element` is injected. So this can be fixed by giving up the...

@dwmkerr Any news on that one?

That's basically the same issue as #71, and it's quite frustrating.

Your proposal sounds reasonable. I haven't had much free time lately to do it myself, but feel free to submit a pull request.

### What you can do Invest into your fixed amount of non-prod infrastructure.

No, it's not supposed to be like that. Commit https://github.com/RyanMullins/angular-hammer/commit/ff754eefb189c10b621465df03d0a6a5f423917f contains a fix for Browserify, but it was merged two weeks after the latest release. @RyanMullins Could 2.2.0 be released?

Without seeing more of the graph, it seems that they were balanced against all other nodes. Perhaps increasing edge weights with the tree depth would force the layout you are...

One might argue that the top most node "should be" in the center, and that you should get a perfect tree layout which seems to be what you are looking...