Skip to content

Conversation

@apankov1
Copy link

Summary

  • Convert Actor.configuration into a real static method so subclasses can reliably override socket settings, and make fetch/getActor pull config from the subclass constructor.
  • Add a regression test confirming a custom upgradePath triggers onWebSocketUpgrade and that /ws still falls through to the HTTP handler.

Testing

  • npm run test --workspace packages/core
  • Validated end-to-end in the project where misrouted WebSocket upgrades originally surfaced.

Code in this PR was AI-assisted and exercised against the pet project that experienced the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant