[10] Create embedded_schemas for e2ee endpoints #35
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
qa
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
main/bromal!35
Loading…
Reference in a new issue
No description provided.
Delete branch "serra/e2ee"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
PR in support of #10.
May have gone a little overboard with some of the request validations here.
@ -656,3 +656,3 @@add :user_id, :string, null: falseadd :algorithms, {:array, :string}add :public_key, :string, null: falseadd :keys, :map, null: falseRealized that this column mapping makes things a whole lot easier for parsing and storing device keys
Wasn't sure if the supporting request types should be under the
Bromal.Typesmodule or yet another layer underBromal.Request.Client.KeysRandom aside, but with this PR, there are exactly 1000 test cases in Bromal now! 🎉
Create embedded_schemas for e2ee endpointsto [10] Create embedded_schemas for e2ee endpoints@ -0,0 +26,4 @@describe "claim form" dotest "parse/1 returns data with user id strings converted to Types.UserId" douser_1 = user_fixture()For future: I would use
user1anduser2instead ofuser_1anduser_2for consistency with other places.Seems to be OK.
For future: the constructions like
... |> map |> filter |> map ...I would rewrite to useStreammodule instead ofEnum. You can leave it as is, at least for now.@serra wrote in #35 (comment):
Hey, I'm finishing tests for CLI/RPC now and thought, that I will want to boast about this number overflow. :)
@serra wrote in #35 (comment):
I suppose, the second variant is better. Under the
Bromal.Typeswe have more primitive and generic types.7cf4a696b8ca011c13c1