🎯 AutoMapper Roslyn Analyzer

✨ Catch AutoMapper configuration errors before they cause runtime chaos
A sophisticated Roslyn analyzer that transforms AutoMapper development from reactive debugging to proactive prevention

---

🎉 Latest Release: v2.30.86

AM020 side-effect-safe computed-receiver fixes

✅ Highlights

• AM020 now captures semantically proven computed IMapperConfigurationExpression receivers exactly once before replaying the original map and appending missing nested registrations. Property, method-call, indexer, parenthesized, conditional, and ReverseMap() receiver shapes are supported without duplicating side effects.
• Stable receivers remain unchanged, while conditional access, unresolved/dynamic receivers, deferred or nested mappings, non-void expression bodies, stale diagnostics, and conditional-compilation regions remain conservatively fixless.

🧪 Validation

• AM020 suite: 122 passed; full suite: 1771 passed on net10.0; catalog, sample snapshots, and compatibility checks passed.

Recent Releases

• v2.30.86: AM020 captures computed IMapperConfigurationExpression receivers exactly once before adding missing nested maps, extending safe fixes to property, method-call, indexed, parenthesized, and conditional receiver shapes.
• v2.30.85: AM021 withholds ineffective element-map fixes for nested collection and array element shapes; test and coverage dependencies were refreshed.
• v2.30.84: New AM060 flags Map/ProjectTo calls with no reachable CreateMap registration (with a profile-scaffolding fix); new AM061 flags enum member name/value misalignment that silently corrupts mapped data.
• v2.30.83: AM021 preserves exact BCL Stack<T> LIFO order in generated element-conversion fixes.
• v2.30.82: AM021 restricts complex element-map insertion to direct, unconditional constructor/method statements while retaining Ignore for nested, deferred, or conditional-region mappings.
• v2.30.81: AM020 withholds constructor/method block insertion inside or across conditional regions while preserving fixes after completed conditional regions.
• v2.30.80: AM020 converts direct expression-bodied void methods into executable blocks while retaining strict return, ownership, receiver, and trivia-safety gates.
• v2.30.79: AM020 converts expression-bodied Profile constructors into executable blocks before appending a missing nested map.
• v2.30.78: AM020 preserves stable external configuration receivers for missing nested-map fixes while withholding computed receiver rewrites.
• v2.30.77: AM041 excludes proven mutually exclusive if/else registration alternatives while preserving diagnostics for independent or unconditional duplicates.
• v2.30.76: AM022 honors deferred root MaxDepth, PreserveReferences, and ConvertUsing configuration through direct mapping locals while retaining direction and duplicate ambiguity boundaries.
• v2.30.75: AM022 follows direct constructor-owned recursion edges, distinguishes safe mixed-path MaxDepth from unsafe construction-only recursion, and withholds ineffective constructor-owned fixes.
• v2.30.74: AM002 respects exact semantic ForCtorParam null-safety ownership, propagates synchronous helper mutations and conditional iterator provenance, requires semantic/unconditional null-safety configuration, tracks nested variance polarity, and repairs unsafe constructor inputs in place.
• v2.30.73: AM041 detects direct local deferred ReverseMap() registrations, including fluent initializers, and removes duplicate standalone calls safely.
• v2.30.72: AM001 respects exact semantic ForCtorParam ownership for positional-record mismatches and withholds stale fixes.
• v2.30.71: AM022 follows unique direct renamed member maps throughout the configured cycle graph while downstream ForMember/ForPath Ignore overrides remove broken edges.
• v2.30.70: AM022 detects direct renamed ForMember(...MapFrom...) cycle edges and emits an effective Ignore alternative.
• v2.30.69: AM032 makes nullable-destination null propagation primary while retaining the throw policy.
• v2.30.68: AM011 single-property fixes stop manufacturing required domain data when no unique fuzzy source match exists.
• v2.30.67: AM031 and AM034–AM038 add executable ForPath Ignore scaffolds while preserving conservative cache/removal boundaries.
• v2.30.66: AM022 respects direction-aware downstream cycle breakers in multi-map recursion graphs.
• v2.30.65: AM004/AM006 same-document sibling recompute for aggregates.
• v2.30.64: AM001 property-token diagnostic placement + aggregate sibling recompute.
• v2.30.63: AM022 graph-aware Ignore for multi-type cycles.
• v2.30.62: Split AM031 performance concepts into AM031 + AM034–AM038.
• v2.30.61: Fixer UX Batch 3 — AM031 best-first Remove/Ignore, AM003/AM021 escape + titles, AM032 net48-safe guard emit.
• v2.30.60: Fixer UX Batch 2 — AM001 multi-property Convert-all/Ignore-all, AM022 MaxDepth best-first, shared AddUsingIfMissing.
• v2.30.59: Fixer UX honesty — AM011 Map-all/Scaffold-all honesty, manual-review aggregate titles, no silent no-op lightbulbs for AM020/AM021/AM031, AM022 MaxDepth scaffold title.
• v2.30.58: AM001 ReverseMap direction keys, Nullable scalar reporting, fixer culture/null/keyword/framework conversion hardening.
• v2.30.57: Full analyzer+fixer audit hardening — AM003/AM021 ownership, AM020 internal fixer parity, AM021 Parse gate, AM041 paren reverse, AM011 reverse fuzzy, AM031 multi-enum all keys, docs/trust honesty.
• v2.30.56: Analyzer hitlist hardening — AM004 unique-best fuzzy gate, AM032 nullable pass-through suppression, AM003 sample isolation, AM001↔AM002 ownership tests, AM030 signature-depth regressions.
• v2.30.55: Analyzer health full reanalysis — refreshed scorecard and Fixer Trust Summary; no analyzer/fixer/test source changes.
• v2.30.54: Analyzer precision and regression hardening — expands typed/string/nameof(...)/const explicit configuration handling, typed ForPath and ConvertUsing coverage, converter guard recognition, duplicate-map and reverse-map boundaries, collection conversion axes, exact BCL performance heuristics, and safer automatic code-fix selection across the implemented rule set.
• v2.30.53: AM032 conditional-access null-handling precision — unsafe invocation/constructor arguments, primitive parse targets, explicit and target-typed Uri constructors, simple-local unsafe arguments, explicit/null-forgiven null coalesce fallbacks, coalesced guards whose null fallback enters unsafe branches, late guarded-local checks after unsafe source use, maybe-null local member dereferences, and nested-helper-only guards report while TryParse success/fallback flows, nullable parse provider/style arguments, null-tolerant argument targets, boolean guard locals, source-free fallback assignments, boolean switch-statement fallbacks, split-assigned guarded locals, and nullable fallback returns stay quiet.
• v2.30.52: AM006/AM004 aggregate + nested "Fix individual…" code-fix actions — keeps the lightbulb short when many properties pile onto one CreateMap (metadata model types).
• v2.30.51: AM011 nested "Fix individual required property…" submenu — keeps the lightbulb short when many required members are unmapped.
• v2.30.50: AM011 aggregate "Map all / Ignore all" code-fix actions — fix every unmapped required property of a CreateMap in a single action.
• v2.30.49: AM021 dictionary key/value decomposition (removes a false positive, adds ToDictionary/element-CreateMap fixes) and AM002 collection element nullability detection.
• v2.30.48: AM021 simple element-conversion fixes now cover destination ImmutableArray<T> collections with fully qualified ImmutableArray.CreateRange(...) mappings.
• v2.30.47: AM003 now covers ImmutableArray<T> container mismatches and offers ImmutableArray.CreateRange(...) for destination immutable arrays.
• v2.30.46: AM050 now covers redundant top-level ForPath MapFrom mappings and removes them with the same safe single-call rewrite guard as ForMember.
• v2.30.45: AM031 tracks SequenceEqual as a terminal enumeration, counts both sequence inputs, and keys static LINQ terminals to their source sequence arguments.
• v2.30.44: AM031 multiple-enumeration tracking now covers Contains, ElementAt, ElementAtOrDefault, and common linear collection instance Contains calls.
• v2.30.43: AM031 reports GetAwaiter().GetResult() sync-over-async mapping expressions across Task, configured Task, ValueTask, and configured ValueTask awaiters.
• v2.30.42: AM020 now respects compiler-known implicit nested conversions, while explicit-only nested conversions still report.
• v2.30.41: AM021 now respects compiler-known implicit element conversions, including value-object collection elements, while explicit-only element conversions still report.
• v2.30.40: AM001 now respects compiler-known implicit conversions, including user-defined value-object conversions, while explicit-only conversions still report.
• v2.30.39: Refreshed CI, release, and CodeQL workflow action pins to current major versions with Node.js 24-compatible releases.
• v2.30.38: AM031 complex LINQ SelectMany diagnostics now require real System.Linq.Enumerable/Queryable calls, so user-defined namesakes with nested selector logic stay quiet.
• v2.30.37: AM001 uses the exact C# implicit numeric conversion table, reports double/float to decimal mappings, and preserves valid widenings such as char to int.
• v2.30.36: AM002 preserves constructed generic type labels in nullable diagnostics and uses default! for generic/reference fallback defaults in generated fixes.
• v2.30.35: Split AM030's mixed converter diagnostics into AM030 invalid implementation, AM032 null handling, and AM033 unused converter rules with independent docs, severities, and trust metadata.
• v2.30.34: Calibrated AM021's analyzer-health Tests score to 5, aligning it with AM022 based on comparable analyzer coverage and stronger AM021 code-fix method count.
• v2.30.33: AM003 detects immutable/frozen destination container mismatches and offers fully qualified factory fixes for ImmutableList<T>, ImmutableHashSet<T>, and FrozenSet<T>.
• v2.30.32: AM004/AM006 diagnostics now point at the offending source/destination property identifiers while preserving code-fix routing through mapping invocation metadata.
• v2.30.31: Correctness/code-fix hardening from an adversarial audit — AM001 signed/unsigned numeric mismatches, keyword-name escaping, AM020 qualified/generic nested CreateMap names, AM003 implicit-conversion-gated element casts, AM031 ValueTask.Result.
• v2.30.30: Added AM021 simple-conversion fixes for ImmutableList<T>, ImmutableHashSet<T>, and FrozenSet<T> while keeping custom immutable-lookalikes manual-only.
• v2.30.29: Hardened AM003 custom collection fixer safety while preserving safe BCL collection constructor rewrites.
• v2.30.28: Tightened AM031 and AM001 fixer action selection so automatic rewrites stay executable and behavior-preserving.
• v2.30.27: Added a direct AM041 test locking the ForPath chained-configuration withhold behavior alongside the existing ForMember/parenthesized/ReverseMap()-chained coverage.
• v2.30.26: Locked AM050 sibling-config withhold behavior with direct PreCondition/UseDestinationValue/Ignore regression tests alongside the existing Condition/NullSubstitute cases.
• v2.30.25: Corrected six AM002/AM011/AM020/AM021/AM022/AM030 rule-docs category lines to match the shipped descriptor categories and added a category drift guard that prevents future doc/descriptor drift.
• v2.30.24: Marked unwired AM003/AM030 DiagnosticDescriptor relics [Obsolete] (binary compatibility preserved) and added a trust drift guard that fails when any shipped analyzer declares a DiagnosticDescriptor field outside its SupportedDiagnostics without an explicit Obsolete attribute.
• v2.30.23: AM050 code fix is withheld when the redundant-MapFrom ForMember lambda contains sibling configuration (Condition, NullSubstitute, …) that would otherwise be dropped.
• v2.30.22: AM031 normalises chained pre-terminal LINQ receivers so multiple enumerations of the same source-rooted collection report.
• v2.30.21: AM050 redundant-MapFrom detection now also fires on parenthesized and typed lambdas such as o.MapFrom((Source s) => s.Name).
• v2.30.20: AM030 recognises ArgumentNullException.ThrowIfNull, ArgumentException.ThrowIfNullOrEmpty, and ArgumentException.ThrowIfNullOrWhiteSpace as null guards on the converter's source parameter.
• v2.30.19: AM030 stops reporting concrete converters as unused when a matching ITypeConverter<TSource, TDestination> is passed to ConvertUsing through DI/service-locator shapes.
• v2.30.18: AM031 multiple-enumeration tracking covers Min, Max, Aggregate, LongCount, Single, SingleOrDefault, ToHashSet, ToDictionary, and ToLookup, with a System.Linq.Enumerable/Queryable namesake gate.
• v2.30.17: AM041 withholds the duplicate-removal fix when the duplicate CreateMap<>() carries chained mapping policy.
• v2.30.16: Analyzer precision hardening across AM002, AM006, AM021, AM031, and AM041.
• v2.30.15: Fixer UX trust hardening with descriptor-specific no-fix metadata and executable interface collection rewrites.
• v2.30.14: AM021 reverse-map collection element diagnostics catch missing reverse element maps without duplicate noise.
• v2.30.13: AM041 duplicate-map labels now preserve generic type arguments and array ranks.
• v2.30.12: AM030 interface-typed converter usage and AM021 dictionary fixer safety.
• v2.30.11: AM001 enum/string conversion fixes for direct property mismatch remediation.
• v2.30.10: AM050 proven redundant MapFrom cleanup for string-based members and type-safe suppressions.
• v2.30.9: AM004/AM005 severity documentation trust with descriptor-aligned rule docs.
• v2.30.8: AM030 null-guard fixer precision without invasive using System edits.
• v2.30.7: AM022 recursion boundary precision for nested-map chains and explicit recursion controls.
• v2.30.6: AM031 source collection cache precision with nested source paths and Task-property .Result coverage.
• v2.30.5: AM030 type-based converter usage precision for ConvertUsing(typeof(...)).
• v2.30.4: AM022 mapped recursion precision with unrelated-cycle false-positive reductions.
• v2.30.3: AM011 ForPath required-member boundary with explicit configuration coverage.
• v2.30.2: AM003 assignable collection boundary suppression with targeted regression coverage.
• v2.30.1: AM002 nullability contract alignment with descriptor-accurate docs and nullable-context regression coverage.
• v2.30.0: Fixer hardening for AM001, AM005, AM006, AM011, and AM021 with safer action selection.
• v2.29.0: Smart primary fix and reduced fixer noise across the main data-integrity fixers.
• v2.28.2: False-positive reduction, fixer UX improvements, and release workflow hardening.
• v2.28.1: Case-aware AM021 suppression and fixer reliability improvements.
• v2.28.0: Analyzer logic fixes and performance improvements.
• v2.27.0: AM050 nullable safety fix and broad regression coverage expansion.
• v2.25.0: Code-fix consolidation and sample verification.

