Feature request: add stability to commands and options

[bitliner]

Context

Sometimes a command could be not stable yet (while it's on a stable release, however still could break, and needs more testing).

Same for command options.

A similar scenario is NodeJS standard API. Node JS manages 3 levels of stability (see here )

• stability 0 - Deprecated
• stability 1 - Experimental (eg Use of the feature is not recommended in production environments)
• stability 2 - Stable

Problem

Yargs does not provide a way to set which options/commands are experimental or stable.

Question

Do you plan to add support for it?

[mleguen]

@bcoe Couldn't that be an evolution of the recently added deprecated feature?

[bcoe]

@mleguen yeah, I think that's a good idea. @laggingreflex thoughts on this one?

[laggingreflex]

Yep, I like this too. This does seem to be a direct evolution.

We can change deprecated:bool|string API to stability:string?

[jgoux]

This feature would be great, I'm writing a tool to automatically generate documentation out of a yargs CLI program and we have experimental commands (I have to edit the doc afterward manually currently).