-
Notifications
You must be signed in to change notification settings - Fork 324
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 remote users when creating a conversation #1569
Conversation
- It allows to access a Galley instance in a monad implementing the class.
- Checks if remote users exist - Adds remote users to the database - Adds integration tests for qualified users - Updates golden tests related to NewConv
132e453
to
176bfc3
Compare
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.
Looks good, but it's missing some "fromJSON" golden tests to check that the schema for NewConv
is backwards compatible, i.e. it can still parse NewConv
requests that only have unqualified user ids.
I can add that myself later, if that's ok.
Hm, I thought there is a test that does that. Initially I changed that test, but then someone (Joe?) told me it should still parse even when the new field is not given in JSON, so I reverted the change and the test still passed, i.e., it should be backwards compatible. At any rate, if you think such a test case is missing, feel free to add it. |
This is to make sure the `qualified_users` is indeed optional in the JSON being parsed.
…w-conv-adt-and-tests
testCase "NewConv" $ | ||
testFromJSONObjects | ||
[(testObject_NewConvUnmanaged_user_1, "testObject_NewConvUnmanaged_user_1.json")] |
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 this!
🎉 |
This adds remote users when creating a conversation. Note: several checks are still missing, as noted in a related funuction
addMembers
:-- that call should probably be made after inserting the conversation membership happens in this backend.
This PR supersedes PR #1528.