Show origin of resolution in verbose list #5951
Merged
Conversation
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
When using some of the new resolvers such as "runnable-recipe", there's no longer a 1:1 relationship that the resolver and the "kind" match. Certain types of resolution may look fine from the perspective of the original resolver, while it may be a broken or invalid reference to a more apt (or canonical) resolver for its set "kind". By listing the original resolver, users may be able to more easily identify what the discrepancy is and where it's coming from. Reference: avocado-framework#5924 Signed-off-by: Cleber Rosa <crosa@redhat.com>
clebergnu
force-pushed
the
list_resolver_origin
branch
from
b47f875
to
1b99f38
Compare
richtja
requested changes
Jun 11, 2024
richtja
approved these changes
Jun 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When using some of the new resolvers such as "runnable-recipe", there's no longer a 1:1 relationship that the resolver and the "kind" match.
Certain types of resolution may look fine from the perspective of the original resolver, while it may be a broken or invalid reference to a more apt (or canonical) resolver for its set "kind".
By listing the original resolver, users may be able to more easily identify what the discrepancy is and where it's coming from.
Reference: #5924