Only consider explicitly included maps

.github/workflows/ci.yml

@@ -9,12 +9,14 @@ on:
       - master
 permissions:
   contents: read
-
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
 jobs:
   build:
     strategy:
       fail-fast: false
-    runs-on: windows-2022
+    runs-on: windows-latest
     steps:
     - name: Checkout
       uses: actions/checkout@v2

.github/workflows/release.yml

@@ -11,7 +11,7 @@ jobs:
   build:
     strategy:
       fail-fast: false
-    runs-on: windows-2022
+    runs-on: windows-latest
     steps:
     - name: Checkout
       uses: actions/checkout@v2

.gitignore

@@ -32,3 +32,4 @@ project.lock.json
 # Read the Docs
 docs/_build
 /src/LastMajorVersionBinary
+*.diagsession

Build.ps1

@@ -22,15 +22,15 @@ function Exec
     }
 }
 
-$artifacts = ".\artifacts"
+$artifacts = "..\artifacts"
 
 if(Test-Path $artifacts) { Remove-Item $artifacts -Force -Recurse }
 
 exec { & dotnet clean -c Release }
 
 exec { & dotnet build -c Release }
 
-exec { & dotnet test -c Release -r $artifacts --no-build -l trx --verbosity=normal }
+exec { & dotnet test -c Release --results-directory $artifacts --no-build -l trx --verbosity=normal }
 
 exec { & dotnet pack .\src\AutoMapper\AutoMapper.csproj -c Release -o $artifacts --no-build }
 

Push.ps1

@@ -1,5 +1,5 @@
 $scriptName = $MyInvocation.MyCommand.Name
-$artifacts = "./artifacts"
+$artifacts = "../artifacts"
 
 if ([string]::IsNullOrEmpty($Env:NUGET_API_KEY)) {
     Write-Host "${scriptName}: NUGET_API_KEY is empty or not set. Skipped pushing package(s)."

docs/12.0-Upgrade-Guide.md

@@ -15,7 +15,7 @@ Another possible occurence is with `ForAllMaps` and `ForAllPropertyMaps` when it
 
 ## `ResolutionContext.Options` was removed
 
-You should use `ResolutionContext.Items` to access the items passed in the `Map` call.
+You should use `ResolutionContext.Items` to access the items passed in the `Map` call. Starting with version 12.0.1, you can use `TryGetItems` if you want to check whether a context was passed in the `Map` call.
 
 Instead of `ServiceCtor`, you should use dependency injection or pass the needed objects in the `Map` call.
 

docs/Construction.md

@@ -52,4 +52,5 @@ You can configure which constructors are considered for the destination object:
 ```c#
 // use only public constructors
 var configuration = new MapperConfiguration(cfg => cfg.ShouldUseConstructor = constructor => constructor.IsPublic);
-```
+```
+When mapping to records, consider using only public constructors.

docs/Mapping-inheritance.md

@@ -25,16 +25,19 @@ CreateMap<DerivedEntity, DerivedDto>()
     .IncludeBase<BaseEntity, BaseDto>();
 ```
 
-In each case above, the derived mapping inherits the custom mapping configuration from the base mapping configuration.
+In each case above, the derived mapping inherits the custom mapping configuration from the base map.
 
-To include all derived maps, from the base type map configuration:
+`Include`/`IncludeBase` applies recursively, so you only need to include the closest level in the hierarchy.
+
+If for some base class you have many directly derived classes, as a convenience, you can include all derived maps from the base type map configuration:
 
 ```c#
 CreateMap<BaseEntity, BaseDto>()
     .IncludeAllDerived();
 
 CreateMap<DerivedEntity, DerivedDto>();
 ```
+Note that this will search all your mappings for derived types and it will be slower than explicitly specifying the derived maps.
 
 ### Runtime polymorphism
 

docs/Queryable-Extensions.md

@@ -89,8 +89,15 @@ select new InstructorIndexData.InstructorModel
 };
 ```
 
-This map through AutoMapper will result in a SELECT N+1 problem, as each child `Course` will be queried one at a time, unless specified through your ORM to eagerly fetch. With LINQ projection, no special configuration or specification is needed with your ORM. The ORM uses the LINQ projection to build the exact SQL query needed.
-
+This map through AutoMapper will result in a SELECT N+1 problem, as each child `Course` will be queried one at a time, unless specified through your ORM to eagerly fetch. With LINQ projection, no special configuration or specification is needed with your ORM. The ORM uses the LINQ projection to build the exact SQL query needed.
+
+That means that you don't need to use explicit eager loading (`Include`) with `ProjectTo`. If you need something like filtered `Include`, have the filter in your map:
+
+```c#
+
+    CreateProjection<Entity, Dto>().ForMember(d => d.Collection, o => o.MapFrom(s => s.Collection.Where(i => ...));
+```
+
 ### Custom projection
 
 In the case where members names don't line up, or you want to create calculated property, you can use MapFrom (the expression-based overload) to supply a custom expression for a destination member:
@@ -220,7 +227,6 @@ Not supported:
 * Custom resolvers
 * Custom type converters
 * ForPath
-* Value converters
-* **Any calculated property on your domain object**
-
-Additionally, recursive or self-referencing destination types are not supported as LINQ providers do not support this. Typically hierarchical relational data models require common table expressions (CTEs) to correctly resolve a recursive join.
+* Value converters
+* Runtime polymorphic mapping with Include/IncludeBase
+* **Any calculated property on your domain object**