Skip to content

[Question]: Why are params with the same responsibility named differently? #21237

@daerogami

Description

@daerogami

Task name

Npm@1 CmdLine@2

Task version

No response

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Windows 10

Question

There are probably more commands but these are the specific ones that come to mind.
Npm@1 has "workingDir" and CmdLine@2 has "workingDirectory". I can't find a reason why npm would have its param shortened and its incredibly frustrating to have commands silently ignore parameters because of subtle name differences.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions