Skip to content

fix: resolve CI build errors (config schema duplicate, UNPROCESSABLE_ENTITY, keyId param) - #856

Open
yugomania wants to merge 2 commits into
accesslayerorg:mainfrom
yugomania:fix/ci-build-errors
Open

fix: resolve CI build errors (config schema duplicate, UNPROCESSABLE_ENTITY, keyId param)#856
yugomania wants to merge 2 commits into
accesslayerorg:mainfrom
yugomania:fix/ci-build-errors

Conversation

@yugomania

@yugomania yugomania commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Closes #769


Summary

Fixes three pre-existing TypeScript build errors on main that break pnpm build:

  1. src/config.schema.tsSTELLAR_AUTH_SECRET was declared twice (duplicate object property, TS1117). Removed the redundant trailing declaration; the canonical definition with its SEP-10 challenge-signing comment is kept.
  2. src/constants/error.constants.ts — routes in admin.routes.ts and creator.routes.ts reference ErrorCode.UNPROCESSABLE_ENTITY (HTTP 422) but the constant was never defined (TS2339). Added it, following the existing ErrorCode convention.
  3. src/modules/creator/creator.routes.tsreq.params.keyId is typed string | string[] under Express 5; normalized with String(...) (same pattern already used throughout admin.routes.ts) so Prisma receives a string filter (TS2322).

Why this is a separate PR

These are base-main issues unrelated to any feature work. Keeping them isolated lets the token-expiry PR stay narrowly scoped.

Validation

  • pnpm build passes (exit 0, zero TS errors)
  • pnpm lint passes

Remove duplicate STELLAR_AUTH_SECRET from config schema, add the
missing UNPROCESSABLE_ENTITY error code, and normalize the creator
route keyId param so Prisma receives a string.

🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>
@Chucks1093

Copy link
Copy Markdown
Member

✅ CI Passed — ⚠️ Merge Conflict

CI is green but this PR has a merge conflict with main and cannot be auto-merged.

To fix:

  1. git fetch origin && git checkout your-branch && git merge origin/main
  2. Resolve conflicts, run npm run build and npm test to verify
  3. Push — will be auto-merged once clean

Resolve conflict by taking upstream's already-merged versions of
config.schema.ts and creator.routes.ts; the PR's fixes are already in main.

🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add unit tests for the token expiry validator correctly computing the expiry timestamp from the issued-at claim

2 participants