---

🌟 Why This Matters

AutoMapper is powerful, but silent failures are its Achilles' heel. Properties that don't map, type mismatches that throw at runtime, nullable violations that cause NullReferenceExceptions—these issues typically surface in production, not during development.

This analyzer changes that equation entirely.

// Before: 😰 Runtime surprise!
public void MapUserData()
{
    var user = mapper.Map<UserDto>(userEntity); 
    // 💥 NullReferenceException in production
    // 💥 Data loss from unmapped properties  
    // 💥 Type conversion failures
}

// After: 🛡️ Compile-time confidence!
public void MapUserData() 
{
    var user = mapper.Map<UserDto>(userEntity);
    // ✅ All mapping issues caught at compile-time
    // ✅ Code fixes suggest proper solutions
    // ✅ Ship with confidence
}

---

⚡ Quick Start

# Install via .NET CLI
dotnet add package AutoMapperAnalyzer.Analyzers

# Or via Package Manager Console
Install-Package AutoMapperAnalyzer.Analyzers

That's it! The analyzer automatically activates and starts checking your AutoMapper configurations. Open any file with AutoMapper mappings and see diagnostics appear instantly.

See the executable package compatibility contract for the exact target-framework and AutoMapper version pairings verified before release.

See it work:

var config = new MapperConfiguration(cfg =>
{
    cfg.CreateMap<User, UserDto>();
    //  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ AM001: Property 'Age' type mismatch
    //  💡 Press Ctrl+. for code fix suggestions
});

---

🚀 What You Get

🛡️ Complete Type Safety

• AM001: Property type mismatches with smart conversion suggestions
• AM002: Nullable-to-non-nullable mapping with null safety patterns
• AM003: Collection type incompatibility detection

🔍 Zero Data Loss

• AM004: Missing destination properties (prevent silent data loss)
• AM006: Unmapped destination properties (detect unintentional defaults)
• AM011: Required property validation (avoid runtime exceptions)
• AM005: Case sensitivity issues (cross-platform reliability)

🧩 Complex Mapping Intelligence

• AM020: Nested object mapping validation with receiver-preserving CreateMap suggestions (supports internal properties, cross-profile detection, stable and capture-once external configuration receivers, and direct expression-bodied constructors/void methods)
• AM021: Collection element type analysis with conversion strategies
• AM022: Circular reference detection with MaxDepth recommendations
• AM030/AM032/AM033: Custom type converter implementation, null safety, and usage validation

⚡ Instant Code Fixes

Every analyzer comes with intelligent code fixes that don't just identify problems—they solve them:

// Problem detected ⚠️
cfg.CreateMap<Source, Dest>();
//    ~~~~~~~~~~~~~~~~~~~~~~~~~ AM001: Property 'Age' type mismatch

// Code fix applied ✨
cfg.CreateMap<Source, Dest>()
   .ForMember(dest => dest.Age, opt => opt.MapFrom(src => 
       int.TryParse(src.Age, out var age) ? age : 0));

---

🎯 Real-World Impact

	Before	After
🐛	Runtime mapping failures	✅ Compile-time validation
🔍	Manual debugging sessions	✅ Instant error highlights
📝	Guessing correct configurations	✅ Code fixes with best practices
⚠️	Production NullReferenceExceptions	✅ Null safety enforcement
📊	Silent data loss	✅ Missing property detection
🌐	Cross-platform mapping inconsistencies	✅ Case sensitivity validation

---

📦 Installation

.NET CLI (Recommended)

dotnet add package AutoMapperAnalyzer.Analyzers

Package Manager Console

Install-Package AutoMapperAnalyzer.Analyzers

Project File (For CI/CD)

<PackageReference Include="AutoMapperAnalyzer.Analyzers" Version="2.30.86">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>

⚡ Universal Compatibility

Platform	Version	Support	AutoMapper	CI/CD Status
.NET Framework	4.8+	🟢 Full	10.1.1+	✅ Tested
.NET	6.0+	🟢 Full	12.0.1+	✅ Tested
.NET	8.0+	🟢 Full	14.0.0+	✅ Tested
.NET	9.0+	🟢 Full	14.0.0+	✅ Tested
.NET	10.0+	🟢 Full	14.0.0+	✅ Tested

Analyzer targets .NET Standard 2.0 for maximum compatibility
All platforms validated in automated CI/CD pipeline

