Closed alexcouper closed 9 years ago
In order to do this, I will be stripping out all notion of hierarchy and feature from the recalculate method.
Since recalculate lives in a module called "hierarchy", I think what I shall do is create a new method + module that the hook will currently use which is essentially to store the branch information so we can display and search based on it.
Yes that is the way forward.
A new method update_branch_info
or suchlike.
Recalculate method only stores branches of interest based on features that are defined. This is not what we want.
From @txels in #76:
We should create/update branch data on every hook receipt.