Patterns, gotchas and small wins from fifteen-odd years of .NET and web work — the Regira packages and modules, entity pipelines, editorial front-ends and everything between.
A list screen users can bookmark, share and hit Back on without losing their filters, and that never shows an error over data that loaded fine. The rules behind it, and the Vue composables that apply them.
One customer must never see another's rows, in any list, count or endpoint, including the one added next year. Seven requirements that make that a property of the system, and which of them no library can meet for you.
One table for every customer, supplier and employee, with roles and alliances as dated relationships instead of extra tables. Tested on Westeros, where everyone knows who betrayed whom and when.
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.
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.
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.
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.
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.
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.