Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Fix label_flag and label_setting to not have a dependency on the default #13667

Closed

Conversation

katre
Copy link
Member

@katre katre commented Jul 12, 2021

value.

This prevents an extra analysis, since the dependency should only be on
the value being used.

Fixes #11291.

Closes #13372.

PiperOrigin-RevId: 369445041

@google-cla google-cla bot added the cla: yes label Jul 12, 2021
mai93 and others added 2 commits July 12, 2021 21:22
`required_providers` attribute allows the aspect to limit its propagation to only the targets whose rules advertise the required providers. It accepts a list of either providers or providers lists. To make some rule targets visible to an aspect, the rule must advertise all providers from at least one of the lists specified in the aspect `required_providers`.

This CL also adds incompatible flag `incompatible_top_level_aspects_require_providers` which when set allows the top level aspects to only run on top level targets that advertise its required providers. It is needed to avoid breaking existing usages on command line aspects on targets not advertising its required providers.

PiperOrigin-RevId: 373738497
value.

This prevents an extra analysis, since the dependency should only be on
the value being used.

Fixes bazelbuild#11291.

Closes bazelbuild#13372.

PiperOrigin-RevId: 369445041
@katre katre closed this Jul 13, 2021
@katre katre deleted the cp-c9f9-label_flag_dep branch July 13, 2021 01:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants