Skip to content

Tie feature update/creation with corrected/available documentation before release. #9761

@VBHunt

Description

@VBHunt

Could you please consider a mechanism to automatically check the documentation associated with a feature so that when you change the feature, the documentation is flagged for correction. Better yet don't allow a new feature to be included until the documentation is corrected to align with the new feature semantics.
For example as a new user of profiles, I could not figure out how to import a profile. The docs claim that there is a drop down menu selection on the new profile command. It does not exist in 1.117. There is an amazingly obscure default mechanism but the notion of "import" is nowhere to be found even though the docs claim it exists. To exercise the import function requires forensic sleuthing to see how one can import. This illustrates the need not only to construct or improve features but also to clearly document them so that we lowly users can learn to use them.

Metadata

Metadata

Assignees

Labels

docs-experiencefeedback on code.visualstudio.com experience

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions