You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[wrangler] Fix self-bindings showing as not connected in dev (#10915)
* fix: self-bindings show as connected in wrangler dev
Fixes#8970
Self-bindings (service bindings where a worker binds to itself) were
incorrectly showing as [not connected] in wrangler dev. This change
detects self-bindings by comparing the service name to the worker name
and always marks them as connected, since a worker is inherently
connected to itself.
- Modified print-bindings.ts to check for self-bindings before registry lookup
- Added test for self-bindings showing as [connected]
- Manually verified with workers-with-assets fixture
Co-Authored-By: smacleod@cloudflare.com <smacleod@cloudflare.com>
* fix: correct test snapshot for self-bindings table formatting
The table column widths are dynamically calculated based on content
length. The self-bindings test has longer binding names than other
service binding tests, which causes wider column spacing in the output.
Updated the snapshot to match the actual table formatting.
Co-Authored-By: smacleod@cloudflare.com <smacleod@cloudflare.com>
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: smacleod@cloudflare.com <smacleod@cloudflare.com>
Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself.
0 commit comments