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:
@@ -60,10 +60,10 @@ export function useNamingCategories() {
|
||||
})
|
||||
}
|
||||
|
||||
export function useNameSuggestions(runId: number | null) {
|
||||
export function useNameSuggestions(runId: number | null, pokemonId?: number | null) {
|
||||
return useQuery({
|
||||
queryKey: ['name-suggestions', runId],
|
||||
queryFn: () => getNameSuggestions(runId!),
|
||||
queryKey: ['name-suggestions', runId, pokemonId ?? null],
|
||||
queryFn: () => getNameSuggestions(runId!, 10, pokemonId ?? undefined),
|
||||
enabled: runId !== null,
|
||||
})
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user