fix: Handle undefined evaluation score in hint request
- Fix second instance of evaluation.score comparison - Ensures production build completes successfully
This commit is contained in:
@@ -273,7 +273,7 @@ User Question: ${text}
|
|||||||
|
|
||||||
Current Position Data:
|
Current Position Data:
|
||||||
- Best Move: ${evaluation?.bestMove}
|
- Best Move: ${evaluation?.bestMove}
|
||||||
- Evaluation: ${evaluation?.score} centipawns ${evaluation?.score > 0 ? '(White is better)' : evaluation?.score < 0 ? '(Black is better)' : '(Equal)'}
|
- Evaluation: ${evaluation?.score ?? 'N/A'} centipawns ${evaluation?.score !== undefined ? (evaluation.score > 0 ? '(White is better)' : evaluation.score < 0 ? '(Black is better)' : '(Equal)') : ''}
|
||||||
- Mate in: ${evaluation?.mate || 'None'}
|
- Mate in: ${evaluation?.mate || 'None'}
|
||||||
|
|
||||||
INSTRUCTIONS:
|
INSTRUCTIONS:
|
||||||
|
|||||||
Reference in New Issue
Block a user