Encode URI path params in accounts.retrieve#2761
Merged
Merged
Conversation
jar-stripe
approved these changes
Jun 22, 2026
Member
Author
|
The tests themselves are passing, but the types-test step is failing because of an upstream issue in the Given that it's unrelated to this PR, i'm going to merge through it and we can file a run ticket for the actual issue, if it persists |
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
2 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.
Why?
Small follow up to #2750 to cover a method we missed. It was generated separately, so we missed it in the initial fix.
What?
encodeURIComponentcall toaccounts.retrieve()See Also