Merge Attributes on Override Attributes and/or Pass User Attributes as Context

[dtothefp]

We have a base set of attributes that are passed to our OptimizelyProvider upon initialization. A common use case is in a hook to pass the overrideAttributes. Generally we would like to have our base attributes merged with the overrideAttributes. It looks like the OptimizelyProvider uses the .setUser method and then in the hook calls .activate with the third argument of the override attributes. I'm under the impression that this will completely override our base set of attributes.

Currently, if we pass overrides we have to access our base attributes from state or context and manually merge them in the hook. I would be nice if they were passed as context and either the hook merges them internally or we can use the Optimizely context to access the base attributes and perform the merge with overrides.

[Tamara-Barum]

Internal ticket: [FSSDK-8652]

[junaed-optimizely]

Hey @dtothefp, it's been a while. I'm going through old issues and found this one. Do you still need it reviewed?

From what I remember, overrideUserAttributes is meant to completely replace the attribute object, not merge it with the base attributes. If a developer wants to merge them, they can.
Also, merging in the SDK layer could introduce new problem, like not being able to unset base attributes.

And its possible to get existing user attributes by doing the following

import { OptimizelyContext } from '@optimizely/react-sdk'

// And then inside the component
const { optimizely }= useContext(OptimizelyContext)
const existingAttr = optimizely?.getUserContext()?.getAttributes() || {}

Let me know if it helps.

[junaed-optimizely]

Closing this due to inactivity! Please feel free to comment / reopen if needed!

Thanks!