Repository navigation
test: certify Dapper 2.1.89 interoperability - #296
rodri-oliveira-dev wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 088550f4ec
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
SonarQube Cloud successThe SonarQube Cloud Quality Gate passed for this PR. Quality Gate status: OK
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Consolidado no PR #298. O comentário de revisão sobre restauração do estado global Dommel foi corrigido, respondido e resolvido no conjunto consolidado. |
…ver-governance Prepare FluentMap 3.6.1 and establish semantic versioning governance. - Set Dapper 2.1.89 as the minimum supported version. - Align DateOnly/TimeOnly conversions across runtime and generated materializers. - Expand interoperability, provider compatibility and Native AOT tests. - Synchronize versioning across all five NuGet packages. - Add a semantic versioning skill and automated validation, preventing unauthorized major upgrades. - Update compatibility, migration and release documentation in English and Portuguese. - Consolidate PRs #291, #295, #296 and #297. Refs #294.
Summary
DynamicParametersdelegation through mapped sync and async queries, including nulls, literals, explicitDbType, size, precision/scale and SQL Server output parametersDateTime/TimeSpan), PostgreSQL/Npgsql 10 (nativeDateOnly/TimeOnly) and SQLite (ISO text plus explicit converters), comparing runtime and strict-generated materializationGeneratedParametersboundary and explicitly rejectDynamicParametersthereInsertMapped*/UpdateMapped*date/time writes, nullable fields, write converters and Dapper bindingProvider matrix
datetime2->DateOnly,time(3)->TimeOnly, nulls and millisecond precisionDbType, decimal precision/scaleDateOnly/TimeOnly, nulls and millisecond precisionDbType, sizeValidation
dotnet restore ./Dapper.FluentMap.slnxdotnet build ./Dapper.FluentMap.slnx --configuration Release --no-restore— 0 warnings, 0 errorsdotnet test ./Dapper.FluentMap.slnx --configuration Release --no-build— 658 total, 583 passed, 75 expected external-provider skips, 0 failedgenerated:okCompatibility
No production API or implementation changes.
GeneratedParametersremains the only accepted parameter collection for strict-generated queries. No blanket Native AOT or unsupported provider date/time claim is introduced.Stack / merge order
This PR is intentionally based on #295, which is based on the Dapper 2.1.89 compatibility-contract work. Merge the baseline work first, then #295, then this PR. Do not merge this PR before its base.
Refs #294
Relates to #295
Upstream: DapperLib/Dapper#2225, DapperLib/Dapper#2228, DapperLib/Dapper#2233