Remove double pass over of graph reactivity

[MayaGans]

Thanks so much for your note yesterday. I was wondering if we could discuss the issue you mentioned in a bit more detail? I've used reactlog for very simple apps but there are a lot of moving parts here.

Do you mind expanding on what you meant by a double pass of the graph - I'm trying to isolate this and find the "culprit" node responsible for this.

Thank you!!

[dgkf]

Apologies for the loooong delay. I somehow missed this notification and only stumbled upon it when trying to add in some issues for Hacktoberfest.

This module has a long chain of reactivity, linking each individual filter to its upstream data source (the source dataset for the first filter, or the preceding filter for subsequent filters). When an upstream filter is modified by subsetting a field, you might have noticed that the downstream elements will refresh twice. This is because something in the downstream filters is causing the upstream filters to be recalculated, triggering a second pass over the reactive chain. Thankfully it seems to limit itself to only two passes, avoiding an infinite reactive loop, but it would be even better if we avoided that second cycle altogether.

If possible, I'd like to avoid this re-triggering since it seems it shouldn't be necessary and results in some jankiness in the rendering with the downstream elements switching rapidly between active and re-calculating (gray-ed out).

[manpil]

@dgkf Hi, I stumbled upon the same issue and wasn't able to fix it yet. Do you have any news on the problem?

[dgkf]

Hi @manpil - always glad to hear from people who have stumbled upon this package.

You're right to identify this as an issue - it's not something I ever got around to fixing up. At the moment, this isn't a priority project for me, but I would totally welcome a PR to get it sorted out.

[manpil]

@dgkf I understand. If I find the issue I will of course PR it. However, I am not sure myself if I have the time to come up with a fix.