-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FSSDK-11128] update decision service and impression event for CMAB #1021
base: master
Are you sure you want to change the base?
Conversation
474b836
to
d966df0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! A couple of suggestions.
One thing we should consider is to split cmab changes into a separate PR (excluding UPSasync and related changes not relevant to CMAB and other SDKs), which will make it much easier to follow the reference.
variation = variationId ? configObj.variationIdMap[variationId] : null; | ||
if (!variation) { | ||
this.logger?.debug( | ||
USER_HAS_NO_VARIATION, | ||
userId, | ||
experimentKey, | ||
); | ||
decideReasons.push([ | ||
USER_HAS_NO_VARIATION, | ||
userId, | ||
experimentKey, | ||
]); | ||
return Value.of(op, { | ||
result: {}, | ||
reasons: decideReasons, | ||
}); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this variationId-exist checking is for CMAB only, what about moving this check to CMAM decision?
reasons: decideReasons, | ||
}; | ||
const cmabPromise = this.cmabService.getDecision(configObj, user, experiment.id, decideOptions).then( | ||
(cmabDecision) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can move the variation validate stuff above to here?
Summary
Test plan
Issues