From cc70ca8c5d6fc15240dc159394e64825aaec6bb8 Mon Sep 17 00:00:00 2001 From: John Nissen-Hooper Date: Fri, 23 Feb 2024 14:10:32 -0500 Subject: [PATCH] Update studio.md fix small typo in the new readme --- docs/docs/studio.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/studio.md b/docs/docs/studio.md index 09694100cc93..c3d23de026be 100644 --- a/docs/docs/studio.md +++ b/docs/docs/studio.md @@ -10,7 +10,7 @@ RedwoodJS Studio is a package used during development to gain runtime insights i Redwood provides tools that lets developers "get to work on what makes your application special, instead of wasting cycles choosing and re-choosing various technologies and configurations."[1](https://github.com/redwoodjs/redwood/blob/main/README.md). -Much happens while your app processes a request: Invoke a function; handle a GraphQL request; resolve the request with a service; build and execute a SQL statement; connect to the database; handle the query response; further resolve the response so in contains all the data needed; return the result ... and more. +Much happens while your app processes a request: Invoke a function; handle a GraphQL request; resolve the request with a service; build and execute a SQL statement; connect to the database; handle the query response; further resolve the response so it contains all the data needed; return the result ... and more. While [logging](https://redwoodjs.com/docs/logger) can show you some of these steps, there is no easy way to see how they relate to each other, compare, or break down individual timings. Observability needed to debug, iterate, try out, and refactor your code is lacking.