feat(support): KYC-Level im User-Suchergebnis ergänzen#3980
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
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.
Was
Das Suchergebnis des Support-/Compliance-Such-Endpoints (
GET /support?key=) liefert pro Kunde neu daskycLevel.UserDataSupportInfo(DTO): FeldkycLevel?: numberergänztSupportService.toUserDataDto:kycLevelaus derUserData-Entity gemapptWarum
Im Compliance-Frontend soll das KYC-Level direkt in der Trefferliste sichtbar sein, ohne zuerst die Detailseite öffnen zu müssen. Das Feld existiert bereits auf der
UserData-Entity und wird in anderen Support-DTOs (Pending Transactions, Detailansicht) bereits genauso gemappt.Migration
Keine —
kycLevelist bereits eine bestehende Entity-Spalte; sie wird lediglich zusätzlich im DTO ausgegeben.Tests
type-check,format:check,lintlokal grün (node 20.20.2)UserDataSupportInfoHinweis
Die konsumierende Frontend-Änderung (neue Spalte) folgt separat. Bis zum DEV-Deploy dieses PRs zeigt das Frontend dort
-.