---

🎨 See It In Action

❌ The Problems

public class UserEntity
{
    public int Id { get; set; }
    public string? FirstName { get; set; }  // Nullable
    public string LastName { get; set; }
    public string Email { get; set; }
    public DateTime CreatedAt { get; set; }
    public List<string> Tags { get; set; }  // Collection type
    public Address HomeAddress { get; set; }  // Complex object
}

public class UserDto  
{
    public int Id { get; set; }
    public string FirstName { get; set; }    // Non-nullable!
    public string FullName { get; set; }     // Different property!  
    public string Age { get; set; }          // Different type!
    public HashSet<int> Tags { get; set; }   // Incompatible collection!
    public AddressDto HomeAddress { get; set; }  // Needs explicit mapping!
}

// This configuration has MULTIPLE issues:
cfg.CreateMap<UserEntity, UserDto>();
//  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
//  🚨 AM002: FirstName nullable→non-nullable (NullReferenceException risk)
//  🚨 AM004: LastName will not be mapped (data loss)  
//  🚨 AM001: Age expects int but gets DateTime (runtime exception)
//  🚨 AM021: Tags List<string>→HashSet<int> incompatible (mapping failure)
//  🚨 AM020: HomeAddress→AddressDto needs CreateMap (runtime exception)

✅ The Solutions (Auto-Generated!)

// Code fixes automatically suggest:
cfg.CreateMap<UserEntity, UserDto>()
   .ForMember(dest => dest.FirstName, opt => opt.MapFrom(src => src.FirstName ?? ""))
   .ForMember(dest => dest.FullName, opt => opt.MapFrom(src => $"{src.FirstName} {src.LastName}"))  
   .ForMember(dest => dest.Age, opt => opt.MapFrom(src => 
       DateTime.Now.Year - src.CreatedAt.Year))
   .ForMember(dest => dest.Tags, opt => opt.MapFrom(src => 
       src.Tags.Select((tag, index) => index).ToHashSet()));

