Request to suppress auto-completion for "deprecated" / "obsolete" status and warn the user.

clicon / clixon

YANG-based toolchain including NETCONF and RESTCONF interfaces and an interactive CLI

http://www.clicon.org/

Other

215 stars 72 forks source link

Request to suppress auto-completion for "deprecated" / "obsolete" status and warn the user. #410

Closed navaneethyv closed 1 year ago

navaneethyv commented 1 year ago

Hello !

From yang spec for keyword status


   o  "deprecated" indicates an obsolete definition, but it permits new/
      continued implementation in order to foster interoperability with
      older/existing implementations.

   o  "obsolete" means the definition is obsolete and SHOULD NOT be
      implemented and/or can be removed from implementations.```

[Slack Message](https://clixondev.slack.com/archives/C9NKJEXML/p1674468367732109)

Request to disable auto-completions for "obsolete" and "deprecated" keywords & provide warning if such an input is provided via CLI.

navaneethyv commented 1 year ago

Suggestion on the behaviour.

"deprecated" and "obsolete" should both prevent the auto completion.
"deprecated" shall accept the config with a warning [ is deprecated ]
"obsolete" nodes should not accept the configs with a warning[ is obsolete]

olofhagsand commented 1 year ago

My proposal is:

Do not generate any CLI syntax for obsolete elements (SHOULD NOT be implemented), that is leave it out altogether.
Accept deprecated syntax and generate completion. But as hidden commands, ie they can be given in scripts etc but are not visible in or <?> commands.

olofhagsand commented 1 year ago

Please verify