Provide a default SessionId value for Unleash context #119
Comments
|
I believe this is correct, in node we do it here for rollout and here for variants. In Java SDK the stickiness is the same provided from Unleash: https://github.com/Unleash/unleash-client-java/blob/fb576bfd7d68cfd27d4a32109a9735a197659f5b/src/main/java/io/getunleash/variant/Variant.java#L67-L70 and it can be nullable... I wonder if this should be resolved in the backend rather than the frontend. Currently stickiness is not a required field in our response: https://github.com/Unleash/unleash/blob/da05c7be5cefdcc7c8fcfff9d6e7fd8c1a3aa90c/src/lib/openapi/spec/variant-schema.ts#L10 if we have it default to |
|
After a quick chat I think what you want here is a default context value for the session id if none is provided. Updated the title but feel free to correct me if you mean something else. My comment was going a different route, possibly a different issue for our backend. |
Describe the feature request
Stickiness is a core concept in Unleash that deterministically selects the correct variant based on previous input, meaning that if you were already "inside" of a rollout percentage or received a variant, given the same input, you would get the same evaluation result in the next cycle. Stickiness in Unleash defaults to userId or sessionId. If none of these are present it returns a random result.
This SDK does not provide any default settings for sessionId like we introduced in the javascript SDK. This means that if you have rollout based strategies or strategy variants, you might get a different result on each request to the frontend API, resulting in uneccesary 200s and payloads being transmitted over the wire. If no sessionId is provided, we should default it.
Background
No response
Solution suggestions
No response
The text was updated successfully, but these errors were encountered: