We have a developer tool that helps us view and override Split in our product, both for testing and for internal use and demo purposes. I noticed defaultTreatment is something that is sent down to the javascript-client, but it not exposed anywhere externally. It would be helpful if we could show this defaultTreatment value, so that Split is the one "source of truth" and we do not need to do something such as create our own default values in our devtool.

I have a fork of this where I tested it out and would be happy to open a PR, but I also wanted to open a thread in case the fact that I would find this property helpful is indicative of us using this tool or understanding this property's purpose incorrectly.

Proposed changes:

• Add defaultTreatment to the SplitView type
• Update sdkManager/index.ts's internal objectToView() to include returning defaultTreatment property

When running in localhost mode, the impressions cache seems to grow unboundedly, as the following condition never triggers: https://github.com/splitio/javascript-commons/blob/development/src/storages/inMemory/ImpressionsCacheInMemory.ts#L31 because onFullQueue is never set.

I was pointed there by heap profiler, as I was investigating an out of memory error in a development pipeline with a long-running analysis task (which uses split in localhost mode).

Do y'all have any plans to support Redis in cluster mode?

The fact that it does or doesn't support it doesn't appear to be documented anywhere, and the Redis configuration documentation uses the word cluster, so the assumption was made...

Symptom:

1. Everything comes back as "control"
2. Digging further: if we were to add a log here we would see that every single request comes back as MOVED, meaning the root node is trying to do load balancing
   • Side note: it sure would be great if there were a log or something there. It sure is frustrating having to debug this thing in tsc-generated code, and figuring out what's wrong took over a dozen hours of deconstructing this thing. ioredis uses debug. It might be nice if you used the same, but no pressure :)

Root Cause:

Apparently the RedisAdapater always extends ioredis and doesn't have any support for ioredis.Cluster, which is what is required.