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
Let's say I have a command with a multi-value argument of the following sort:
cmdArgs.StringsArgPtr(
&cmd.args.srcs,
"SOURCE_PATHS",
nil,
"Directories or files to load",
)
The automatically inferred spec for it will (incorrectly) be "something something SOURCE_PATHS". This will incorrectly reject multiple "source path" arguments with an "incorrect usage" error (only a single argument will be allowed).
The correct, working spec can be specified explicitly to fix the issue: "something something SOURCE_PATHS...".
However, it seems that multi-value argument constructor can be made a little smarter to add ellipsis to spec automatically.
The text was updated successfully, but these errors were encountered:
Let's say I have a command with a multi-value argument of the following sort:
The automatically inferred spec for it will (incorrectly) be "something something SOURCE_PATHS". This will incorrectly reject multiple "source path" arguments with an "incorrect usage" error (only a single argument will be allowed).
The correct, working spec can be specified explicitly to fix the issue: "something something SOURCE_PATHS...".
However, it seems that multi-value argument constructor can be made a little smarter to add ellipsis to spec automatically.
The text was updated successfully, but these errors were encountered: