Skip to content

Reserved parameter names or and and should not be reserved #59

Description

@MartinHelmut

Description

Currently the following two parameter names are reserved:

  • or - This parameter name is restricted for command script expressions.
  • and - This parameter name is reserved, though not used anywhere, yet.

The reason is that those cannot be clearly distinguished currently from the existing operators. Command script example:

[commands]
build = "echo %{value 'one' or 'two'}"

The value here is an actual parameter value passed in, where or is the keyword.

Proposal

It should not be necessary to reserve those names. This would also make more issues in the future if there would be more keywords. So those should either be:

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementImprove on an existing feature.refactorEnhance or hardens functionality.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions