Merged
Conversation
github-actions
bot
requested review from
TaprootFreak and
davidleomay
as code owners
* [DEV-4546] SupportIssue type VerificationCall * [DEV-4546] Set department * [DEV-4546] add phoneCallTimes and phoneCallStatus * [DEV-4546] remove unused code * [DEV-4546] remove more unused code * [DEV-4546] auto set PhoneCallStatus with supportIssue * [DEV-4546] Refactoring * [DEV-4546] add migration * [DEV-4546] add new amlReason * [DEV-4546] Rename enum * [DEV-4546] Refactoring * [DEV-4546] Restructuring * [DEV-4546] add phoneCall in user get endpoint * [DEV-4546] Refactoring * [DEV-4546] Refactoring 2 * [DEV-4546] Refactoring 3 * [DEV-4546] Rename status * [DEV-4546] Refactoring 4 * [DEV-4546] fix bug * [DEV-4546] Add anchor in failed mails
* [NOTASK] move phoneCall to v2 user dto * [NOTASK] fix build
* Add recommendation network graph API and enriched KYC step data - Add BFS-based recommendation graph endpoint that traverses the entire connected network in both directions (recommender and recommended) - Enrich KYC step support info with recommender/recommended user data and all recommendations by the same recommender - Add recommendation lookup by kycStepId with fallback to recommendedId for mail invitations where kycStepId is null * Harden recommendation graph: add node cap and batch user loading - Cap BFS traversal at 500 nodes to prevent unbounded graph traversal - Replace N individual getUserData calls with single batch query via getUserDataByIds using IN clause - Remove direct UserDataRepository dependency from SupportService * Fix prettier formatting
…rror (#3406) * fix: load kycSteps relation in updateUser to prevent duplicate step error updateUserV1 and updateUser did not load the kycSteps relation on userData. When updatePhone called createCustomKycStep, getNextSequenceNumber returned 0 (empty kycSteps array) instead of the correct next value, causing a unique index violation on repeated phone changes. * fix: load kycSteps in updatePhone before creating audit step When updatePhone calls createCustomKycStep, getNextSequenceNumber needs the kycSteps relation to compute the correct sequence number. If kycSteps is not loaded (e.g. when called from updateUserSettings), it returns 0, causing a unique index violation on repeated phone changes. Load kycSteps on demand in updatePhone via getStepsByUserData, only when createStep is true and kycSteps is not already loaded. This follows the same pattern used in cron jobs and avoids loading kycSteps unnecessarily in the outer user update queries.
TaprootFreak
previously approved these changes
Mar 13, 2026
TaprootFreak
approved these changes
Mar 13, 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
4 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.
Automatic Release PR
This PR was automatically created after changes were pushed to develop.
Commits: 1 new commit(s)
Checklist