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

feat: migration to rum v2 #76

Merged
merged 7 commits into from
Jul 16, 2024
Merged

feat: migration to rum v2 #76

merged 7 commits into from
Jul 16, 2024

Conversation

kptdobe
Copy link
Contributor

@kptdobe kptdobe commented Jun 19, 2024

Use rum v2 and optimise rum loading sequence using manual enhance method - depends on adobe/helix-rum-js#175

This introduces a new custom event: hlx:section:loaded which fires when a section is loaded.

When first section is loaded, we "enhance" the rum sampling.

@kptdobe
Copy link
Contributor Author

kptdobe commented Jul 10, 2024

@davidnuescheler and I came to the conclusion we do not need a custom event, at least for now. The only consumer would be our boilerplate, for which we know exactly when to call sample.enhance(). No need to create a custom event that we'll have to maintain for a single usage.
I'll change the implementation.

@kptdobe kptdobe merged commit 7ebf186 into main Jul 16, 2024
4 checks passed
@kptdobe kptdobe deleted the rum-js-v2 branch July 16, 2024 12:30
adobe-bot pushed a commit that referenced this pull request Jul 16, 2024
# [2.5.0](v2.4.0...v2.5.0) (2024-07-16)

### Features

* migration to rum v2 ([#76](#76)) ([7ebf186](7ebf186))
@adobe-bot
Copy link

🎉 This PR is included in version 2.5.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants