Skip to content
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

Expose constant SKIP_TIME_THRESHOLD as skipTimeThreshold in replayer #1408

Merged
merged 2 commits into from
Apr 11, 2024

Conversation

avillegasn
Copy link
Contributor

There is this hardcoded constant SKIP_TIME_THRESHOLD to define the amount of time in milliseconds of an inactive period. By default it is set to 10 seconds, but I believe this should be exposed as a configuration option of the replayer so that users may configure it to fit their needs.

This pull request exposes SKIP_TIME_THRESHOLD as skipTimeThreshold.

Copy link

changeset-bot bot commented Feb 12, 2024

⚠️ No Changeset found

Latest commit: 5cc2515

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

guide.md Outdated
@@ -301,6 +301,7 @@ The replayer accepts options as its constructor's second parameter, and it has t
| root | document.body | the root element of replayer |
| loadTimeout | 0 | timeout of loading remote style sheet |
| skipInactive | false | whether to skip inactive time |
| skipTimeThreshold | 10000 | a threshold of inactive time in milliseconds |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| skipTimeThreshold | 10000 | a threshold of inactive time in milliseconds |
| skipTimeThreshold | 10000 | the threshold in milliseconds for what should be considered an inactive period |

@eoghanmurray
Copy link
Contributor

Thanks for your contribution! I don't use the svelte player but this looks good.

May I suggest a better name for the config setting?

Maybe minInactivePeriod or inactivePeriodThreshold rather than skipTimeThreshold?

@avillegasn
Copy link
Contributor Author

Thanks for your contribution! I don't use the svelte player but this looks good.

May I suggest a better name for the config setting?

Maybe minInactivePeriod or inactivePeriodThreshold rather than skipTimeThreshold?

I did the change to inactivePeriodThreshold.

@eoghanmurray eoghanmurray merged commit 729361e into rrweb-io:master Apr 11, 2024
5 of 6 checks passed
@avillegasn avillegasn deleted the expose-skip-time-threshold branch April 11, 2024 10:20
eoghanmurray added a commit to eoghanmurray/rrweb that referenced this pull request Apr 17, 2024
billyvg pushed a commit to getsentry/rrweb that referenced this pull request Apr 25, 2024
…layer (rrweb-io#1408)

Expose constant SKIP_TIME_THRESHOLD as `inactivePeriodThreshold` config setting in replayer
billyvg pushed a commit to getsentry/rrweb that referenced this pull request Apr 25, 2024
…layer (rrweb-io#1408)

Expose constant SKIP_TIME_THRESHOLD as `inactivePeriodThreshold` config setting in replayer
jaj1014 pushed a commit to pendo-io/rrweb that referenced this pull request Apr 30, 2024
…layer (rrweb-io#1408)

Expose constant SKIP_TIME_THRESHOLD as `inactivePeriodThreshold` config setting in replayer
jaj1014 pushed a commit to pendo-io/rrweb that referenced this pull request Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants