【PARAM usage】Can I write a PARAM tag that do nothing ?

[Shawn Qiu]

The question is that I want to convert some commands like below to xml: 

cmd  [ < ipv4 | ipv6 >  [ unicast | multicast | vpn | labeled-unicast | flowspec ] ]

It seem like I need to write:

COMMAND  cmd

        PARAM  mode="switch"  optional="true"

                PARAM  ipv4  mode="subcommand"

                        PARAM  mode="switch"  optional="true"

                                PARAM  unicast  mode="subcommand"

                                PARAM  multicast  mode="subcommand"

                                PARAM  vpn  mode="subcommand"

                                PARAM  labeled-unicast  mode="subcommand"

                                PARAM  flowspec  mode="subcommand"

                PARAM  ipv6  mode="subcommand"

                        PARAM  mode="switch"  optional="true"

                                PARAM  unicast  mode="subcommand"

                                PARAM  multicast  mode="subcommand"

                                PARAM  vpn  mode="subcommand"

                                PARAM  labeled-unicast  mode="subcommand"

                                PARAM  flowspec  mode="subcommand"

But I would like to write:

COMMAND  cmd

        PARAM  nop  optional="true"

                PARAM  mode="switch"

                        PARAM  ipv4  mode="subcommand"

                        PARAM  ipv6  mode="subcommand"

                PARAM  mode="switch"  optional="true"

                        PARAM  unicast  mode="subcommand"

                        PARAM  multicast  mode="subcommand"

                        PARAM  vpn  mode="subcommand"

                        PARAM  labeled-unicast  mode="subcommand"

                        PARAM  flowspec  mode="subcommand"

PARAM nop is used to control optional of its child params but user in CLI doesn't need to enter value for it. 

I found that somebody had created an issue about this in google code. It's Issue 82.

https://groups.google.com/g/klish-dev/c/qj6U_r5CaCE/m/P9dqazc_u2oJ

So is that feature available?

Looking forward to your reply,

Thank you

[Serj Kalichev]

Such feature is not available.

You can write something like that:

COMMAND  cmd

            PARAM  name="s1" mode="switch" optional="true"

                    PARAM  ipv4  mode="subcommand"

                    PARAM  ipv6  mode="subcommand"

            PARAM  mode="switch"  optional="true" test='"x${s1}" != "x"'

                    PARAM  unicast  mode="subcommand"

                    PARAM  multicast  mode="subcommand"

                    PARAM  vpn  mode="subcommand"

                    PARAM  labeled-unicast  mode="subcommand"

                    PARAM  flowspec  mode="subcommand"

Note "test=..." and "optional" with first switch

13.10.2021 06:58, 'Shawn Qiu' via klish-dev пишет:

--
You received this message because you are subscribed to the Google Groups "klish-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to klish-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/klish-dev/91df0ae6-ba16-4789-a6fd-db0b8e5f7a63n%40googlegroups.com.

[Shawn Qiu]

It works and it's just what I need! Thank you very much!!

In fact I had tried that but I made a mistake. I wrote test=“-n ${switch_param_name}” but it didn't work as my expection. 

The correct syntax is test='-n "${switch_param_name}"'. Never forget to use a pair of quotation marks while testing a string!

Thanks again!

[Serj Kalichev]

I'm not sure but may be something like test='"${switch_name}"' will work too.

14.10.2021 05:38, 'Shawn Qiu' via klish-dev пишет:

To view this discussion on the web visit https://groups.google.com/d/msgid/klish-dev/02f228c1-d597-41ff-8bd1-dc6061f36973n%40googlegroups.com.

[Shawn Qiu]

Yes, my test show that the effect of using test='"${switch_name}"' and test='${switch_name}' are the same, and both of them could work.

But test='-n ${switch_name}' and test='-n "${switch_name}"' are different.