-
Notifications
You must be signed in to change notification settings - Fork 3
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
[WIP]Request access to join private channels. #443
Conversation
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.
From a user's perspective:
- I expected private rooms next to channels (second tab)
- The information about secret private channels should only be there in the private groups
I'll keep on reviewing, but it looks really promising
@@ -42,9 +42,9 @@ RocketChat.createRoom = function(type, name, owner, members, readOnly, extraData | |||
sysMes: readOnly !== true | |||
}); | |||
|
|||
if (type === 'd') { | |||
/* if (type === 'd') { |
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 has this been commented?
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 are some more kind-of-minor items pending, see above and below. But I believe most of them to be quite minor. Good job!
message: 'Room_join_request_accepted', | ||
data(message) { | ||
const room = message.room; | ||
Template.room.events({ |
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.
This adds a (global) event to the room-template - every time a join-request is being rendered. Should/could this not been done statically (as part of the rooms template, ideally)?
@@ -164,6 +170,9 @@ Template.createChannel.events({ | |||
}, | |||
'change [name="type"]'(e, t) { | |||
t.type.set(e.target.checked ? e.target.value : 'd'); | |||
if (!e.target.check) { |
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.
How does this reflect the comment? I don't see a validation with respect to public channels only. And afterall: should this not be checked
?
tests/chimp-config.js
Outdated
@@ -19,7 +19,7 @@ module.exports = { | |||
// showXolvioMessages: true, | |||
|
|||
// // - - - - CUCUMBER - - - - | |||
path: 'tests/end-to-end', | |||
path: 'tests/end-to-end/ui_dummy', |
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.
see the comments above.
We should at least make sure an previously removed user has the option to request access to a channel again.
In general the German translations should be checked.
@vickyokrm with 0.69, there is a new API in RC which renders buttons: |
* Added text and image buttons Added image button with msg Fixed according to updated JSON Added horizontal buttons support Fixed indentation Added text and image buttons * Added image button with msg * Fixed according to updated JSON * Added horizontal buttons support * fix style logic * Fixed lint errors and merge conflict * Remove lint errors * Added Actions schema to tests
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 looks really good to me! Since it's quite an extensive PR which will result in a lot of merge conflicts in future, I'd like to get some feedback from Rocket.Chat prior to merging it though.
} else { | ||
delete record.$loki; // TODO: Why loki used here |
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 did you remove it? Did that cause issues?
What is keeping us away merging this PR? |
21968f1
to
071d72e
Compare
Unfortunately, we didn't push this to a core PR. We'll not enlarge our diff, so if we should need this again, we'll keep this closed PR as reference |
Private Groups
Secrecy
to the private channels.