8000 Support outputs template variable in dependency outputs field · Issue #2662 · getporter/porter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Support outputs template variable in dependency outputs field #2662
Closed
@carolynvs

Description

@carolynvs

When evaluating a dependency's outputs for template syntax, we should support a shorter way of addressing the current dependency's outputs

Instead of ${bundle.dependencies.CURRENT_DEP.outputs.OUTPUT_NAME} the author should be able to use ${outputs.OUTPUT_NAME}. These should be equivalent variables and use the same backing map when the template is resolved.

This variable is only applicable to the outputs section of a dependency. Each template must be evaluated separately, if we want to support this new variable since it is specific to the context in which it's running.

Questions

  • Is this too similar to ${bundle.outputs.OUTPUT_NAME} which stores different data? like it could be ${dependency.outputs.OUTPUT_NAME} instead. 🤷‍♀️

ℹ️ Read PEP003 - Advanced Dependencies for context about how dependencies should work, design details, and notes about desired behavior.

Metadata

Metadata

Assignees

Labels

pep003-advanced-dependenciesImplementation of the Advanced Dependencies proposalplaceholderTracks work that has not yet be fully designed

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0