@12-apps/payments-frontend 3.18.0 → 3.18.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@12-apps/payments-frontend",
-  "version": "3.18.0",
+  "version": "3.18.1",
   "type": "module",
   "sideEffects": false,
   "description": "Browser half of the vendor-agnostic payments platform: plug-and-play MUI components for the per-provider settings page (credential form from each provider's schema, masked hints, verify/enable) and the checkout page (PIX QR + polling, card tokenization, hosted-checkout redirect), plus the headless hooks and fetch clients they build on. Talks only to the host's payments HTTP surface — never to a provider directly. Microfrontend-ready: no app coupling, host injects theme and auth.",

package/src/ledger/query.ts

@@ -55,11 +55,22 @@ export function ledgerSearchTerm(params: URLSearchParams): string {
   return params.get('q') ?? '';
 }
 
-/** A grid query mapped back onto the params a ledger URL owns. */
+/**
+ * A grid query mapped back onto the params a ledger URL owns.
+ *
+ * `dir` accepts `null` as well as absent, because that is what a real grid
+ * produces: a column can be in the sort list with no direction chosen yet, and
+ * a data-grid library spells that `null` rather than by leaving the key out.
+ * The runtime always treated the two the same — an unsorted column contributes
+ * no `sort` param — so this is the TYPE catching up with the behaviour rather
+ * than a change to it. Typed the other way, every adopter writes the same
+ * `?? undefined` mapping at the call site, which is exactly the boilerplate
+ * this module exists to delete.
+ */
 export function ledgerParams(query: {
   search: string;
   page: number;
-  sortBy: readonly { id: string; dir?: 'asc' | 'desc' }[];
+  sortBy: readonly { id: string; dir?: 'asc' | 'desc' | null }[];
 }): Record<string, string | undefined> {
   const sort = query.sortBy[0];
   return {