Skip to content

fix(checkout): commerce widget error #2643

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

Merged
merged 2 commits into from
Jun 2, 2025

Conversation

jeetparikh
Copy link
Contributor

Summary

The WALLETCONNECT_PROVIDER_UPDATED event was not being mapped to a commerce connect event throwing an error for an unknown type. This event was not comsumed so dropped this event for commerce widget and the updated provider is available via success event.

@jeetparikh jeetparikh requested a review from a team as a code owner May 30, 2025 06:24
@jeetparikh jeetparikh changed the title fix(checkout) commerce widget error fix(checkout): commerce widget error May 30, 2025
Copy link

nx-cloud bot commented May 30, 2025

View your CI Pipeline Execution ↗ for commit 1293ac4.

Command Status Duration Result
nx run-many -p @imtbl/sdk,@imtbl/checkout-widge... ✅ Succeeded 2s View ↗

☁️ Nx Cloud last updated this comment at 2025-06-01 23:16:02 UTC

@jeetparikh jeetparikh enabled auto-merge June 1, 2025 23:14
@jeetparikh jeetparikh disabled auto-merge June 1, 2025 23:14
@jeetparikh jeetparikh enabled auto-merge June 1, 2025 23:15
@jeetparikh jeetparikh added this pull request to the merge queue Jun 1, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jun 1, 2025
@jeetparikh jeetparikh added this pull request to the merge queue Jun 1, 2025
Merged via the queue into main with commit 18fe545 Jun 2, 2025
10 of 11 checks passed
@jeetparikh jeetparikh deleted the feat/gfi-596-fix-commerce-widget-error branch June 2, 2025 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants