Why should you care?

ShopNest custom paginated catalog cursors should feel like foreach without leaking SQL details.

See it live — copy this example

Paste into a C# console or class library project and run dotnet run.

public sealed class SkuPage
{
    private readonly string[] _skus;
    public SkuPage(params string[] skus) => _skus = skus;
    public IEnumerator<string> GetEnumerator()
    {
        foreach (var s in _skus) yield return s;
    }
}

foreach (var sku in new SkuPage("HD-100", "HD-200"))
    Console.WriteLine(sku);

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• yield return builds an iterator state machine.
• Callers foreach without knowing the array.
• Rarely build a manual IEnumerator unless you need special cursor semantics.

Practice next

1. Foreach the SkuPage.
2. Add a Filter iterator with yield.
3. Prefer IAsyncEnumerable for streaming APIs.
4. Yield only SKUs starting with HD.
5. Write an async iterator reading pages.

Remember

Traverse without exposing guts. IEnumerable/yield in C#. Custom iterators for cursors.

ShopNest catalog cursor

API streams SKUs via IAsyncEnumerable.

Outcome: Clients iterate pages without SQL knowledge.