Right now, finders keep a track of their own jobId, which is then set on the nodes.
If you want to alternately use finders on a graph it could generate incorrect paths (or not find them at all) due to skipping some nodes, assuming they were already evaluated.
Node's job should be store per type / category, meaning each node should be able to have more than one jobId at the same time.
xaguzman
commented
9 years ago
Right now, finders keep a track of their own jobId, which is then set on the nodes. If you want to alternately use finders on a graph it could generate incorrect paths (or not find them at all) due to skipping some nodes, assuming they were already evaluated.
Node's job should be store per type / category, meaning each node should be able to have more than one jobId at the same time.