Skip to content

1.0.0-alpha.1 - Normalize and harden page handling with updated runtime requirements

Pre-release
Pre-release

Choose a tag to compare

@allanmcarvalho allanmcarvalho released this 18 Nov 02:15
· 11 commits to 1.x since this release

Added

  • Preview documentation & contracts (adapter): Added/updated Dapter preview docs, related contracts, and new adapter implementation code to expand the preview surface area and clarify upcoming expectations.
  • AI standards documentation: Introduced an AI standards bundle with related “skills” documentation to formalize repository guidance for agent behavior.
  • Regression coverage: Added tests for query defaults and result counts to guard against regressions in query-building behavior.

Changed

  • Minimum supported dependencies: Bumped the minimum supported Inertia and Vue versions required by the adapter.

Fixed

  • Preserve Eloquent keys for simple-page rows: Normalized simple-page row shape consistently while preserving original Eloquent keys to prevent downstream identity/order/linkage issues after transformation/rehydration.
  • Vite distribution packaging canonicalization: Canonicalized the packed consumer root for Vite distribution handling.
  • Console: preserve non-string name validation/analysis: Updated console validation/analysis to preserve non-string name values rather than implicitly converting/dropping them, improving correctness and diagnostic fidelity.
  • Eloquent paging hardening: Rejected deferred callbacks and sanitized page bounds to prevent inconsistent results and runtime issues from delayed execution paths and invalid pagination parameters.

CI / Internal Maintenance

  • Native backend DB workflow & distribution checks: Added a CI workflow using a native backend database setup and included distribution/package verification checks to improve build/test reliability across expected environments.

Compatibility & Migration

  • Dependency constraints may break older setups: The adapter now requires newer Inertia and Vue versions. If you’re pinned below the new minimums, update your project dependencies before upgrading.
  • No migration required for standard usage:
    • Page handling fixes (normalization, key preservation, bounds sanitation) are intended to correct behavior; normal API usage should remain compatible.
    • If you previously relied on deferred callbacks behavior or passed out-of-range bounds, you’ll need to adjust inputs to match the newly enforced expectations.

Testing

  • Added regression tests covering query defaults and counts to improve confidence in query stability and result accuracy.