Read an Account's profile and its decided Games over the wire, in an ADR superseding 0034 #389
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#390 Open an Account's profile at /players/<username>: rows, show more, empty and not-found
amaurycoudr/chess-project
#386 Show a self-game once, with both sides as You
amaurycoudr/chess-project
#388 Offer the claim at sign-up and after sign-in
amaurycoudr/chess-project
Reference
amaurycoudr/chess-project#389
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Parent
#366
What to build
Anyone, signed in or not, can read an Account's public profile by username: the username as stored, when the Account joined, and one page of its decided Games, newest first, with a cursor for the next page. A Guest has no profile, and a Game with no Account on either side appears on no profile. The answer carries nothing else about the Account. See #366, Contract, API and ADRs.
First, an ADR superseding ADR 0034 records the one changed decision: an Account's decided Games are listed publicly on its profile, and a Game with no Account owner is listed only to its owner. It restates every other decision of ADR 0034.
Then a new
profilerouter in the contract with one read,profile.get, on a GET route addressed by username, implemented in the games feature module beside "my games":PROFILE_NOT_FOUNDrefusal (404), in the refusal status table and the controller's refusal table;Seam: The RPC wire
Acceptance criteria
mentioned in issue #390
mentioned in issue #366
mentioned in issue #386
mentioned in issue #388
marked this issue as related to #366
marked this issue as related to #386
marked this issue as related to #388
marked this issue as related to #390
mentioned in commit
db9e1fdf59mentioned in commit
d90d1c04a4mentioned in commit
4c3398c3c2mentioned in commit
26a3ed3b6amentioned in commit
0cb053dbe9mentioned in commit
92db661c71mentioned in commit
3ac3237f08mentioned in commit
febccf71f7mentioned in merge request !531