-
-
Notifications
You must be signed in to change notification settings - Fork 833
Allow setting knock room visibility #11464
Allow setting knock room visibility #11464
Conversation
Signed-off-by: Charly Nguyen <[email protected]>
cae8b82
to
798f13a
Compare
FYI @daniellekirkwood 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your contribution @charlynguyen . Please have a look at my comments:
We are using switches in most places. Can you replace the checkboxes with switches? Otherwise the UI would be (more) inconsistent. Update: Looks like design suggests it this way.
switch | checkbox |
---|---|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some additional thoughts from me:
- This feels like three separate changes, which are only very tangentially related. I think it would be easier to review and merge if split into separate PRs.
- We already have a switch to control whether a room is in the public room directory (on the "General" tab) - I think adding a second control on another tab will be confusing.
@@ -298,6 +304,18 @@ export default class CreateRoomDialog extends React.Component<IProps, IState> { | |||
); | |||
} | |||
|
|||
let visibilitySection: JSX.Element | undefined; | |||
if (this.state.joinRule === JoinRule.Knock) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we only expose this control for knockable rooms? Isn't it relevant to other rooms too?
@@ -215,6 +217,10 @@ export default class CreateRoomDialog extends React.Component<IProps, IState> { | |||
return result; | |||
}; | |||
|
|||
private onIsPublicChange = (isPublic: boolean): void => { | |||
this.setState({ isPublic }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was also my conclusion. So, I decided to give it a purpose.
I've checked the designs. This is how they suggested it. Doesn't mean we shouldn't open this up for discussion. |
yeah... I'd like to understand the reasoning behind that decision. Duplicating the setting, but only for knockable rooms, seems confusing to me. |
I agree with this:
However, the switch being "point of need" at the "ask to join" part of settings makes sense to me. If we want to remove it from General, then maybe we explore that. Having discussed the "Compoundifying" of Knocking with @nadonomy this morning we've agreed that it's not on our critical path and we're happy with the team at Nordeck to push forwards with the Knocking designs that we have provided them - then agreeing that when we get to Settings in the Compound project (Q4/Q1) we will review all the switches, toggles, pages and repeated info hollistically and remove them later. |
@daniellekirkwood can you just confirm my understanding on a few points:
|
I'm happy for this PR to use the method that's been shared in the designs. Esp. knowing that it's likely we'll update it in the next 12 months as part of the compound project. Unless @nadonomy has a big blocker here.
Not happy but believe it's a temporary necessity as we don't have the answer to where it should like (nor the time/bandwidth to find the answer). The two switches should be linked though - if one is on, the other should reflect that state and vice versa.
Good point -- when someone selects Public it doesn't necessarily add it to the directory, right? Maybe this checkbox should appear there also... @nadonomy i would like support on that question... |
That was also my impression during the implementation, but I decided to stick to the screens. |
It seems like this does match the intentions from the design team, but I'd still rather see it land as three separate pull requests rather than a single one. @charlynguyen would you mind breaking it up? |
That is totally fine by me 🙂 |
We @nordeck are currently implementing the knock rooms behind the feature flag
feature_ask_to_join
(introduced in #11182).This pull request allows setting knock room visibility.
Epic: element-hq/element-web#18655
Is blocked byAddjoin_rule
field to /publicRooms response matrix-js-sdk#3673Relates to
Screens / Videos
CreateRoomDialog
JoinRuleSettings
SpotlightDialog
Checklist
Here's what your changelog entry will look like:
✨ Features