fix: fixed strict check for paymasterUrl in useCapabilities #2059
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.
Title:
Fixed strict check for
paymasterUrl
inuseCapabilities
Description:
What changed? Why?
Previously,
paymasterService
was added even whenpaymasterUrl
was an empty string (""
), resulting in an invalid configuration. Now, the check ensures thatpaymasterService
is only included ifpaymasterUrl
is not empty, preventing incorrect payloads.Notes to reviewers
The main change is in the conditional logic—switched from a loose check to an explicit validation. This prevents edge cases where an empty string could lead to an incomplete configuration.
How has it been tested?
paymasterUrl
values.paymasterService
is only included when the URL is present.usePaymaster
to ensure no regressions.