Uh oh!
There was an error while loading. Please reload this page.
Update coin description + social links - #429
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| row := app.writePool.QueryRow(c.Context(), sql, args) | ||
| var result struct { |
There was a problem hiding this comment.
I'm curious why we are returning all of this? Is the goal to merge it into the client side cache? Mostly concerned because it's not the full fieldset from /v1/coins (here), so we would have to be careful not to just replace the client side object.
There was a problem hiding this comment.
i also was wondering this, maybe better to just not return?
do we have a similar update endpoint whose conventions i can follow?
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| assert.Equal(t, 403, status) | ||
| jsonAssert(t, body, map[string]any{ | ||
| "error": "You do not own this coin", |
There was a problem hiding this comment.
I continue to think that testing the exact content of these messages is brittle and unnecessary. But I might be in the minority. :-)
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| args := pgx.NamedArgs{"mint": mint} | ||
| hasUpdates := false | ||
| if body.Description != "" { |
There was a problem hiding this comment.
Is unsettling the description allowed?
POST endpoint to update artist coin description + social links
seems like we forgot to update
swagger-v1-full.yamlwith/coinget endpoint so adding that too.