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

chat: reword CHA-PR9 points #243

Merged
merged 1 commit into from
Nov 25, 2024
Merged

chat: reword CHA-PR9 points #243

merged 1 commit into from
Nov 25, 2024

Conversation

AndyTWF
Copy link
Contributor

@AndyTWF AndyTWF commented Nov 25, 2024

Reworded for clarity and to match JS implementation.

Closes #236

Reworded for clarity and to match JS implementation.

Closes #236
Copy link
Collaborator

@lawrence-forooghian lawrence-forooghian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@AndyTWF AndyTWF merged commit e843b1d into main Nov 25, 2024
2 checks passed
@AndyTWF AndyTWF deleted the chat-presence-clarifications branch November 25, 2024 19:01
@@ -391,8 +391,8 @@ Presence allows chat room users to indicate to others that they're online, as we
** @(CHA-PR7c)@ @[Testable]@ A subscription to presence may be removed, after which it shall receive no further events.
* @(CHA-PR8)@ @[Testable]@ Users may subscribe to discontinuity events to know when there's been a break in presence. Their listener will be called when a discontinuity event is triggered from the room lifecycle. For presence, there shouldn't need to be user action as the underlying core SDK will heal the presence set.
* @(CHA-PR9)@ Users may configure their presence options via the @RoomOptions@ provided at room configuration time.
** @(CHA-PR9a)@ @[Testable]@ Setting @enter@ to false prevents the user from entering presence by means of the @ChannelMode@ on the underlying realtime channel. Entering presence will result in an error. The default is true.
** @(CHA-PR9b)@ @[Testable]@ Setting @subscribe@ to false prevents the user from subscribing to presence by means of the @ChannelMode@ on the underlying realtime channel. This does not prevent them from receiving their own presence messages, but they will not receive them from others. The default is true.
** @(CHA-PR9a)@ @[Testable]@ If @enter@ is set to true (or left unspecified), then the presence feature must set the @PRESENCE@ mode on the underlying Realtime channel.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or left unspecified means it's set to false right?

Copy link
Collaborator

@sacOO7 sacOO7 Nov 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, any combination of enter and subscribe is permitted right? I mean do need to have validation like we do for negative typing timeout

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In JS, it's if you leave it as undefined - at which point it takes the default value.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, any combination of enter and subscribe is permitted right? I mean do need to have validation for the same like we do in case of negative typing timeout

Any combination is permitted, yes.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

default is true for both right

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes - for some reason my IDE didn't commit the line where I added "default is true" will do that as a separate PR now.

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

Successfully merging this pull request may close these issues.

Chat spec points about preventing presence are unclear
3 participants