You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2021. It is now read-only.
ugly code, with a bunch of parameters specified for every call
duplication, with parameters specified in multiple places (unless the user abstracts them out)
upgrade difficulty, because otherwise-insignificant method signature changes will break calls
uncertain behavior, because without thoroughly investigating argo-server code, it's unclear what values are the correct defaults
I suspect this is either an OpenAPI-Generator bug or config issue. If I generate a scala client with OpenAPI-Generator's scala-akka plugin, the parameters are Options defaulted to None.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
WorkflowServiceApi.listWorkflows, for example, requires all parameters even though all but
namespace
is optional.This causes several issues:
I suspect this is either an OpenAPI-Generator bug or config issue. If I generate a scala client with OpenAPI-Generator's
scala-akka
plugin, the parameters areOption
s defaulted toNone
.The text was updated successfully, but these errors were encountered: