[#310]: Fix incorrect relocation of partner CFs with very similar NAME filters #311
Conversation
This file contains 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
…E filters Fixed situations where consecutive address claims by partners that were very similar based on NAME filters would cause an already valid partner to be overwritten with a different partner's address data. Also, locked TC example to use the primary TC.
ad3154
temporarily deployed
to
Integrate Pull Request
GitHub Actions
Inactive
|
Kudos, SonarCloud Quality Gate passed!
|
GwnDaan
approved these changes
Aug 30, 2023
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.
Fixed situations where consecutive address claims by partners that were very similar based on NAME filters would cause an already valid partner to be overwritten with a different partner's address data. Also, locked TC example to use the primary TC.
Closes #310