Explanation for why the parsed property is deprecated?

[dlong500]

The parsed property is marked as deprecated (apparently with the #1898 commit) but without comments as to why it was deprecated or what we should be using going forward to access the same info.

I'm interested in getting a list of explicitly passed arguments (to differentiate from the final resolved arguments that contain defaults). Ideally this list would be generated by yargs internally in the same way the yargs.parsed.defaulted object is generated. See #513 for similar discussion. What would be the recommended way to access the yargs details going forward?

[shadowspawn]

Thanks for the links, and saying why you are interested.

There is a closed PR that was going to offer new detailed parse information, which mentions issues with existing .parsed: #1472 (comment)

The PR would have changed the docs to say:

note: The .parsed option has known limitations and is deprecated. Instead use yargs.parserConfiguration({detailed: true}) to get a detailed parse.

So my reading is that .parsed has still been deprecated due to the limitations, but there is not a replacement yet.