-
Notifications
You must be signed in to change notification settings - Fork 197
fix: lazy replay received flag tracking should be in the wrapper #2405
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
7 files reviewed, 2 comments
|
Size Change: +1.26 kB (+0.02%) Total Size: 5.11 MB
ℹ️ View Unchanged
|
| const persistResponse = () => { | ||
| const sessionRecordingConfigResponse = response.sessionRecording | ||
| const sessionRecordingConfigResponse = | ||
| response.sessionRecording === false ? undefined : response.sessionRecording |
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.
wild that we've never represented that sessionRecording can be false
it's "safe" to just treat it as undefined when false
lifting changes out of #2404
i want to make as many changes as possible before removing the lazy loaded code so i have a chance to back out of i need to
we're tracking received flag in the lazy loaded code, but not using it
and types are wrong... sessionRecording can be false but we don't represent that