Skip to content

Feat/provider capability matrix#67

Open
oraimoitel wants to merge 3 commits into
emrekayat:mainfrom
oraimoitel:feat/provider-capability-matrix
Open

Feat/provider capability matrix#67
oraimoitel wants to merge 3 commits into
emrekayat:mainfrom
oraimoitel:feat/provider-capability-matrix

Conversation

@oraimoitel

Copy link
Copy Markdown

Done ✅👍✅
closes #61

@vercel

vercel Bot commented Jun 29, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the emrekayat's projects Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave

drips-wave Bot commented Jun 29, 2026

Copy link
Copy Markdown

@oraimoitel 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! 🚀

Learn more about application limits

@emrekayat

Copy link
Copy Markdown
Owner

Thanks for the provider capability matrix work. I cannot merge this yet because the API test suite fails at module import time.

Command run:

npm run test --workspace @query402/api

Failure:

Error: Invalid environment: X402_PAY_TO_ADDRESS Required

The failure happens when apps/api/src/lib/pricing.ts imports config at module load time. Existing tests like src/lib/pricing.test.ts and src/providers/registry.test.ts import pricing/provider modules before applyApiTestEnv() has a chance to set env vars, so they now fail before any tests run.

Please avoid making the static pricing module depend on full runtime config at import time, or make the capability caveat logic injectable/lazy so existing pricing/provider tests remain credential-free. Also please check the new matcher usage in pricing.test.ts: expect.toBeOneOf(...) is not a standard Vitest matcher unless a matcher plugin is installed.

After fixing, rerun:

npm run test --workspace @query402/api
npm run typecheck --workspaces
npm run build --workspaces
git diff --check origin/main...HEAD

@oraimoitel oraimoitel force-pushed the feat/provider-capability-matrix branch from da384e1 to 0cdb32d Compare June 30, 2026 06:12
@emrekayat

Copy link
Copy Markdown
Owner

Thanks for the update. I rechecked the merge ref from the maintainer account. The focused checks pass on the current GitHub merge ref:

git diff --check main...pr-67-merge
npm run test --workspace @query402/shared
npm run test --workspace @query402/api -- src/lib/pricing.test.ts src/routes/public.test.ts
npm run typecheck --workspace @query402/api
npm run typecheck --workspace @query402/web
npm run build --workspace @query402/web

Results: shared tests pass (12), API tests pass (24), API/web typecheck pass, and web build passes.

I still cannot merge this branch because GitHub now reports it as DIRTY / CONFLICTING against latest main. The merge ref is based on an older main; against current main it would also undo recently merged work such as receipt export, payment leak check, and x402 snapshot tests.

Please rebase or merge latest main, resolve the overlap, and push again. Functionally this looks close once it is based on current main and the same checks stay green.

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 provider capability matrix endpoint for stable marketplace diligence

2 participants