From a318cbf9c4ffc300e94a55fe366eee2be61b9120 Mon Sep 17 00:00:00 2001 From: Stefan Schmutz Date: Wed, 11 Dec 2024 10:33:02 +0100 Subject: [PATCH] Fix broken Link to the Tidyverse style guide in Conditions.Rmd --- Conditions.Rmd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Conditions.Rmd b/Conditions.Rmd index cfb3346bf..485e4bd20 100644 --- a/Conditions.Rmd +++ b/Conditions.Rmd @@ -130,7 +130,7 @@ f() (NB: `stop()` pastes together multiple inputs, while `abort()` does not. To create complex error messages with abort, I recommend using `glue::glue()`. This allows us to use other arguments to `abort()` for useful features that you'll learn about in Section \@ref(custom-conditions).) -The best error messages tell you what is wrong and point you in the right direction to fix the problem. Writing good error messages is hard because errors usually occur when the user has a flawed mental model of the function. As a developer, it's hard to imagine how the user might be thinking incorrectly about your function, and thus it's hard to write a message that will steer the user in the correct direction. That said, the tidyverse style guide discusses a few general principles that we have found useful: . +The best error messages tell you what is wrong and point you in the right direction to fix the problem. Writing good error messages is hard because errors usually occur when the user has a flawed mental model of the function. As a developer, it's hard to imagine how the user might be thinking incorrectly about your function, and thus it's hard to write a message that will steer the user in the correct direction. That said, the tidyverse style guide discusses a few general principles that we have found useful: . ### Warnings \index{warnings}