Regira.blog v1.3
← All articles
Series

Filtering in Regira Entities

6 parts 28 min in total

Six short parts on the read side of an API: naming what users can filter on once, then sorting and paging, the rules every query obeys, archiving, free-text search, and combining searches. Each part has a sample to curl along.

  1. From Query Parameters to a Composable Filter Pipeline

    Search screens that stay simple as the filters pile up: name what users can filter on once, and let the database do the work. Most APIs grow a tangle of optional parameters nobody tests instead.

    8 min read

  2. Sorting and Paging Without Surprises

    Lists that users sort by several columns, that load related data only when a screen asks, and that never hand a client a million rows. Declared once, applied to every list.

    5 min read

  3. Filters You Register Once and Cannot Forget

    Rules that must hold for every record, such as hiding deleted data or showing each customer only their own, set up once and applied everywhere. They also cover the endpoint added next year, and nobody skips them by accident.

    3 min read

  4. Delete Without Losing Anything

    Let users delete a record and still get it back: it disappears from every screen, stays in the database, and restores in one click. A recycle bin and an audit view come with it, no extra code.

    5 min read

  5. A Search Box That Finds Café When You Type Cafe

    A search box that finds 'Café' when someone types 'Cafe', and 'Mercedes-Benz' for 'mercedes', without extra work on every search. The trick: tidy the text once when it is saved, not each time someone searches.

    4 min read

  6. Let Users Search for This or That

    Let users ask for this or that, one brand or anything overdue, in a list that still pages and sorts like every other. How to offer 'or' without a flag nobody trusts.

    3 min read