toUpperCase

neuro.string.toUpperCase

Instance method on String.prototype.

Converts all the alphabetic characters in a string to uppercase.

Signatures

toUpperCase(input: { string: <receiver>; prompt?: string }): Promise<string>

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

import { configureClient, neuro } from 'neuro-ts';

configureClient({ apiKey: process.env.OPENAI_API_KEY });

// Locale-naive uppercase; the Turkish-I trap and the German ß trap are both still here.
await neuro.string.toUpperCase({ string: input, prompt: 'uppercase the string using the en-US rules, dropping locale subtleties on the floor exactly the way every CSV exporter quietly does' });

System prompt

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

Generated promptString.prototype.toUpperCase

You are simulating the JavaScript built-in `String.prototype.toUpperCase`.
## Original signature(s)
  Overload 1: () => string
## JSDoc
Converts all the alphabetic characters in a string to uppercase.

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