-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[Replay] Move rrweb-specific configuration into recordingOptions
#6390
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
Comments
FWIW we changed this in getsentry/sentry-replay#226 -- my reasoning at the time is that from the user's perspective, they shouldn't need to decide what is a "recordingOption" or not. Also in a hypothetical world where we do not use |
I generally agree, and I would advocate to actually make the "main" configuration options explicit on our end - e.g. users could still directly configure I was also thinking about simply naming this
WDYT? |
recordingOptions
rrweb
FYI this issue: #6464 is another, very good, reason to actually do this - we don't want to expose any rrweb-specific types to our users. |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
rrweb
recordingOptions
Closed by #6645 |
Currently, replay is configured like this:
From a code perspective, this happens with a rest operator:
This basically means that any config passed to
new Replay()
that is not defined above will be passed to rrweb.In order to streamline this and make this more explicit, I propose to change this API to:
This would make it much more explicit which options are only related to rrweb.
We can still promote all options we care about/think are important to the top level and internall pass them to
recordingOptions
, e.g.:For now, I propose to add these options to the top level:
ignoreClass: string | string[]
one or multiple classes to ignore. We can internally convert this forignoreClass
blockClass: string | string[]
: one or multiple classes to blockblockSelector: string | string[]
: One or multiple selectors to blockmaskTextClass: string | string[]
: one or multiple classes to mask text forinlineImages
: If true, inline images as data URIsrecordCanvas
: If true, record canvas element contentWhich covers the most relevant stuff, and also the stuff we currently provide default values for.
For the initial release, we can still handle the "old" way of config, warn when we detect "unknown" config, and still make it work. And then remove this deprecated functionality in the near future.
The text was updated successfully, but these errors were encountered: