-
Notifications
You must be signed in to change notification settings - Fork 56
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: Add collection response information on creation #1499
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -713,7 +713,15 @@ type user { | |
|
||
switch v := resp.Data.(type) { | ||
case map[string]any: | ||
assert.Equal(t, "success", v["result"]) | ||
assert.Equal(t, map[string]any{ | ||
"result": "success", | ||
"collections": []any{ | ||
map[string]any{ | ||
"name": "user", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. lol: 🤣 we still have a lowercase GQL type. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. lol - we have a lot, I think the entire There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah not sure why those didn't get picked up. The There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we have +1000 tests atm, would have been amazing if you/Orpheus managed to get all of them lol There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think all the cid related ones are done, others are easy to change as/when spotted |
||
"id": "bafkreigrucdl7x3lsa4xwgz2bn7lbqmiwkifnspgx7hlkpaal3o55325bq", | ||
}, | ||
}, | ||
}, v) | ||
|
||
default: | ||
t.Fatalf("data should be of type map[string]any but got %T\n%v", resp.Data, v) | ||
|
@@ -1024,7 +1032,7 @@ type user { | |
verified: Boolean | ||
points: Float | ||
}` | ||
err := db.AddSchema(ctx, stmt) | ||
_, err := db.AddSchema(ctx, stmt) | ||
if err != nil { | ||
t.Fatal(err) | ||
} | ||
|
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.
question: Do we still want to return
"result", "success"
? Do we do this for all successful calls across the http api?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.
Yeah, I had a similar thought. Its a somewhat meaningless item to include, but I have no strong preference either way.
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.
It wasn't meaningless when there was nothing else we were returning but now I think we can safely remove it.