Repository navigation
✨ feat!: migrate to eQuantic.Core.Data v5 - #1
Merged
Merged
Conversation
Brings core-api onto the current data stack: eQuantic.Core.Data 4.3.2 -> 5.5.0, the EntityFramework providers to their v5 lane (net8 8.2.0/8.3.0, net10 10.1.0/10.2.0), and the eQuantic.Linq family (Web + Swashbuckle) to 3.7.1. The v5 repository contracts drop the TUnitOfWork generic parameter — the engine is out of the generics — so IAsyncQueryableRepository<TEntity, TKey> and GetAsyncQueryableRepository<TEntity, TKey>() take two type arguments instead of three. core-api's own code was already v5-shaped (EntityDataBase implements IEntity<TKey>); only the sample service consumed the old three-argument form. Build clean across net8/net10; the full suite (Domain, Persistence, Relational, PostgreSql, Api) is green on both frameworks. BREAKING CHANGE: repository resolution now uses the two-argument v5 contracts (IAsyncQueryableRepository<TEntity, TKey>); consumers on the three-argument v4 form must drop the TUnitOfWork type argument.
|
🎉 This PR is included in version 3.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Brings
core-apionto the current data stack — it was the last consumer still on Core.Data v4.eQuantic.Core.DataeQuantic.Core.Data.EntityFramework(.SqlServer/.PostgreSql/.MySql/.MongoDb)eQuantic.Linq.WebeQuantic.Linq.Web.SwashbuckleCode impact — minimal
The v5 repository contracts drop the
TUnitOfWorkgeneric parameter (the engine is out of the generics), soIAsyncQueryableRepository<TEntity, TKey>andGetAsyncQueryableRepository<TEntity, TKey>()take two type arguments instead of three.core-api's own code was already v5-shaped (EntityDataBase<TKey>implementsIEntity<TKey>withGetKey/SetKey); the only source change was the sample service, which consumed the old three-argument form.Proof
Solution builds clean on net8 + net10. Full suite green on both frameworks: Domain (7), Persistence (5), Persistence.Relational (9), Persistence.PostgreSql (8), Api (4) — 33 tests × 2 TFMs, all via EF InMemory (no Docker needed).
The pre-existing NU1608 (Pomelo MySql 9 vs EF Relational 10) warning is unchanged upstream noise.
Notes
TUnitOfWorktype argument) → semantic-release will cut a major.eQuantic.Core.Apiversion.