Skip to content
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

feat: check for private key on public Channel and error #1125

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

chasers
Copy link
Contributor

@chasers chasers commented Aug 7, 2024

As a developer, if I want to ensure my private messages are sent on a private Channel I can include a private key with value true.

If a message with a private key of value true is sent on a public Channel, the Realtime server will error and close the socket.

Copy link

vercel bot commented Aug 7, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
realtime-demo ⬜️ Ignored (Inspect) Visit Preview Dec 18, 2024 0:26am

@chasers chasers marked this pull request as ready for review August 8, 2024 22:52
@chasers chasers requested review from filipecabaco and w3b6x9 August 8, 2024 22:52
@chasers
Copy link
Contributor Author

chasers commented Aug 9, 2024

Inspector is now compatible with private Channels and messages.
Screenshot 2024-08-08 at 5 04 00 PM
Screenshot 2024-08-08 at 5 03 53 PM

@filipecabaco filipecabaco force-pushed the feat/require-private-key-private-channel branch from bfa8e6e to 47953d1 Compare October 29, 2024 11:51
@filipecabaco filipecabaco force-pushed the feat/require-private-key-private-channel branch from 47953d1 to af73a79 Compare December 18, 2024 12:26
@filipecabaco
Copy link
Contributor

rebased the PR against main

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.

2 participants