fanfan54old / epitech-coding-style-checker

:white_check_mark: Check your epitech coding style while you're coding.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

epitech-coding-style-checker

Check your coding style while you're coding πŸš€

demo

Thanks to ronanboiteau's checker

Features

  • βœ… Lines with too many columns (> 80).
  • βœ… Forbidden files: every regular file that does not match Makefile, *.c or *.h (ex: *.o, *.gch, bsq, ...) & that is not mentioned in a .gitignore file located in your current working directory.
  • βœ… Too broad filenames (ex: string.c, algo.c, my_algorithm.c, ...).
  • βœ… Missing or corrupted header in sources files (.c), headers (.h) & Makefiles.
  • βœ… Functions that contain more than 20 lines.
  • βœ… Several semicolon-separated assignments on the same line.
  • βœ… Forbidden functions (printf(), dprintf(), atoi(), memcpy(), scanf(), strlen()...).
  • βœ… Trailing space(s) and/or tabulation(s) at the end of a line.
  • βœ… Filenames that don't respect the snake_case naming convention.
  • βœ… Condition and assignment on the same line.
  • βœ… Directory names that don't respect the snake_case naming convention.
  • βœ… Too many functions in file (> 5).
  • βœ… Functions with no parameters that don't take void as argument in their declaration.
  • βœ… Functions with too many arguments (> 4).
  • βœ… Space(s) in indentation.
  • βœ… Missing space after keyword.
  • βœ… Misplaced pointer symbol(s).
  • βœ… Macros used for constants.
  • βœ… Macros containing multiple assignments.
  • βœ… Too many else if statements.
  • βœ… Misplaced comments.
  • βœ… Missing space after comma.
  • βœ… Missing space around binary or ternary operator (=, ==, !=, <=, >=, &&, ||, +=, -=, *=, /=, %=, &=, ^=, |=, |, ^, >>, <<, >>=, <<=).
  • βœ… Extra space after unary operators (!, sizeof, ++, --).
  • βœ… Forbidden keyword (goto).
  • βœ… Functions must be separated by one and only one empty line in .c files.
  • βœ… Check he Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file.

For example if there is an image subfolder under your extension project workspace:

Requirements

# Fedora
sudo dnf install ruby
# Macos
brew install ruby

Install

  • Do CTRL + P on vscode.
  • Past this ext install lucasmarandat.epitech-coding-style-checker
  • Open an project folder and enjoy !

Have an issue ?

Write it here.


Enjoy!

About

:white_check_mark: Check your epitech coding style while you're coding.


Languages

Language:Ruby 87.1%Language:TypeScript 12.9%