Skip to content

$env:ChocolateyPackageName: for consistency, it should better be named $env:ChocolateyPackageId #2781

Closed
@schittli

Description

@schittli

Is Your Feature Request Related To A Problem? Please describe.

Yes, it is a problem because it creates confusion.
The Docs: Environment Variables explains:

  • ChocolateyPackageTitle: … equivalent to the <title /> field in the nuspec
  • ChocolateyPackageVersion: … equivalent to the <version /> field in the nuspec

This rule is great: The $Env-Variable is named according to the field in nuspec 😃, therefore we must not ask google for the $env variable name for the nuspec Title / Version field. It is intuitive.

But now, Choco breaks the rule, the Docs explains:

  • ChocolateyPackageName: … equivalent to the <id /> field in the nuspec

Describe The Solution. Why is it needed?

It would be very helpful if in the next version of Chocolatey:

  • $env:ChocolateyPackageName will be renamed to $env:ChocolateyPackageId
  • Then, $env:ChocolateyPackageName gets an Alias for $env:ChocolateyPackageId which will disappear in a later version

I hope that I have not to explain why this is useful 😃

Additional Context.

N/A

Related Issues

N/A

Metadata

Metadata

Assignees

Labels

4 - DoneEnhancementIssues that enhances existing functionality, or adds new features

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions