From f6c57d411fb4e437ffe86c3cea50fe026ada274d Mon Sep 17 00:00:00 2001 From: Eugene Fox Date: Fri, 20 Sep 2024 16:45:37 +0300 Subject: [PATCH] Updated Code style (markdown) --- Code-style.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Code-style.md b/Code-style.md index 52b502b..a758c6a 100644 --- a/Code-style.md +++ b/Code-style.md @@ -1,15 +1,15 @@ This article contains a set of rules and guidelines that you should follow when working on an issue. There's not much rules here, but it is good to follow some of the key points: -- Indetation and spacing +- Indentation and spacing - **Use tabs**, not spaces. - Use LF file separators (UNIX style). - Separate logical blocks with empty lines - Separate block statements (if/else, try/catch, switch, etc.) with empty lines - Always place opening braces on a new line - - Always place conditional statement on the a new line + - Always place conditional statement on a new line - Always make sure that there's no ESLint warnings. -- Priorize readability over performance. +- Prioritize readability over performance. - More comments is better. > [!TIP] @@ -19,5 +19,5 @@ There's not much rules here, but it is good to follow some of the key points: This project uses ESLint to maintain key aspects of the code style. It runs in following cases: - Project build (fails build if critical issues are found) -- Manual `npm run lint` command exectution +- Manual `npm run lint` command execution - [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) extension for VS Code is installed