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.
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
Replace
include_special_cased_deps
flag withshould_traverse_deps_predicate
#19272Replace
include_special_cased_deps
flag withshould_traverse_deps_predicate
#19272Changes from 6 commits
c95aa60
c2c6f26
ef7a09f
e30672c
941c3c2
c1c9252
c1ed5a2
39e5bde
434a8fb
945b50b
869b91f
f0a808c
a77b046
412e994
0b91c76
57660a6
d0364f5
b856127
7ce2bce
6a28cd6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In #19155, I just had a comment on the
determine_explicitly_provided_dependencies
rule that said:NB: This rule ignores request.should_traverse_deps_predicate.
@thejcannon recommended I use an actual type instead of just a comment in #19155 (comment)
So, I added this
ExplicitlyProvidedDependenciesRequest
with a rule to minimize API churn in this PR.Do we want to deprecate
Get(ExplicitlyProvidedDependencies, DependenciesRequest)
? If/when we do that, we can probably put a deprecation warning in this rule.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's a good idea, although feel free to carry this over into a future PR so we can merge this one.
Also up to you here 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can deprecate once we have updated all uses within the pants repo. So, it fits best in a future PR.