supabase / supabase-swift / 18411866812

80%

push

github

feat(realtime): add explicit REST API broadcast method (#818)

* fix(realtime): add explicit REST API broadcast method

This commit ports the feature from supabase-js PR #1749 which adds
an explicit `postSend()` method for sending broadcast messages via
REST API, addressing the issue where users may unknowingly use REST
fallback when WebSocket is not connected.

Changes:
- Add `postSend()` method to RealtimeChannelV2 for explicit REST delivery
- Add deprecation warning to `broadcast()` when falling back to REST
- Add comprehensive test coverage for the new method
- Support custom timeout parameter for REST requests
- Include proper error handling and status code validation

The `postSend()` method always uses the REST API endpoint regardless
of WebSocket connection state, making it clear to developers when
they are using REST vs WebSocket delivery.

Ref: https://github.com/supabase/supabase-js/pull/1749

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* refactor: rename postSend to httpSend

Rename the explicit REST API broadcast method from postSend to
httpSend to better align with naming conventions.

Changes:
- Rename postSend() to httpSend() in RealtimeChannelV2
- Update all test names from testPostSend to testHttpSend
- Update deprecation warning to reference httpSend()
- Update error messages to reference httpSend()

All tests continue to pass.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* drop MainActor

* simplify try/catch

* reuse BroadcastMessagePayload

---------

Co-authored-by: Claude <noreply@anthropic.com>

56 of 61 new or added lines in 1 file covered. (91.8%)

5920 of 7647 relevant lines covered (77.42%)

25.09 hits per line