Transition Support: add configuration id to TargetKey #7926
Conversation
This file contains hidden or 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
Collaborator
Author
|
Configuration id will only be exposed to aspects starting with Bazel 8.5: bazelbuild/bazel#27128 |
# Conflicts: # MODULE.bazel # MODULE.bazel.lock # aspect/testing/rules/src/com/google/idea/blaze/aspect/IntellijAspectTest.java
LeFrosch
force-pushed
the
pull/07091d5209512f66808fcaa9081ba534eaea0f24
branch
from
07091d5 to
e8df2bf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to support transitions we need to be able to differentiate targets with different configurations. This PR adds the configuration id to the TargetKey class which is different after every transition.