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

add post to conversation flow operator #2487

Merged
merged 12 commits into from
Dec 16, 2019
Merged

Conversation

blizzz
Copy link
Member

@blizzz blizzz commented Nov 22, 2019

for #2414

fyi @juliushaertl @nickvergessen

lib/Flow/Operation.php Outdated Show resolved Hide resolved
lib/Flow/Operation.php Outdated Show resolved Hide resolved
try {
$participant = $this->getParticipant($room);
if (!$participant->hasModeratorPermissions(false)) {
throw new UnexpectedValueException('Not allowed to mention room');
Copy link
Member

Choose a reason for hiding this comment

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

Is this intended? we do not limit mentions of the "conversation" to moderators

Copy link
Member Author

Choose a reason for hiding this comment

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

We agreed that we do not want a person be able to spam others with mentions. Now I had the idea that some trusted individuals it might be allowed to trigger mentions to a crowd, and in Talk they would be identified by Moderators. If it does not make sense, we can kill it. Or extend/relax it later.

src/PostToConversation.vue Outdated Show resolved Hide resolved
src/PostToConversation.vue Outdated Show resolved Hide resolved
src/PostToConversation.vue Outdated Show resolved Hide resolved
this.fetchRooms()
},
methods: {
fetchRooms() {
Copy link
Member

Choose a reason for hiding this comment

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

There is a RoomSelector.vue available for the projects stuff. Would it make sense to reuse?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll have a look, thx for the pointer

Copy link
Member Author

Choose a reason for hiding this comment

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

Only with refactoring the RoomSelector as it brings a hard model with it. I'd refrain of it for now.

src/flow.js Outdated Show resolved Hide resolved
@blizzz blizzz requested a review from nickvergessen November 27, 2019 16:23
Signed-off-by: Arthur Schiwon <[email protected]>
Signed-off-by: Arthur Schiwon <[email protected]>
Signed-off-by: Arthur Schiwon <[email protected]>
Signed-off-by: Arthur Schiwon <[email protected]>
because the logged in user might not be the one who set up the flow, e.g.
a share recipient

Signed-off-by: Arthur Schiwon <[email protected]>
Signed-off-by: Arthur Schiwon <[email protected]>
Signed-off-by: Arthur Schiwon <[email protected]>
Copy link
Member

@nickvergessen nickvergessen left a comment

Choose a reason for hiding this comment

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

Works 🐘

@nickvergessen nickvergessen merged commit 32049dc into master Dec 16, 2019
@nickvergessen nickvergessen deleted the enh/2414/flow-operator branch December 16, 2019 14:24
@blizzz blizzz mentioned this pull request Dec 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants