Fix FieldClearMap service registration issue causing runtime error #3005
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.
The
FieldClearMap
was causing a runtime error when users tried to use it in their field mapping configuration:This occurred when users configured the field map in their migration settings:
The issue was that while the
FieldClearMap
class was fully implemented and documented, it was missing from the dependency injection service registration in theAddMigrationToolServicesForClientLegacyAzureDevOpsObjectModel
method.Root Cause
The
FieldMappingTool
resolves field maps from the DI container usingServices.GetRequiredService(type)
, butFieldClearMap
was not registered as a transient service like other field maps.Changes
context.AddTransient<FieldClearMap>();
to the service registration inServiceCollectionExtensions.cs
FieldClearMapOptions
configurationImpact
Users can now successfully use the FieldClearMap functionality that was already documented and implemented but previously inaccessible due to the missing service registration.
Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.