<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Search on Pauls Blog</title><link>https://prule.github.io/pauls-blog/tags/search/</link><description>Recent content in Search on Pauls Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 11 May 2026 00:00:00 +1000</lastBuildDate><atom:link href="https://prule.github.io/pauls-blog/tags/search/index.xml" rel="self" type="application/rss+xml"/><item><title>Anatomy of a Search Endpoint: Filter, Sort, Paginate, HATEOAS</title><link>https://prule.github.io/pauls-blog/post/coding/2026/anatomy-of-search/</link><pubDate>Mon, 11 May 2026 00:00:00 +1000</pubDate><guid>https://prule.github.io/pauls-blog/post/coding/2026/anatomy-of-search/</guid><description>&lt;h1 id="anatomy-of-a-search-endpoint-filter-sort-paginate-hateoas"&gt;Anatomy of a Search Endpoint: Filter, Sort, Paginate, HATEOAS&lt;/h1&gt;
&lt;p&gt;A walk through &lt;code&gt;GET /api/1/sessions&lt;/code&gt; in the Laptime Insights server — from the Ktor route, down through the use case and persistence port, into the Exposed query, and back out as a HATEOAS page that the React frontend uses to render a sortable table.&lt;/p&gt;
&lt;p&gt;The feature is small but it touches every layer, so it&amp;rsquo;s a good example of how clean architecture lets each concern live in exactly one place: the domain decides what&amp;rsquo;s sortable, the repository decides how that maps to a column, the resource decides how it appears on the wire, and the UI decides how to render it. Nothing leaks.&lt;/p&gt;</description></item></channel></rss>