Reduce EstateDomainService.CreateEstateUser complexity by extracting user creation helpers#1691
Merged
StuartFerguson merged 2 commits intomasterfrom Mar 18, 2026
Merged
Conversation
Co-authored-by: StuartFerguson <16325469+StuartFerguson@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] [Complexity] Reduce cyclomatic complexity of CreateEstateUser method
Reduce Mar 18, 2026
EstateDomainService.CreateEstateUser complexity by extracting user creation helpers
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
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.
EstateDomainService.CreateEstateUserexceeded the configured cyclomatic complexity limit due to inline request construction and security-user lookup flow. This change keeps the behavior intact while splitting those branches into focused private helpers.Service refactor
BuildEstateUserRequest(...)to isolate request assembly, role override handling, and estate claim assignment.CreateEstateSecurityUser(...)to encapsulate theCreateUser+GetUserssequence and null-user failure path.CreateEstateUser(...)focused on orchestration: build request, create/fetch user, load aggregate, attach user, save aggregate.Behavior preserved
EstateRoleNameenvironment override continues to drive the assigned role.estateIdclaim is still added to the security user request.Focused coverage
CreateUserRequestand verifies the role override andestateIdclaim are still present after the refactor.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
f.feedz.io/usr/bin/dotnet dotnet test /home/REDACTED/work/TransactionProcessor/TransactionProcessor/TransactionProcessor.Tests/TransactionProcessor.Tests.csproj --filter VerifyBootstrapperIsValid --no-restore -nologo(dns block)/usr/bin/dotnet dotnet test /home/REDACTED/work/TransactionProcessor/TransactionProcessor/TransactionProcessor.BusinessLogic.Tests/TransactionProcessor.BusinessLogic.Tests.csproj --filter EstateDomainService_ --no-restore -nologo(dns block)/opt/hostedtoolcache/CodeQL/2.24.3/x64/codeql/csharp/tools/linux64/Semmle.Autobuild.CSharp /opt/hostedtoolcache/CodeQL/2.24.3/x64/codeql/csharp/tools/linux64/Semmle.Autobuild.CSharp(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.