fix: squash down recorder size a little #1064
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This didn't have as big an impact as I'd hoped, but we can use the absence of initiator type allowlist to mean allow all, and keep an empty array meaning allow none. Which means we don't need to have a list of unminifiable strings in the bundle.
And since we have multiple no-op functions in the recorder we can share them to save a few more bytes
tested by running recording locally with payload capture on and off