We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bringing this to the attention, as it will likely disappear in the void otherwise: https://github.com/orgs/supabase/discussions/30361
How can one implement a custom transport when setupConnection is not run against it from the RealtimeClient?
The text was updated successfully, but these errors were encountered:
We have patched realtime-js on our end and added the missing setupConnection line. Everything seems to be working well.
setupConnection
I presume it's just an oversight/bug, because otherwise one would have to reimplement the whole realtmeclient in order to use a custom transport.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Bug report
Describe the bug
Bringing this to the attention, as it will likely disappear in the void otherwise: https://github.com/orgs/supabase/discussions/30361
How can one implement a custom transport when setupConnection is not run against it from the RealtimeClient?
The text was updated successfully, but these errors were encountered: