How to use a custom CLI flag separator

[JonasScharpf]

How to use a custom CLI flag separator

[JonasScharpf]

not setting a Value for StringSliceFlag solves the issue somehow. fancy_name --groups="asdf,foo" --groups="qwertz" then returns the expected content which is [asdf,foo qwertz]

[Pipello]

I already tried to set app.SliceFlagSeparator = ";" but this has no effect
I guess that is a bug

or a specific flag
I don't see a real usage fof setting separator per flag but having a Separator string on the StringSliceFlag could solve it

[dearchap]

Can you try WithSeparatorSpec on the string slice flag ?

[JonasScharpf]

could you give me a code hint for WithSeparatorSpec on a StringSliceFlag? May I do something wrong as Go newbie, because of unknown field 'WithSeparatorSpec' in struct literal of type cli.StringSliceFlag

[dearchap]

https://github.com/urfave/cli/blob/v2-maint/flag_string_slice.go#L181

Are you using the latest v2 release ?

[JonasScharpf]

yes I do, v2.27.0

I still believe this is a syntax thing on my side

func GetCliFlags() []cli.Flag {
    return []cli.Flag{
        &cli.StringSliceFlag{
            Name:    "groups",
            Value:   cli.NewStringSlice("this,that,other", "foo"),
            Usage:   "Groups, can be given multiple times",
            WithSeparatorSpec: cli.separatorSpec{sep: ";"},
    }
}

[dearchap]

Ah no you need to do

func GetCliFlags() []cli.Flag {
    ssflag := &cli.StringSliceFlag{
            Name:    "groups",
            Value:   cli.NewStringSlice("this,that,other", "foo"),
            Usage:   "Groups, can be given multiple times",
    }
    ssflag.WithSeparatorSpec(cli.separatorSpec{sep: ";"})

    return []cli.Flag{
        ssflag,
    }
}

[JonasScharpf]

Thanks for the hint, but it does not work as separatorSpec is not exported (function starting with lower case). In the yet unreleased v3 this is even no longer available

./first.go:90:34: separatorSpec not exported by package cli
./first.go:90:48: unknown field 'sep' in struct literal of type cli.separatorSpec

I'll stay with v2, keep the setting globally and use no default value