feat(config): fee config fixedFee takes an amount and a currency code - #787
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
✱ Stainless preview builds for gridThis PR will update the cli go kotlin openapi php python ruby typescript Edit this comment to update them. They will appear in their respective SDK's changelogs. ✅ grid-typescript studio · code · diff
✅ grid-openapi studio · code · diff
✅ grid-ruby studio · code · diff
✅ grid-go studio · code · diff
✅ grid-kotlin studio · code · diff
✅ grid-python studio · code · diff
✅ grid-php studio · code · diff
✅ grid-cli studio · code · diff
This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push. |
f4ab8f7 to
fe42acc
Compare
Greptile SummaryThe PR changes fixedFee from a source-currency integer to an explicit amount-and-currency object.
Confidence Score: 4/5This PR should not merge until the fixedFee wire-format break is placed behind the repository’s required API-version change. The current platform configuration request and response contracts replace an integer with a required object, invalidating existing payloads and generated client types while info.version remains unchanged. Files Needing Attention: openapi/components/schemas/config/FeeConfig.yaml and openapi/openapi.yaml
|
| Filename | Overview |
|---|---|
| openapi/components/schemas/config/FeeConfig.yaml | Defines the new fixedFee object contract, but introduces a breaking type change without the required API version bump. |
| openapi.yaml | Correctly reflects the source-schema change in the generated public bundle, including the unversioned breaking contract. |
| mintlify/openapi.yaml | Remains synchronized with the root generated bundle and exposes the same breaking fixedFee shape to documentation consumers. |
Prompt To Fix All With AI
### Issue 1
openapi/components/schemas/config/FeeConfig.yaml:19-21
**Unversioned fixed-fee type break**
When existing clients send an integer `fixedFee` to `PATCH /platform/config` or deserialize it from `GET /platform/config`, the changed schema replaces that value with a required object, causing request validation or generated-client type failures without the required API-version boundary.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: f4ab8f7 | Re-trigger Greptile
fixedFee is an object of amount plus a plain ISO 4217 currency code, so the fee currency is explicit without nesting the full Currency object. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
fe42acc to
d17bf85
Compare
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|

fixedFee is now an object of amount plus a plain ISO 4217 currency code,
so the fee currency is explicit without nesting the full Currency object.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com