Release v0.8.2

Author: hugobessa

CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## Version 0.8.2
+
+* **`orderBy` support added to `filterNotifications`**:
+  * Added optional `orderBy` contract to service/backend filtering flow with date-based fields: `sendAfter`, `sentAt`, `readAt`, `createdAt`, `updatedAt`.
+  * Added explicit ordering direction support: `asc` and `desc`.
+  * Added/extended backend filter capability keys for ordering: `orderBy.sendAfter`, `orderBy.sentAt`, `orderBy.readAt`, `orderBy.createdAt`, `orderBy.updatedAt`.
+  * Updated service-level capability merge behavior coverage for multi-backend reads (`defaults + backend overrides`).
+* **Backend behavior**:
+  * Prisma backend supports all `orderBy.*` fields.
+  * Medplum backend supports ordering by `sendAfter`, `sentAt`, `createdAt`, `updatedAt`; `orderBy.readAt` is unsupported and reported as `false`.
+* **Documentation updates**:
+  * Added README section describing `filterNotifications(..., orderBy)`, `NotificationOrderBy` shape, and capability discovery with `getBackendSupportedFilterCapabilities()`.
+
 ## Version 0.8.1
 
 * **Multi-backend support added to VintaSend**:

README.md

@@ -159,6 +159,57 @@ const backendStats = await vintasend.getBackendSyncStats();
 - Additional backend replication failures are logged and do not fail the primary operation.
 - This keeps primary workflows available while still enabling redundancy.
 
+## Filtering and Ordering Notifications
+
+Use `filterNotifications` to query notifications with pagination and optional ordering.
+
+```typescript
+const notifications = await vintasend.filterNotifications(
+  {
+    status: 'PENDING_SEND',
+  },
+  1,
+  25,
+  {
+    field: 'createdAt',
+    direction: 'desc',
+  },
+);
+```
+
+### `orderBy` shape
+
+```typescript
+type NotificationOrderBy = {
+  field: 'sendAfter' | 'sentAt' | 'readAt' | 'createdAt' | 'updatedAt';
+  direction: 'asc' | 'desc';
+};
+```
+
+Examples:
+- `{ field: 'createdAt', direction: 'desc' }`
+- `{ field: 'sendAfter', direction: 'asc' }`
+
+### Checking backend support
+
+Use `getBackendSupportedFilterCapabilities()` to detect support gaps per backend.
+
+```typescript
+const capabilities = await vintasend.getBackendSupportedFilterCapabilities();
+
+if (!capabilities['orderBy.readAt']) {
+  // Fallback to another ordering field
+}
+```
+
+When using multiple backends, you can check capabilities for a specific backend identifier:
+
+```typescript
+const replicaCapabilities = await vintasend.getBackendSupportedFilterCapabilities('replica-backend');
+```
+
+`vintasend-medplum` currently does not support `orderBy.readAt`, and reports `orderBy.readAt: false`.
+
 ## Attachment Support
 
 VintaSend supports file attachments for notifications with an extensible architecture that allows you to choose your preferred storage backend.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "vintasend",
-  "version": "0.8.1",
+  "version": "0.8.2",
   "main": "dist/index.js",
   "files": [
     "dist"