hikari 0dc572c6fa fix: use stable unique keys for quest reward list ...

The previous key `${reward.type}-${amount ?? ""}` collapsed to
"adventurer-" for every adventurer-unlock reward (which carries no
amount), producing duplicate-key React warnings on every render tick.
Because console.error is forwarded to the backend telemetry service,
this caused continuous email alerts.

The key now uses targetId (present on adventurer and upgrade rewards)
first, falls back to amount (present on gold/essence/crystal rewards),
and uses the map index only as a last resort.

2026-03-09 22:07:36 -07:00

..

src

fix: use stable unique keys for quest reward list

2026-03-09 22:07:36 -07:00

test

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00

eslint.config.js

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00

index.html

feat: error handling, logging, analytics, OG tags, and sticky sidebar (#44)

2026-03-09 19:54:42 -07:00

package.json

feat: render changelog as markdown in about panel (#33)

2026-03-09 09:35:30 -07:00

tsconfig.json

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00

vite.config.ts

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00

vitest.config.ts

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00