// Separate mapping for complex types  
cfg.CreateMap<Address, AddressDto>();

---

⚙️ Fine-Tuned Control

Severity Configuration (.editorconfig)

# Treat type safety as build errors
dotnet_diagnostic.AM001.severity = error
dotnet_diagnostic.AM002.severity = error  
dotnet_diagnostic.AM011.severity = error

# Data loss warnings  
dotnet_diagnostic.AM004.severity = warning
dotnet_diagnostic.AM005.severity = warning

# Suggestions for optimization
dotnet_diagnostic.AM020.severity = suggestion
dotnet_diagnostic.AM021.severity = suggestion  

Selective Suppression

// Suppress with clear justification
#pragma warning disable AM001 // Custom IValueConverter handles string→int
cfg.CreateMap<Source, Dest>();
#pragma warning restore AM001

// Method-level suppression
[SuppressMessage("AutoMapper", "AM004:Missing destination property",
    Justification = "PII data intentionally excluded for GDPR compliance")]
public void ConfigureSafeUserMapping() { }

---

📊 Complete Analyzer Coverage

Rule	Description	Analyzer	Code Fix	Severity
🔒 Type Safety
AM001	Property Type Mismatch	✅	✅	Error
AM002	Nullable→Non-nullable	✅	✅	Error / Info
AM003	Collection Incompatibility	✅	✅	Error
AM061	Enum Member Mismatch	✅	✅	Warning
📊 Data Integrity
AM004	Missing Destination Property	✅	✅	Warning
AM005	Case Sensitivity Issues	✅	✅	Warning
AM006	Unmapped Destination Property	✅	✅	Info
AM011	Required Property Missing	✅	✅	Error
🧩 Complex Mappings
AM020	Nested Object Issues	✅	✅	Warning
AM021	Collection Element Mismatch	✅	✅	Warning
AM022	Circular Reference Risk	✅	✅	Warning
AM030	Invalid Type Converter Implementation	✅	—	Error
AM032	Type Converter Null Handling	✅	✅	Warning
AM033	Unused Type Converter	✅	—	Info
⚡ Performance
AM031	Multiple Enumeration	✅	✅	Warning
AM034	Expensive Operation	✅	✅	Warning
AM035	Expensive Computation	✅	✅	Warning
AM036	Sync-Over-Async	✅	✅	Warning
AM037	Complex LINQ	✅	✅	Warning
AM038	Non-Deterministic Operation	✅	✅	Info
⚙️ Configuration
AM041	Duplicate Mapping Registration	✅	✅	Warning
AM050	Redundant MapFrom	✅	✅	Info
AM060	Unregistered Type Map	✅	✅	Warning
🚀 Future
AM040+	Additional configuration rules	🔮	🔮	-
AM050+	Advanced Optimizations	🔮	🔮	-

---

🛠️ Development Experience

IDE Integration

• Visual Studio: Full IntelliSense integration with lightbulb code fixes
• VS Code: Rich diagnostic experience via OmniSharp
• JetBrains Rider: Native analyzer support with quick-fix suggestions
• Command Line: Works seamlessly with dotnet build

Testing Your Configuration

# Quick validation
dotnet build  # Analyzer runs automatically

# Comprehensive testing
git clone https://github.com/georgepwall1991/automapper-analyser.git
cd automapper-analyser
dotnet run --project samples/AutoMapperAnalyzer.Samples

# See all analyzer warnings in action
dotnet build samples/ --verbosity normal

# Run full test suite with coverage
dotnet test --collect:"XPlat Code Coverage" --settings coverlet.runsettings

CI/CD & Quality Assurance

• 🔄 Automated Testing: Every commit tested across multiple .NET versions
• 📊 Code Coverage: Integrated with Codecov for comprehensive coverage tracking
• 🛡️ Quality Gates: Build fails only on genuine errors, warnings are preserved
• ⚡ Cross-Platform: Validated on Ubuntu (CI) and Windows (compatibility tests)
• 📈 Performance: Incremental builds with analyzer caching for optimal speed

---

🏗️ Architecture Highlights

This isn't just another analyzer—it's built for enterprise-grade reliability:

