feat: add holding capacity precheck endpoint - #924
PEPPERITO23 wants to merge 4 commits into
Conversation
|
@PEPPERITO23 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
@accesslayerorg Implemented issue #913 with an unauthenticated holding-capacity precheck endpoint, validated wallet/quantity inputs, key-not-found handling, cap calculations, and boundary tests. |
|
@accesslayerorg @PEPPERITO23 The latest upstream main already contains the holding-capacity implementation and tests in |
|
@accesslayerorg @PEPPERITO23 AccessLayer #913 is implemented in commit ff1dfd8. PR #924 was reopened, its body now contains Fixes #913, and the endpoint provides the unauthenticated holding-capacity pre-check with validation, latest ownership lookup, cap calculation, and tests. Please review and merge. |
|
@accesslayerorg @PEPPERITO23 Fixed and pushed in commit |
|
@accesslayerorg @PEPPERITO23 I refreshed the exact PR head after verifying that the current base commit is already included and the local merge is conflict-free. Pushed |
|
Conflict |
# Conflicts: # src/modules/keys/keys.routes.ts
|
Hi @Chucks1093, the merge conflict is resolved against the latest main and CI is passing. Could you please review and merge this PR when you have a chance? Thanks. |
Summary
Verification
tsc --noEmitpassed after Prisma client generation.git diff --checkpassed.Fixes #913