The ValueNode class does not have an "onSet" callback. While the onValueChange callback gives the ability to track node value changes, you cannot distinguish between @set methods from a requester and node value updates locally. The .setValue function also triggers the onValueChange, therefore the ValueNode doesn't give the programmer the ability to distinguish between local changes the upstream changes. This pushes the programmer to use invoke functions to produce a logical flow of information rather than using @set in cases where it makes more sense.
The ValueNode class does not have an "onSet" callback. While the onValueChange callback gives the ability to track node value changes, you cannot distinguish between @set methods from a requester and node value updates locally. The .setValue function also triggers the onValueChange, therefore the ValueNode doesn't give the programmer the ability to distinguish between local changes the upstream changes. This pushes the programmer to use invoke functions to produce a logical flow of information rather than using @set in cases where it makes more sense.