• 🏎️ Performance-First: Incremental analysis with minimal IDE impact
• 🔧 Extensible Design: Clean plugin architecture for new rules
• 🧪 Battle-Tested: release validation includes full suite coverage plus targeted regression tests for high-risk fixers
• 🌐 Cross-Platform: Identical behavior on Windows, macOS, Linux
• ⚡ CI/CD Ready: Automated GitHub Actions with codecov integration
• 📊 Code Coverage: 55%+ coverage with comprehensive testing

---

🎯 What's Next

Recently Completed ✅

• v2.30.15: Fixer UX trust hardening with descriptor-specific no-fix metadata and executable interface collection rewrites
• v2.30.14: AM021 reverse-map collection element diagnostics catch missing reverse element maps without duplicate noise
• v2.30.13: AM041 duplicate-map labels preserve generic type arguments and array ranks
• v2.30.12: AM030 interface-typed converter usage and AM021 dictionary fixer safety
• v2.30.11: AM001 enum/string conversion fixes for direct property mismatch remediation
• v2.30.10: AM050 proven redundant MapFrom cleanup for string-based members and type-safe suppressions
• v2.30.9: AM004/AM005 severity documentation trust with descriptor-aligned rule docs
• v2.30.8: AM030 null-guard fixer precision without invasive using System edits
• v2.30.7: AM022 recursion boundary precision for nested-map chains and explicit recursion controls
• v2.30.6: AM031 source collection cache precision with nested source paths and Task-property .Result coverage
• v2.30.5: AM030 type-based converter usage precision for ConvertUsing(typeof(...))
• v2.30.4: AM022 mapped recursion precision with unrelated-cycle false-positive reductions
• v2.30.3: AM011 ForPath required-member boundary with explicit-configuration regression coverage
• v2.30.2: AM003 assignable collection boundary suppression with targeted regression coverage
• v2.30.1: AM002 nullability contract alignment with descriptor-accurate docs and nullable-context regression coverage
• v2.30.0: Fixer hardening for AM001, AM005, AM006, AM011, and AM021 with safer action selection
• v2.29.0: Smart Primary Fix — reduced fixer noise to max 2 lightbulb options per diagnostic
• v2.28.2: False-positive reduction, fixer UX improvements, and release workflow hardening
• v2.28.1: Case-aware AM021 suppression and fixer accuracy improvements
• v2.28.0: Analyzer logic fixes and performance improvements
• v2.27.0: AM050 nullable safety fix and expanded regression coverage

Phase 5B: Performance split (shipped in v2.30.62)

• AM031 / AM034–AM038: Independent performance rule IDs (multiple enumeration, expensive ops, computation, sync-over-async, complex LINQ, non-determinism)

Phase 6: Configuration & Profile Analysis

• AM040+: Additional profile/configuration analysis

Beyond Code Analysis

• NuGet Package Templates: Project templates with pre-configured analyzers
• MSBuild Integration: Custom build targets for mapping validation
• Documentation Generation: Auto-generate mapping documentation
• Metrics Dashboard: Build-time analysis reporting

---

🤝 Contributing

We're building something special, and your expertise makes it better.

Quick Start Contributing:

git clone https://github.com/georgepwall1991/automapper-analyser.git
cd automapper-analyser
dotnet test

What We Need:

• 🧪 More edge-case scenarios
• 📝 Documentation improvements
• 🚀 Performance optimizations
• 💡 New analyzer rule ideas

See our Contributing Guide for detailed guidelines.

---

📚 Deep Dive Resources

• 📖 Architecture Guide - How it all works under the hood
• 🔍 Diagnostic Rules - Complete rule reference
• 🧭 Generated Rule Catalog - Descriptor, fixer, sample, and trust-level source of truth
• 🧪 Sample Gallery - Real-world scenarios
• 🚀 CI/CD Pipeline - Our build and deployment process
• 📊 Compatibility Matrix - Framework support details

---

💬 Community & Support

Get Help:

• 🐛 Issues - Bug reports and feature requests
• 💬 Discussions - Questions and ideas
• 📖 Wiki - Comprehensive documentation

📄 License

MIT License - Use it anywhere, contribute back if you can.

---

⭐ Star this repo if it's saving you time!

Built with ❤️ by developers who've debugged too many AutoMapper issues

🚀 Get Started Now • 📖 Read the Docs • 💬 **Join the Discussion **