ref(browser): Create standalone INP spans via startInactiveSpan
#11788
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.
builds on top of #11696 #11699
This PR refactors how we create INP spans. Previously we'd directly initialize a
SentrySpan
instance with the necessary properties and manually sample the span. Ironically, we heavily discourage directly initializing aSpan
class.With this refactor PR, we leverage the
standalone: true
flag introduced in #11696. This way, we can also use the built-in sampling functionality and ensure that we only have one logic for creating standalone span envelopes. Also bundle size should decrease slightly 🤞Adjusted the integration tests to more thoroughly test the INP span envelopes