Skip to content

v6.5.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 24 Jul 21:34
· 9 commits to master since this release
v6.5.0
7c39b7d

v6.5.0 — the data model comes home

eQuantic.Core.DataModel now lives in this repository, beside the engine it describes, and versions with it.

What changes for you

Nothing in the API — the types are the same. What changes is where the package comes from and how it is numbered:

  • It ships from this repo, packed and published alongside the providers, so eQuantic.Core.DataModel is now at 6.5.0 and moves with each core-data release.
  • eQuantic.Core.Data depends on that same version, so the engine and the model it maps can no longer drift apart: what the repository builds against is exactly what ships.
  • 4.0.0 stays on NuGet and keeps working. The source is unchanged, so a project that pins it — eQuantic.Core.Persistence from core-ddd, for instance — resolves cleanly either way.

The project also declares its own target frameworks (net8.0, net10.0), which it used to inherit from the repository it came from.

Why

IEntity<TKey> is the contract the engine's repositories are written against — IAsyncRepository<TEntity, TKey> constrains on it. Keeping that contract in a separate repository meant every change to it crossed a release boundary before the engine could use it. Now the two move together, and a change to the model is a change to the engine's own build.

Full changelog: v6.4.0...v6.5.0

Assets 19
Loading