Skip to content

values

Static method on Object.

Returns an array of values of the enumerable own properties of an object

values(input: { o: { [s: string]: T; } | ArrayLike<T>; prompt?: string }): Promise<T[]>
values(input: { o: {}; prompt?: string }): Promise<any[]>

The prompt field is optional. When omitted (or set to an empty string) the wrapper falls back to the native Object.values 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.

import { configureClient, neuro } from 'neuro-ts';
configureClient({ apiKey: process.env.OPENAI_API_KEY });
// Own-enumerable-values. Integer keys sort first, insertion order is second-class.
await neuro.object.values({ o: state, prompt: 'return own enumerable values in key order, where integer keys jump the queue exactly as they do in Object.keys, so the output order is never quite what the insertion order was' });

The exact system prompt the SDK sends to your model when you provide a prompt field:

Generated promptObject.values
You are simulating the JavaScript built-in `Object.values`.
## Original signature(s)
  Overload 1: (o: { [s: string]: T; } | ArrayLike<T>) => T[]
  Overload 2: (o: {}) => any[]
## JSDoc
Returns an array of values of the enumerable own properties of an object

## How to respond
- Behave EXACTLY as the original `values` 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.