@object-ui/data-objectstack 16.1.0 → 17.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -179,7 +179,12 @@ import {
179
179
  BulkOperationError, // Bulk operation failures with partial results
180
180
  ConnectionError, // Network/connection errors (503/504)
181
181
  AuthenticationError, // Authentication failures (401/403)
182
- ValidationError, // Data validation errors (400)
182
+ DataApiValidationError, // Data validation errors (400). Its runtime `name` is
183
+ // still 'ValidationError' — that string is the wire
184
+ // discriminator shared with @objectstack/client. The
185
+ // SYMBOL is prefixed because @objectstack/spec/kernel
186
+ // owns `ValidationError` for a { field, message, code? }
187
+ // record (objectui#3160).
183
188
  } from '@object-ui/data-objectstack';
184
189
  ```
185
190
 
@@ -296,7 +301,7 @@ child write fails.
296
301
  Whether the adapter can rely on server atomicity is decided **at connect time**,
297
302
  not by firing a batch and reading the failure. `connect()` reads the
298
303
  `capabilities.transactionalBatch` flag from `GET /api/v1/discovery`
299
- ([framework #3298](https://github.com/objectstack-ai/framework/issues/3298)),
304
+ ([framework #3298](https://github.com/objectstack-ai/objectstack/issues/3298)),
300
305
  which the server sets to `true` only when the `/batch` route is mounted **and**
301
306
  the runtime engine can honour a transaction (`declared === enforced`):
302
307
 
@@ -326,9 +331,9 @@ would turn "saves, less safe" into "no save path" on older backends
326
331
 
327
332
  Atomic cross-object saves are **guaranteed only against ObjectStack backends on
328
333
  the 16.x line that advertise `capabilities.transactionalBatch: true`** — the
329
- endpoint landed in [framework #1604](https://github.com/objectstack-ai/framework/issues/1604)
334
+ endpoint landed in [framework #1604](https://github.com/objectstack-ai/objectstack/issues/1604)
330
335
  and its discovery capability in
331
- [framework #3298](https://github.com/objectstack-ai/framework/issues/3298).
336
+ [framework #3298](https://github.com/objectstack-ai/objectstack/issues/3298).
332
337
  ObjectUI does not hard-require it: against an older backend a master-detail save
333
338
  still succeeds, but non-atomically via the fallback above. Treat the advertised
334
339
  capability as the floor for the atomicity guarantee, not as a connection