From 74755c8bef4293ce32476793aef5881a19af825f Mon Sep 17 00:00:00 2001 From: Ayush Chugh Date: Sun, 29 Dec 2024 18:47:25 +0530 Subject: [PATCH] docs: console.log invaluable typo (#9234) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Console.logs are valuable in development so changed `invaluable` to `valuable` --------- Co-authored-by: ehconitin Co-authored-by: Félix Malfait --- .../developers/frontend-development/best-practices-front.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/twenty-website/src/content/developers/frontend-development/best-practices-front.mdx b/packages/twenty-website/src/content/developers/frontend-development/best-practices-front.mdx index 8b1b0a4e2903..c48d0b01d615 100644 --- a/packages/twenty-website/src/content/developers/frontend-development/best-practices-front.mdx +++ b/packages/twenty-website/src/content/developers/frontend-development/best-practices-front.mdx @@ -149,9 +149,9 @@ They are often not necessary and will make the code harder to read and maintain ## Console.logs -`console.log` statements are invaluable during development, offering real-time insights into variable values and code flow. But, leaving them in production code can lead to several issues: +`console.log` statements are valuable during development, offering real-time insights into variable values and code flow. But, leaving them in production code can lead to several issues: -1. **Performance**: Excessive logging can affect the runtime performance, specially on client-side applications. +1. **Performance**: Excessive logging can affect the runtime performance, especially on client-side applications. 2. **Security**: Logging sensitive data can expose critical information to anyone who inspects the browser's console.