Closed wizardlyhel closed 2 weeks ago
Oxygen deployed a preview of your hl-update-analytics-components branch. Details: |
Storefront | Status | Preview link | Deployment details | Last update (UTC) |
---|---|---|---|---|---|
vite | ✅ Successful (Logs) | Preview deployment | Inspect deployment | May 2, 2024 9:15 PM | |
third-party-queries-caching | ✅ Successful (Logs) | Preview deployment | Inspect deployment | May 2, 2024 9:15 PM | |
skeleton | ✅ Successful (Logs) | Preview deployment | Inspect deployment | May 2, 2024 9:15 PM | |
optimistic-cart-ui | ✅ Successful (Logs) | Preview deployment | Inspect deployment | May 2, 2024 9:15 PM | |
subscriptions | ✅ Successful (Logs) | Preview deployment | Inspect deployment | May 2, 2024 9:15 PM | |
custom-cart-method | ✅ Successful (Logs) | Preview deployment | Inspect deployment | May 2, 2024 9:15 PM |
Learn more about Hydrogen's GitHub integration.
Fixes #0000 👯
We detected some changes in packages/*/package.json
or packages/*/src
, and there are no updates in the .changeset
.
If the changes are user-facing and should cause a version bump, run npm run changeset add
to track your changes and include them in the next release CHANGELOG.
If you are making simple updates to examples or documentation, you do not need to add a changeset.
WHY are these changes introduced?
<Analytics.Provider>
will not send any events.consent.checkoutDomain
andconsent.storefrontAccessToken
is requiredIntroduce
onReady
callback foruseCustomerPrivacy
hook.WHAT is this pull request doing?
HOW to test your changes?
Use
analytics
example:consent.checkoutDomain
from root loader --> site should generate error about missing propsconsent.storefrontAccessToken
from root loader --> site should generate error about missing propsconsent.withPrivacybanner: false
in the root loader --> You should seeCustomAnalytics
logging page views in the console logPost-merge steps
Checklist