-
-
Notifications
You must be signed in to change notification settings - Fork 646
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
Clarify how __defaults__
apply to target generators.
#17493
Merged
kaos
merged 2 commits into
pantsbuild:main
from
danxmoran:danxmoran/defaults-docs-clarification
Nov 8, 2022
Merged
Clarify how __defaults__
apply to target generators.
#17493
kaos
merged 2 commits into
pantsbuild:main
from
danxmoran:danxmoran/defaults-docs-clarification
Nov 8, 2022
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
I've seen a few users (including myself) be confused when `__defaults__` don't apply to generated targets. Add a blurb to the docs explicitly stating that defaults only apply _before_ target generation, so if you want to specify defaults for both generated & manually-written targets then you need to list both the generator & generated targets in the `__defaults__` dict.
kaos
approved these changes
Nov 8, 2022
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.
Thank you Dan for that clarifying note. 👍🏽
danxmoran
added a commit
to danxmoran/pants
that referenced
this pull request
Nov 8, 2022
) I've seen a few users (including myself) be confused when `__defaults__` don't apply to generated targets. Add a blurb to the docs explicitly stating that defaults only apply _before_ target generation, so if you want to specify defaults for both generated & manually-written targets then you need to list both the generator & generated targets in the `__defaults__` dict. # Rust tests and lints will be skipped. Delete if not intended. [ci skip-rust]
danxmoran
added a commit
to danxmoran/pants
that referenced
this pull request
Nov 8, 2022
) I've seen a few users (including myself) be confused when `__defaults__` don't apply to generated targets. Add a blurb to the docs explicitly stating that defaults only apply _before_ target generation, so if you want to specify defaults for both generated & manually-written targets then you need to list both the generator & generated targets in the `__defaults__` dict.
kaos
pushed a commit
that referenced
this pull request
Nov 8, 2022
…#17493) (#17498) Clarify how `__defaults__` apply to target generators. (#17493) I've seen a few users (including myself) be confused when `__defaults__` don't apply to generated targets. Add a blurb to the docs explicitly stating that defaults only apply _before_ target generation, so if you want to specify defaults for both generated & manually-written targets then you need to list both the generator & generated targets in the `__defaults__` dict. # Rust tests and lints will be skipped. Delete if not intended. [ci skip-rust]
kaos
pushed a commit
that referenced
this pull request
Nov 8, 2022
…#17493) (#17499) Clarify how `__defaults__` apply to target generators. (#17493) I've seen a few users (including myself) be confused when `__defaults__` don't apply to generated targets. Add a blurb to the docs explicitly stating that defaults only apply _before_ target generation, so if you want to specify defaults for both generated & manually-written targets then you need to list both the generator & generated targets in the `__defaults__` dict.
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.
Closes #17450
I've seen a few users (including myself) be confused when
__defaults__
don't apply to generated targets. Add a blurb to the docs explicitly stating that defaults only apply before target generation, so if you want to specify defaults for both generated & manually-written targets then you need to list both the generator & generated targets in the__defaults__
dict.