Age | Commit message (Collapse) | Author |
|
nextcloud/bugfix/noid/allow-to-respond-with-modified-common-read-value
Allow to respond with modified common read value on "not modified" messages
|
|
We need to set the status code to 200 when the header is modified,
because as per "section 10.3.5 of RFC 2616" entity headers shall be
stripped out on 304: https://stackoverflow.com/a/17822709
This means the header would not be sent to the clients at all, so
they wouldn't update the read marker when idling in the chat.
For the web interface this is not needed, as we update the info
every 30 seconds with the conversation list refresh and can therefor
save the query
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Co-authored-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Fix number detection in participantType tests
The guests app is now enabled.
The spreed app is whitelisted for guest account users.
A password is now set for the guest account users to be able to log in properly.
Added system message tests for listable and read-only attributes.
Added tests scenarios for permission checks and room type checks before
setting listable attribute.
Added integration tests for /listed-rooms endpoint
Covers permissions to search and also with and without search terms.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Added a spreedcheats endpoint to allow creating guest account
users for integration tests.
Grabs the GuestManager from the guests app to create a guest user in the
correct backend.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Added guest app to CI for callapi tests.
Added test scenarios for joining listable rooms.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Bootstrap SystemMessage/ListenerTest.
Add test cases for user add event.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Always join as USER when joining group or public room
Allow nulls for Oracle
Changes after review
Removed populateBaseRoomData and reused the existing code by adding an
extra condition for when querying listable rooms with null participant.
Co-authored-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Added ability to set a conversation as listable for regular users and/or
guest users from the guest app.
This only implements the flag, endpoint and UI to manage it but not yet
making it appear in search results.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Create a new table for internal signaling and guest names with a PK
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
As the description length is limited and the response for the
conversation list endpoint is gzip compressed the hash does not provide
too much of a reduction, but introduces a more complex logic in the
clients. Due to all this, for simplicity now the raw description is also
returned when getting the conversation list.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
By default API version 1 will be used. To use a specific API version
" (v1)", " (v2)" or " (v3)" can be appended to the step name.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
nextcloud/fix-user-management-in-password-request-rooms
Fix user management in password request rooms
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Only the owner and another participant will be allowed to join a
password request room, so there is no point in being able to add more
participants to those rooms.
Although throwing the exception in the listener is enough to prevent
adding the participants unhandled exceptions in the endpoint are
returned as error 404, but the expected error would be 400. To minimize
conflicts with other pull requests and backports it is explicitly
checked if the room is a password request room instead of refactoring
the code to handle the exception.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
This fixes a regression introduced in 4afa2d7946.
The active guests are only those who are currently in a call, and not
those who are currently in the conversation. Therefore other guests or
users were not prevented from joining a password request conversation if
a guest was in the conversation but not in the call.
Fortunately in practice this was not a problem, as the Web UI starts a
call immediately after joining the conversation, which made the guest
immediately active and thus prevented others from joining.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Until now it was possible to verify the room data when getting the full
room list with the "user is participant of the following rooms" step.
Now the same can be optionally done when using "user is participant of
room XXX" too.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Updated for some acceptable issues around the listener introduced by
server side changes.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
integration tests mostly anyway
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|