-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Codegen: better handling of duplicate param names #3780
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
✅ Deploy Preview for redux-starter-kit-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 48883be:
|
|
@phryneas Hello! Can you give me a review? |
Oh, this is no good. export type ConnectCoreV1GetNamespacedPodProxyWithPathApiArg = {
/** name of the PodProxyOptions */
name: string
/** object name and auth scope, such as for teams and projects */
namespace: string
/** path to the resource */
path: string
/** Path is the URL path to use for the current proxy request to pod. */
path?: string
} |
02f5340
to
0f4efdc
Compare
@phryneas Added test. The reason we didn't just prefix it with _ is that it depends on the order of loading. If for some reason the _ at the beginning of a path is attached to a query, it will cause a huge bug. |
Hey @kahirokunn, thanks for the PR! |
@phryneas thanks! |
…re overlapped, the one defined first would disappear.
@phryneas |
Ugh... I'll try and find it 🤣 |
Found it... merged :) |
Released in v1.1.0 |
Thx! |
When we generated this swagger, the names of the path parameter and query parameter were covered and broken, so we fixed it.