Add naming scheme support for genlockes with lineage-aware suggestions (#20)
Genlockes can now select a naming scheme at creation time, which is automatically applied to every leg's run. When catching a pokemon whose evolution family appeared in a previous leg, the system suggests the original nickname with a roman numeral suffix (e.g., "Heracles II"). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Reviewed-on: TheFurya/nuzlocke-tracker#20 Co-authored-by: Julian Tabel <juliantabel.jt@gmail.com> Co-committed-by: Julian Tabel <juliantabel.jt@gmail.com>
This commit was merged in pull request #20.
This commit is contained in:
@@ -230,6 +230,7 @@ export interface Genlocke {
|
||||
status: 'active' | 'completed' | 'failed'
|
||||
genlockeRules: GenlockeRules
|
||||
nuzlockeRules: NuzlockeRules
|
||||
namingScheme: string | null
|
||||
createdAt: string
|
||||
legs: GenlockeLeg[]
|
||||
}
|
||||
@@ -239,6 +240,7 @@ export interface CreateGenlockeInput {
|
||||
gameIds: number[]
|
||||
genlockeRules: GenlockeRules
|
||||
nuzlockeRules: NuzlockeRules
|
||||
namingScheme?: string | null
|
||||
}
|
||||
|
||||
// Genlocke list / detail types
|
||||
@@ -283,6 +285,7 @@ export interface GenlockeDetail {
|
||||
status: 'active' | 'completed' | 'failed'
|
||||
genlockeRules: GenlockeRules
|
||||
nuzlockeRules: NuzlockeRules
|
||||
namingScheme: string | null
|
||||
createdAt: string
|
||||
legs: GenlockeLegDetail[]
|
||||
stats: GenlockeStats
|
||||
|
||||
Reference in New Issue
Block a user