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.

Sign up for GitHub

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

chore(docs): fix code blocks without language settings #1040

Merged
merged 1 commit into from
Sep 19, 2022
Merged

chore(docs): fix code blocks without language settings #1040

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1131,7 +1131,7 @@ So far we've focused on how Ginkgo specs are constructed using nested nodes and

You typically use a matcher library, like [Gomega](https://github.com/onsi/gomega) to make assertions in your spec. When a Gomega assertion fails, Gomega generates a failure message and passes it to Ginkgo to signal that the spec has failed. It does this via Ginkgo's global `Fail` function. Of course, you're allowed to call this function directly yourself:

```
```go
It("can read books", func() {
if book.Title == "Les Miserables" && user.Age <= 3 {
Fail("User is too young for this book")
Expand Down Expand Up @@ -4109,7 +4109,7 @@ Describe("Repaginating Books", func() {

Now when this spec runs Ginkgo will print out a report detailing the experiment:

```
```bash
Will run 1 of 1 specs
------------------------------
• [2.029 seconds]
Expand Down