Skip to content
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

Closed
wants to merge 2 commits into from
Closed

Conversation

paulreece
Copy link
Contributor

Summary

Test plan

Copy link
Contributor

@mrazauskas mrazauskas left a 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.

@@ -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
Copy link
Contributor

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.

Comment on lines 176 to 182
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:

:::
Copy link
Contributor

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.

@paulreece
Copy link
Contributor Author

Okay so for this one should I just close the PR? @mrazauskas

@paulreece
Copy link
Contributor Author

I'm closing this one.

@paulreece paulreece closed this Sep 24, 2022
@github-actions
Copy link

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants