-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Properly handle package-default visibility in AggregatingAttributeMapper
Have `#visitAttribute` recognize that visibility is special, which lets it play nice with the `attr` query function and lets us delete `#getPossibleAttributeValues`. We check for the visibility special case after checking for selects and computed defaults - visibility shouldn't be either of these, but stranger things have happened. I think the history here is that package-default visibility was always broken for the `attr` query function, which uses `#visitAttribute`, while query output was correct because it used #getPossibleAttributeValues (or other scattered special-casing which existed at various times). rule_test_test needed to be updated because it was expecting the broken behavior - package-default visibility being ignored by `attr(...)`. PiperOrigin-RevId: 309477218
- Loading branch information
1 parent
23609fd
commit 0f38eea
Showing
5 changed files
with
51 additions
and
59 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters