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
> Default values can be provided with the [cli.FlagDefault](https://pkg.go.dev/go.followtheprocess.codes/cli#FlagDefault) Option
182
+
180
183
The types are all inferred automatically! No more `BoolSliceVarP` ✨
181
184
182
185
The types you can use for flags currently are:
@@ -232,7 +235,7 @@ cli.New(
232
235
)
233
236
```
234
237
235
-
This will return a `[]string` containing all the positional arguments to your command (not flags, they've already been parsed elsewhere!)
238
+
This will return a `[]string` containing all the positional arguments to your command (not flags, they've already been parsed out!)
236
239
237
240
Or, if you want to get smarter 🧠 `cli` allows you to define *type safe* representations of your arguments, with or without default values! This follows a similar
238
241
idea to [Flags](#flags)
@@ -294,7 +297,8 @@ The types you can currently use for positional args are:
294
297
-`net.IP`
295
298
296
299
> [!WARNING]
297
-
> Slice types are not supported (yet), for those you need to use the `cmd.Args()` method to get the arguments manually. I'm working on this!
300
+
> Slice types are not supported (yet), for those you need to use the `cmd.Args()` method to get the arguments manually. I plan to address this but it can be tricky
301
+
> as slice types will eat up the remainder of the arguments so I need to figure out a good DevEx for this as it could lead to confusing outcomes
0 commit comments