Skip to content

chore: Sync account schemas - #886

Open
lightspark-copybara[bot] wants to merge 1 commit into
mainfrom
auto/sync-grid-schemas-20260901-181010
Open

chore: Sync account schemas#886
lightspark-copybara[bot] wants to merge 1 commit into
mainfrom
auto/sync-grid-schemas-20260901-181010

Conversation

@lightspark-copybara

Copy link
Copy Markdown
Contributor

Auto-synced account schemas.

These schemas are generated from VASP adapter field definitions in sparkcore.

Synced schemas:

  • common/ — per-currency account info, beneficiary, and payment account schemas
  • common/PaymentInstructions.yaml — payment instructions oneOf (new currencies added)
  • external_accounts/ — per-currency external account schemas (reference common/)
  • mintlify/snippets/corridor-required-fields.mdx — per-corridor required fields table
  • mintlify/corridor-fields.js — filter script for that table

Please review the changes before merging.

@mintlify

mintlify Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Grid 🟢 Ready View Preview Sep 1, 2026, 6:13 PM

@vercel

vercel Bot commented Sep 1, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
grid-wallet-demo Building Building Preview Sep 1, 2026 6:10pm UTC
1 Skipped Deployment
Project Deployment Actions Updated
grid-flow-builder Ignored Ignored Preview Sep 1, 2026 6:10pm UTC

Request Review

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

✱ Stainless preview builds for grid

This PR will update the grid SDKs with the following commit messages.

cli

chore(internal): regenerate SDK with no functional changes

go

chore(internal): regenerate SDK with no functional changes

kotlin

chore(tests): update bank name in PHP account test fixtures

openapi

chore(internal): regenerate SDK with no functional changes

php

chore(internal): regenerate SDK with no functional changes

python

chore(internal): regenerate SDK with no functional changes

ruby

chore(internal): regenerate SDK with no functional changes

typescript

chore(internal): regenerate SDK with no functional changes

Edit this comment to update them. They will appear in their respective SDK's changelogs.

grid-typescript studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅build ⏭️ (prev: build ✅) → lint ⏭️ (prev: lint ❗) → test ✅

grid-openapi studio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️

grid-ruby studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅build ⏭️ (prev: build ✅) → lint ✅test ✅

grid-kotlin studio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️build ✅lint ✅test ❗

grid-go studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅build ⏭️ (prev: build ✅) → lint ❗test ❗

go get github.com/stainless-sdks/grid-go@850d7b3996917cd1f1458a10f720b7b74315c39f
grid-python studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅build ⏭️ (prev: build ✅) → lint ⏭️ (prev: lint ❗) → test ❗

grid-php studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅lint ✅test ✅

grid-cli studio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️build ❗lint ❗test ❗


This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-09-01 18:17:27 UTC

@greptile-apps

greptile-apps Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR updates the PHP account schema’s bank-name example from BDO Unibank to Bank of the Philippine Islands and synchronizes both assembled OpenAPI contracts.

  • Updates the modular PhpAccountInfoBase source schema.
  • Updates the root and Mintlify OpenAPI bundles.
  • Leaves checked-in wallet bank-field artifacts stale relative to the changed source example.

Confidence Score: 4/5

The generated bank-field artifacts should be synchronized before merging so verification passes and wallet examples do not remain stale.

The OpenAPI source and bundles agree, but the changed example feeds checked-in generated wallet data that still contains the old value.

Files Needing Attention: openapi/components/schemas/common/PhpAccountInfoBase.yaml and generated wallet bank-field artifacts

Important Files Changed

Filename Overview
openapi/components/schemas/common/PhpAccountInfoBase.yaml Updates the PHP bank-name example, but dependent generated wallet artifacts were not regenerated.
openapi.yaml Keeps the assembled root contract synchronized with the modular schema change.
mintlify/openapi.yaml Keeps the Mintlify contract synchronized with the modular schema change.
Prompt To Fix All With AI
### Issue 1
openapi/components/schemas/common/PhpAccountInfoBase.yaml:23
**Generated bank fields are stale**

When bank-field verification regenerates artifacts from this changed OpenAPI example, the output differs from the checked-in demo and production files, causing verification to fail and leaving wallet examples on the old `BDO Unibank` value.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "chore: Sync account schemas" | Re-trigger Greptile

minLength: 1
maxLength: 255
example: BDO Unibank
example: Bank of the Philippine Islands (BPI)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Generated bank fields are stale

When bank-field verification regenerates artifacts from this changed OpenAPI example, the output differs from the checked-in demo and production files, causing verification to fail and leaving wallet examples on the old BDO Unibank value.

Context Used: CLAUDE.md (source)

Knowledge Base Used: Grid API contract

Prompt To Fix With AI
This is a comment left during a code review.
Path: openapi/components/schemas/common/PhpAccountInfoBase.yaml
Line: 23

Comment:
**Generated bank fields are stale**

When bank-field verification regenerates artifacts from this changed OpenAPI example, the output differs from the checked-in demo and production files, causing verification to fail and leaving wallet examples on the old `BDO Unibank` value.

**Context Used:** CLAUDE.md ([source](https://github.com/lightsparkdev/grid-api/blob/main/CLAUDE.md))

**Knowledge Base Used:** [Grid API contract](https://app.greptile.com/lightspark/-/custom-context/knowledge-base/lightsparkdev/grid-api/-/docs/api-contract.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

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.

0 participants