isFinite
neuro.number.isFinite
Section titled “neuro.number.isFinite”Static method on Number.
Returns true if passed value is finite. Unlike the global isFinite, Number.isFinite doesn’t forcibly convert the parameter to a number. Only finite values of the type number, result in true.
Signatures
Section titled “Signatures”isFinite(input: { number: unknown; prompt?: string }): Promise<boolean>The prompt field is optional. When omitted (or set to an empty string)
the wrapper falls back to the native Number.isFinite and returns a
resolved Promise without contacting the LLM. When present, the LLM is given
the original arguments plus your prompt and is asked to behave like the
original method.
Example
Section titled “Example”import { configureClient, neuro } from 'neuro-ts';
configureClient({ apiKey: process.env.OPENAI_API_KEY });
// Strict finite check. Unlike scope creep, this actually has a limit.await neuro.number.isFinite({ number: budget, prompt: 'return true only when the argument is a finite Number, unlike your technical debt which has no bounds' });System prompt
Section titled “System prompt”The exact system prompt the SDK sends to your model when you provide a
prompt field:
Number.isFiniteYou are simulating the JavaScript built-in `Number.isFinite`.
## Original signature(s)
Overload 1: (number: unknown) => boolean
## JSDoc
Returns true if passed value is finite.
Unlike the global isFinite, Number.isFinite doesn't forcibly convert the parameter to a
number. Only finite values of the type number, result in true.
## How to respond
- Behave EXACTLY as the original `isFinite` would, but use the user's intent to choose any callback / comparator / transform logic that the original would normally accept as an argument.
- Strictly preserve the original return type and shape.
- Output ONLY the JSON-encoded return value of the function call.
- Do NOT include explanations, prose, comments, or markdown fences.
- If the function would return `undefined`, output the literal string `undefined`.
- For Date / RegExp / Map / Set / TypedArray returns, output an object of the form { "__type": "Date" | "RegExp" | "Map" | "Set" | "<TypedArrayName>", ... } so the SDK can rehydrate it.