feat: implement admin KYC review UI and server integration #165 #261
bytebindersAnnotations
10 errors and 3 warnings
|
Server
Object literal may only specify known properties, and 'entryHash' does not exist in type 'WalletKeyAccessAuditSelect<DefaultArgs>'.
|
|
Server
Argument of type '{ id: string; userId: string; publicKey: string; encryptedSecretKey: string; encryptionVersion: number; createdAt: Date; updatedAt: Date; }' is not assignable to parameter of type '{ id: string; publicKey: string; encryptionVersion: number; createdAt: Date; lastRotatedAt: Date | null; }'.
|
|
Server
Object literal may only specify known properties, but 'encryptedSecretKeyVersion' does not exist in type '(Without<UserWalletUpdateInput, UserWalletUncheckedUpdateInput> & UserWalletUncheckedUpdateInput) | (Without<...> & UserWalletUpdateInput)'. Did you mean to write 'encryptedSecretKey'?
|
|
Server
Argument of type '{ id: string; userId: string; publicKey: string; encryptedSecretKey: string; encryptionVersion: number; createdAt: Date; updatedAt: Date; }' is not assignable to parameter of type '{ id: string; publicKey: string; encryptionVersion: number; createdAt: Date; lastRotatedAt: Date | null; }'.
|
|
Server
Object literal may only specify known properties, but 'encryptedSecretKeyVersion' does not exist in type '(Without<UserWalletUpdateInput, UserWalletUncheckedUpdateInput> & UserWalletUncheckedUpdateInput) | (Without<...> & UserWalletUpdateInput)'. Did you mean to write 'encryptedSecretKey'?
|
|
Server
Argument of type '{ id: string; userId: string; publicKey: string; encryptedSecretKey: string; encryptionVersion: number; createdAt: Date; updatedAt: Date; }' is not assignable to parameter of type '{ id: string; publicKey: string; encryptionVersion: number; createdAt: Date; lastRotatedAt: Date | null; }'.
|
|
Server
Argument of type '{ id: string; userId: string; publicKey: string; encryptedSecretKey: string; encryptionVersion: number; createdAt: Date; updatedAt: Date; }' is not assignable to parameter of type '{ id: string; publicKey: string; encryptionVersion: number; createdAt: Date; lastRotatedAt: Date | null; }'.
|
|
Server
Argument of type '{ id: string; userId: string; publicKey: string; encryptedSecretKey: string; encryptionVersion: number; createdAt: Date; updatedAt: Date; }' is not assignable to parameter of type '{ id: string; publicKey: string; encryptionVersion: number; createdAt: Date; lastRotatedAt: Date | null; }'.
|
|
Server
Object literal may only specify known properties, but 'encryptedSecretKeyVersion' does not exist in type 'Without<UserWalletCreateInput, UserWalletUncheckedCreateInput> & UserWalletUncheckedCreateInput'. Did you mean to write 'encryptedSecretKey'?
|
|
Server
Argument of type '{ id: string; userId: string; publicKey: string; encryptedSecretKey: string; encryptionVersion: number; createdAt: Date; updatedAt: Date; }' is not assignable to parameter of type '{ id: string; publicKey: string; encryptionVersion: number; createdAt: Date; lastRotatedAt: Date | null; }'.
|
|
Server
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Frontend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Contracts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|