feat: add mayanNonEvmPermitSignature to routes and quotes API parameters #460
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nathandem
force-pushed
the
feat/LF-14894-add-mayanNonEvmPermitSignature-to-routes-and-stepTransaction-API-options
branch
2 times, most recently
from
85a2a9c to
afb8c4f
Compare
nathandem
force-pushed
the
feat/LF-14894-add-mayanNonEvmPermitSignature-to-routes-and-stepTransaction-API-options
branch
from
152bb6c to
0c99dc3
Compare
nathandem
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This tiny PR is based on v17.47.0 to avoid causing issues in lifi-backend.
At the time of writing/coding this, lifi-backend relies on @lifi/types 17.47.0 and @lifi/data-types 6.42.1. Making this PR on top of v17.48 breaks a lot of things unrelated to this change.
Wen types in BE repo to avoid this issue? 😁