-
Notifications
You must be signed in to change notification settings - Fork 437
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(conversations): add option to force passwords #13767
base: main
Are you sure you want to change the base?
Conversation
We also need 2 capabilities:
|
Can you rebase, so CI runs? |
ad9fb9f
to
25d7135
Compare
Almost there, just a small bug and some documentation fixes |
f7e9726
to
4a5795f
Compare
cf54d5d
to
010bb92
Compare
…tions Signed-off-by: Anna Larch <[email protected]>
010bb92
to
3fd8877
Compare
@@ -115,7 +115,6 @@ | |||
## Creating a new conversation | |||
|
|||
*Note:* Creating a conversation as a child breakout room, will automatically set the lobby when breakout rooms are not started and will always overwrite the room type with the parent room type. Also, moderators of the parent conversation will be automatically added as moderators. | |||
|
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.
$password parameter should also be added to Allow guests in a conversation (public conversation)
@@ -645,10 +654,10 @@ protected function createCircleRoom(string $targetCircleId): DataResponse { | |||
} | |||
|
|||
/** | |||
* @return DataResponse<Http::STATUS_CREATED, TalkRoom, array{}>|DataResponse<Http::STATUS_BAD_REQUEST, array{error?: string}, array{}>|DataResponse<Http::STATUS_NOT_FOUND, array<empty>, array{}> | |||
* @return DataResponse<Http::STATUS_CREATED, TalkRoom, array{}>|DataResponse<Http::STATUS_BAD_REQUEST, array{error?: string, hint?: string}, array{}>|DataResponse<Http::STATUS_NOT_FOUND, array<empty>, array{}> |
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.
Should we use message
to align with the other cases where we add the human readable message?
* @return DataResponse<Http::STATUS_CREATED, TalkRoom, array{}>|DataResponse<Http::STATUS_BAD_REQUEST, array{error?: string, hint?: string}, array{}>|DataResponse<Http::STATUS_NOT_FOUND, array<empty>, array{}> | |
* @return DataResponse<Http::STATUS_CREATED, TalkRoom, array{}>|DataResponse<Http::STATUS_BAD_REQUEST, array{error?: string, message?: string}, array{}>|DataResponse<Http::STATUS_NOT_FOUND, array<empty>, array{}> |
Same then in the actual code I guess
} catch (TypeException $e) { | ||
return new DataResponse(['error' => $e->getReason()], Http::STATUS_BAD_REQUEST); | ||
} | ||
|
||
return new DataResponse(); | ||
|
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.
nitpick
☑️ Resolves
in public conversations
🛠️ API Checklist
🚧 Tasks
🏁 Checklist
docs/
has been updated or is not required