tree cb16719d52343c611e98edb8e75a7d02424e0923
parent 52cfb9cd4af6787a635d1cd2976bd1bc15dd0077
author juliexxia <juliexxia@google.com> 1535060267 -0700
committer Copybara-Service <copybara-piper@google.com> 1535060348 -0700

Modify AliasConfiguredTargets to store related config conditions.

This allows for properly resolved selects for the proto output format of cquery (b/112853400). AliasConfiguredTargets don't extend RuleConfiguredTargets, just stores an 'actual' configured target value. Since they don't extend RuleConfiguredTarget, they don't  have access to the config conditions for the alias target. They *can* currently access the config condition for the 'actual' target, but those aren't the correct conditions for the alias target.

ex of pattern that this CL addresses:

//test:BUILD
alias(
  name = 'fake_target',
  actual = select({
    ':config1': ':target1',
    ':config2': ':target2',
  })
)

Currently, running "blaze cquery 'deps(//test:fake-target)' --output=proto --correct_flag_to_trigger_config1" returns an error since the output formatter attempts to use the config conditions of target1 (the resolved value of the 'actual' attribute) to evaluate the select in the 'actual' attribute of the alias target.

PiperOrigin-RevId: 210002631