Add exposureHook for control over exposure logging #42
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows us to decouple evaluation from exposure logging. We can check local or distributed caches if we've already reported this exposure. Work-in-progress - I imagine Statsig would like to retain control over the de-duplication logic. Possibly, the hook can accept a dedupe key instead/additionally.
EddShaw
commented
Jan 14, 2026
EddShaw
commented
Jan 14, 2026
| } | ||
|
|
||
| // Logs an exposure event for the dynamic config | ||
| func (c *Client) LogExposureEvent(event ExposureEvent) { |
Author
There was a problem hiding this comment.
LogExposureEvent allows us to report an exposure after checking our de-duplication cache.
❔ Should we expose a Immediately variant of this? I don't think that's necessary for our use-case.
EddShaw
commented
Jan 14, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows us to decouple evaluation from exposure logging. We can check local or distributed caches if we've already reported this exposure, without blocking the gate/experiment evaluation.
One issue with this PR I already foresee: I imagine Statsig would like to retain control over the de-duplication logic. Possibly, the hook could accept a dedupe key additionally? (I hadn't spotted that we already have a method for deriving a dedupe key in the SDK when I initially implemented this. 🙈)
I don't expect this PR to merge (at least, as is). Mostly, I'm hoping to open the conversation about how Statsig might support the eval/exposure logging decoupling (ideally, with some supported wire format for the exposure itself).
(Experiments/Layers haven't had the equivalent changes made to them yet - but I can come back and update those if Statsig are keen.)