single-or-array-pattern

You normalize API inputs by converting single items into one-element arrays using Array.isArray checks. This approach enforces a single internal array-based pathway, allowing CRUD operations and factory functions to handle one or many inputs efficiently.

The overload pattern for API design normalizes single inputs to one-element arrays automatically, delegating them to a shared array-based implementation. This provides a single flexible entry point and avoids maintaining separate code paths for single and bulk operations.

Batch processing APIs often fail with single items because downstream code expects array methods. Normalizing inputs by wrapping single items into one-element arrays before processing ensures all data flows through a single consistent array-based implementation path.

The best way to simplify CRUD operations is normalizing inputs to arrays at the entry point. By converting single items to one-element arrays, you provide a single internal path for bulk processing, reducing branching logic and simplifying your API design.

Yes, you can use the single-or-array pattern for factory functions. It normalizes inputs by converting single items into one-element arrays, allowing factory functions to process one or many inputs through a single array-based implementation path.

You should avoid array normalization for API inputs when the distinction between a single item and an array carries specific semantic meaning for your downstream processing. If wrapping a single item changes the operational logic, maintaining separate paths may be necessary.