Elliott Dicus

That makes sense. However, I'd like to be able to show a visualization for any arbitrary node. Short of adding a fixed length buffer back into every node purely for...

Okay, thanks. I'll give that a shot. I'd like to switch to single-sample so that I can use the FFT stuff when that's all wrapped up, I just can't lose...

I forked and added a buffer for visualization to each node. You can look at the specifics here: https://github.com/ewdicus/Audiolet. Then I'm plotting it using Canvas and Javascript.

I should clarify, I haven't updated the examples there. I've just made the changes to the code. If you need help figuring it out, let me know.

Hi @EmilianoSanchez, Thanks for the quick response! Setting `updateOnSdkUpdate` on the client does change that to the previous behavior. However, I also have to set it on calls to `useSplitTreatments`....

@EmilianoSanchez I appreciate the extra information. For context we have exactly the situation indicated here (https://help.split.io/hc/en-us/articles/360046771911-React-SDK-Lazy-initialization-of-Split-client) where we don't know the user id when the factory is constructed. Is there...

Ok great! 🙌🏻 We have several places in the app where we use useSplitTreatments, and we'd like to prevent prop-drilling the userId to all those call sites. Is there a...