Show a self-game once, with both sides as You #386

New issue

Closed

opened 2026-10-11 16:27:34 +00:00 by root · 8 comments

root commented

2026-10-11 16:27:34 +00:00

(Migrated from gitlab.core-project.space)

Imported from GitHub amaurycoudr/chess-project#386, opened by @amaurycoudr on 2026-10-11 16:27 UTC.

Parent

#365

What to build

A claim can leave one Account owning both Colors of a Game: two claimed Guests that played each other, or a Guest that played its own Account. ADR 0035 keeps such a self-game. The Player sees it once in "My games", with both sides as "You". The result reads as the winning Color or a draw, never as won or lost. The Game page shows it with White at the bottom.

The caller's Color in the "My games" listing, the viewer on the Game read and the Color in the Account export gain one value: the owner of both Colors. This widens the earlier specs' shapes in place.
The listing returns a self-game once.
"My games" and the Game page render that value; every new string goes in the Paraglide catalogue in English and French (ADR 0025).

Seam: The RPC wire (the listing row, the Game read's viewer, the export's Color) and the front views ("My games" view, Game page)

Acceptance criteria

On the wire, a self-game from two claimed Guests and one from a Guest against its own Account each come back as one listing row, with the "both" value as the caller's Color.
game.get as the owning Account answers the "both" viewer; as anyone else it answers as before.
The Account export gives a self-game the "both" Color.
"My games" shows a self-game once, both sides as "You", and its result as the winning Color or a draw.
The Game page shows a self-game with both sides as "You" and White at the bottom.
Every new string exists in English and French.

> _Imported from GitHub [amaurycoudr/chess-project#386](https://github.com/amaurycoudr/chess-project/issues/386), opened by [@amaurycoudr](https://github.com/amaurycoudr) on 2026-10-11 16:27 UTC._  --- ## Parent #365 ## What to build A claim can leave one **Account** owning both **Colors** of a **Game**: two claimed **Guests** that played each other, or a **Guest** that played its own **Account**. ADR 0035 keeps such a self-game. The **Player** sees it once in "My games", with both sides as "You". The result reads as the winning **Color** or a draw, never as won or lost. The **Game** page shows it with White at the bottom. - The caller's **Color** in the "My games" listing, the viewer on the **Game** read and the **Color** in the **Account** export gain one value: the owner of both **Colors**. This widens the earlier specs' shapes in place. - The listing returns a self-game once. - "My games" and the **Game** page render that value; every new string goes in the Paraglide catalogue in English and French (ADR 0025). Seam: The RPC wire (the listing row, the **Game** read's viewer, the export's **Color**) and the front views ("My games" view, **Game** page) ## Acceptance criteria - [ ] On the wire, a self-game from two claimed **Guests** and one from a **Guest** against its own **Account** each come back as one listing row, with the "both" value as the caller's **Color**. - [ ] `game.get` as the owning **Account** answers the "both" viewer; as anyone else it answers as before. - [ ] The **Account** export gives a self-game the "both" **Color**. - [ ] "My games" shows a self-game once, both sides as "You", and its result as the winning **Color** or a draw. - [ ] The **Game** page shows a self-game with both sides as "You" and White at the bottom. - [ ] Every new string exists in English and French.

root commented

2026-10-11 16:27:34 +00:00

(Migrated from gitlab.core-project.space)

GitHub issue relations, imported as "related" links (GitLab CE has no sub-issues or blocking links).

Parent (sub-issue of): #365
Blocked by: #385
Blocking: #389

> _GitHub issue relations, imported as "related" links (GitLab CE has no sub-issues or blocking links)._  - Parent (sub-issue of): #365 - Blocked by: #385 - Blocking: #389

root commented

2026-10-13 08:39:51 +00:00

(Migrated from gitlab.core-project.space)

mentioned in issue #389