-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(replay): Allow to configure maxReplayDuration
#8769
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
Conversation
8cc5a7f
to
6363e66
Compare
size-limit report 📦
|
@@ -148,7 +147,6 @@ export class ReplayContainer implements ReplayContainerInterface { | |||
this.timeouts = { | |||
sessionIdlePause: SESSION_IDLE_PAUSE_DURATION, | |||
sessionIdleExpire: SESSION_IDLE_EXPIRE_DURATION, | |||
maxSessionLife: MAX_SESSION_LIFE, |
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.
Why not keep the max duration part of timeouts?
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.
🤷 just aligning this - the only reason these timeouts
exist was to allow overwriting them in tests, which can now be done "correctly"/publicly via maxReplayDuration
?
6363e66
to
ed1ac3b
Compare
note: I rebased on develop, fixing inconsistencies. |
cc1a468
to
7f6fbad
Compare
7f6fbad
to
db0d4f6
Compare
This defaults to 60min, and is capped at max. 60min (=you cannot specify a longer max duration than 60min).
db0d4f6
to
8f62064
Compare
This defaults to 60min, and is capped at max. 60min (=you cannot specify a longer max duration than 60min).
Closes #8758