Reword fixture docs for clarity#6627
Merged
nicoddemus merged 1 commit intopytest-dev:masterfrom Jan 30, 2020
DanielArndt:fixture-docs-reword-for-clarity
Merged
Reword fixture docs for clarity#6627nicoddemus merged 1 commit intopytest-dev:masterfrom DanielArndt:fixture-docs-reword-for-clarity
nicoddemus merged 1 commit intopytest-dev:masterfrom
DanielArndt:fixture-docs-reword-for-clarity
Conversation
Contributor
Author
|
I'm not a linguist, but alternatively "Not only can fixtures be used in test functions, but fixture functions can use other fixtures themselves". |
nicoddemus
approved these changes
Jan 30, 2020
Member
nicoddemus
left a comment
There was a problem hiding this comment.
Indeed it looks better, thanks!
You are right, small adjustments to the docs in general don't need a CHANGELOG entry.
Thanks again! 👍
Merged
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
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.
I stumbled over the wording here a bit, and I thought this would make it read a little easier.
I'm not sure if I need a
changelogentry for this. Obviously, there is no issue to attribute it to. Let me know if that is necessary.