Bug fix for lame FieldDefinitionNotExistException #2626
Merged
Conversation
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
…xception when setting ClosedDate field Wraps the assignment of the "ClosedDate" field in a try-catch block to handle the FieldDefinitionNotExistException. This change prevents the application from crashing when the field definition does not exist, which can occur due to inconsistencies in the TFS API. The exception is caught and ignored to ensure the migration process continues smoothly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
🐛 (TfsWorkItemMigrationProcessor.cs): handle FieldDefinitionNotExistException when setting ClosedDate field
Wraps the assignment of the "ClosedDate" field in a try-catch block to handle the FieldDefinitionNotExistException. This change prevents the application from crashing when the field definition does not exist, which can occur due to inconsistencies in the TFS API. The exception is caught and ignored to ensure the migration process continues smoothly.
Co-Authored: @anderssonpof