Solve a rated Puzzle: served near the Puzzle rating, Moves checked by the server #443
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
#444 The provisional Puzzle rating: an info icon and a tooltip
amaurycoudr/chess-project
#445 Hint, Show solution, give up and an unrated retry
amaurycoudr/chess-project
#446 Train on a Theme
amaurycoudr/chess-project
#441 The Puzzle rating rules: a Glicko-2 module, its ADR and the glossary terms
amaurycoudr/chess-project
#442 The Puzzle set loaded on every stack
amaurycoudr/chess-project
Reference
amaurycoudr/chess-project#443
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
#440
What to build
The tracer bullet: a signed-in Player solves or fails a rated Puzzle, end to end.
/puzzlesneeds an Account Session, with the samebeforeLoadguard as the account page (#409), remembering the destination. A Guest is asked to sign in or sign up.puzzlerouter withnext,moveandrating, Account-only, its errors inREFUSAL_STATUS. Moves over the wire as UCI (ADR 0021). Copy in English and French (ADR 0025).Seams: S1 (the API through its RPC contract) and S3 (the app's router with the API fakes). Covers stories 1-17, 20-21, 27-31, 47-48 of #440.
Acceptance criteria
/puzzlesgoes to sign-in and comes back after it; a signed-out RPC call is refused.rpc-gamesandrpc-clockintegration tests,router.test.tsx.CONTRIBUTING.md, "The five commands").mentioned in issue #444
mentioned in issue #445
mentioned in issue #446
mentioned in issue #441
marked this issue as related to #440
marked this issue as related to #441
marked this issue as related to #442
marked this issue as related to #444
marked this issue as related to #445
marked this issue as related to #446
mentioned in merge request !554