feat: remove fee columns from SwapInfo and update API definition #53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the Jupiter API documentation: https://dev.jup.ag/api-reference/swap/quote,
quoteResponse.routePlan.swapInfo.feeAmountandquoteResponse.routePlan.swapInfo.feeMinthave been deprecated. ThequoteAPI no longer returns these two fields; therefore,feeAmountandfeeMintin theQuoteResponsepassed duringswapwill be two empty strings, causing a swap error.This pull request updates the Jupiter API client and OpenAPI schema to remove swap fee fields from the swap response model. The most significant change is the removal of
feeAmountandfeeMintfrom both the OpenAPI spec and the generated client code, reflecting an update in the API contract.API contract changes
feeAmountandfeeMintproperties from theSwapInforesponse model in the OpenAPI spec (jupiter/openapi/swap-api.yaml). [1] [2]feeAmountandfeeMint.Generated client updates
jupiter/client.gen.gousingoapi-codegenv2.5.1, which removesfeeAmountandfeeMintfrom theRoutePlanStepstruct and updates the code generation version. [1] [2]