-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Setup admonitions. #12495 #13304
Setup admonitions. #12495 #13304
Conversation
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.
Thanks, but for my eye these changes look unnecessary.
docs/SetupAndTeardown.md
Outdated
@@ -97,7 +97,11 @@ describe('matching cities to foods', () => { | |||
}); | |||
``` | |||
|
|||
Note that the top-level `beforeEach` is executed before the `beforeEach` inside the `describe` block. It may help to illustrate the order of execution of all hooks. | |||
:::note |
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.
No need of this. The order is illustrated just below, but this is also illustration for the code above. Semantically this is just one piece of text and need to change anything.
docs/SetupAndTeardown.md
Outdated
Just like the `describe` and `test` blocks Jest calls the `before*` and `after*` hooks in the order of declaration. | ||
|
||
:::note | ||
|
||
The `after*` hooks of the enclosing scope are called first. For example, here is how you can set up and tear down resources which depend on each other: | ||
|
||
::: |
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.
Also here there is no need to change anything. It does not look good or logic to end the note with a colon. Also this splitting does not make sense, because this is just one piece of text.
Okay so for this one should I just close the PR? @mrazauskas |
39f4bc3
to
e9696bb
Compare
I'm closing this one. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Test plan