fix(fetch): propagate deployless parameter to nested fetch calls#512
Merged
Foulks-Plb merged 3 commits intomainfrom Feb 4, 2026
Merged
fix(fetch): propagate deployless parameter to nested fetch calls#512Foulks-Plb merged 3 commits intomainfrom
Foulks-Plb merged 3 commits intomainfrom
Conversation
Foulks-Plb
changed the title
Rubilmax
approved these changes
Feb 3, 2026
Collaborator
|
tests are failing |
Contributor
Author
Probably E2E flaky tests. |
Rubilmax
approved these changes
Feb 4, 2026
oumar-fall
approved these changes
Feb 4, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Context
A large part of the failing calls comes from the fact that deployless contract calls are not well supported by our RPC providers.
In the V1 flows, deployless is disabled by default, but some nested calls do not inherit the deployless property, which causes a lot of unnecessary errors.
Problem
When fetch functions destructure the deployless parameter from DeploylessFetchParameters, this value is not propagated to nested fetch calls. This causes inconsistent behavior in the fallback path.
Fix
Pass deployless explicitly to nested fetch calls