Long lists of positional arguments on API methods

[edvald]

This appears to be more of an upstream issue with swagger-codegen (ref swagger-api/swagger-codegen#7930) but I wanted to flag it here.

Basically as it stands, adding a new option is likely to break compatibility, and the usability isn't great as it is... To illustrate I just wrote this call: client.listNamespacedPod(namespace, undefined, undefined, undefined, undefined, labelSelector) - who knows what sequence the parameters will be in for the next k8s version :)

I'd at least suggest setting the appropriate configuration flag if the above issue gets resolved.

[lucasyvas]

I sympathize with the effort required to make client libraries for multiple languages, but using a generator produces some terrible interfaces like this as you've pointed out.

I'm happy you created this issue as I was wondering what the best default value was to put in for values you want to not set! So I will try this out and maybe that'll work.

It's too risky to expose the client calls to the code base... wrapping it in my own class right now to protect from inevitable breakages. There are super annoying problems with the TypeScript definitions as well (lots of things say they are mandatory, but they are not).

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.