From cf611c4703d91f2fa92f07227026920bc2185ea6 Mon Sep 17 00:00:00 2001 From: Abirdcfly Date: Mon, 19 Sep 2022 16:26:44 +0800 Subject: [PATCH] chore(docs): fix code blocks without language settings --- docs/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/index.md b/docs/index.md index 07516a668..b09a66849 100644 --- a/docs/index.md +++ b/docs/index.md @@ -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") @@ -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]