fix(ParticipantResolver): fix duplicate organizations in participant resolution - #21
Merged
Merged
Conversation
Mortega5
approved these changes
Jun 25, 2026
wistefan
approved these changes
Jun 25, 2026
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
3 participants
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.
ParticipantResolver.getTmfId used Optional.orElse(createOrganization(did)), which eagerly evaluates createOrganization on every call and POSTs a new org even when one already exists. Switch to orElseGet so creation is lazy.
Also paginate OrganizationApiClient.getByDid: the TMForum query only filters by characteristic name, so a matching org beyond the first page was missed and re-created. Page through results until matched or exhausted.