It was used in CommitmentManager.to_buy() which gives you a list of purchase requirements.
But the method itself did not work correctly, would be difficult to make work correct (dependent on network facet and pattern configuration), and was painfully slow.
I commented it out, but now (if I deploy my change) people will see a lot of purchase requirements for resources which they do not actually want to purchase.
So we need a new and simpler and faster way to designate resources that are purchased.
It was used in CommitmentManager.to_buy() which gives you a list of purchase requirements. But the method itself did not work correctly, would be difficult to make work correct (dependent on network facet and pattern configuration), and was painfully slow. I commented it out, but now (if I deploy my change) people will see a lot of purchase requirements for resources which they do not actually want to purchase.
So we need a new and simpler and faster way to designate resources that are purchased.