Add option to suppress "preview" event logging #471
Labels
Comments
tonyjin
pushed a commit
to tonyjin/box-content-preview
that referenced
this issue
Feb 5, 2018
Add new Preview option `disableEventLog` to disable the client-side `preview` log to the Events API. Previews with this option enabled will not increment access stats, but all content access is still logged server-side for audit purposes. Resolves box#471.
tonyjin
added a commit
that referenced
this issue
Feb 6, 2018
Add new Preview option `disableEventLog` to disable the client-side `preview` log to the Events API. Previews with this option enabled will not increment access stats, but all content access is still logged server-side for audit purposes. Resolves #471.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's a common use case for platforms and web applications to prefetch/preload data but not have them visible to the user. For example, we want to load multiple
ContentPreviewinstances ahead of time and only log an actual preview event when the user interacts/sees the preview element on the page.For this, we need to actually suppress the current Preview logging that happens out of the box, and talking with Tony, it should be fine since content access is always logged. Furthermore, we'd need a way to log the preview event for the content after user has interacted with it in some way.
The text was updated successfully, but these errors were encountered: