Skip to content

Make name required in additional-dependency-nodes #430

@javierbrea

Description

@javierbrea

Summary

The name property in additional-dependency-nodes should become required.

With the new object-based selector syntax, [custom dependency nodes can be referenced through nodeKinds, and name is the identifier used for that]](#386). Without name, an additional dependency node cannot be targeted from selectors, which makes it incomplete in the new model.

Why

  • name is needed to reference custom dependency nodes from selectors.
  • It makes the configuration more explicit and self-documenting.
  • It avoids defining nodes that cannot be used by the selector system consistently.

Metadata

Metadata

Assignees

No one assigned

    Labels

    scope: codeChanges in the funcional code of packagestype: featureFeature to be implemented

    Projects

    Status

    Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions