-
1. Define better eslint standard.
2. Base on some code standard guideline.
-
This is where code standards are updated/stored.
-
- give variables/parameters names that let the developer infer the type of the variable by looking at the code without having to debug it
- example:
```smalltalk
printOn: aWriteStream
"instead o…
-
4- Is the code understandable and readable?
No , 80%
Related Issues: NO comments in code .
-
Is indentation used properly?
NO , 50 % ;
most parameters and variables not use spaces between simples ( , = , > ,< ) ;
Ex: long key=entity.getKey().getId() , ... etc
-
As of https://github.com/ClassicPress-research/classic-commerce/pull/190 the coding standards checks on every PR are disabled. This is because the coding standards checks run whenever a file is chang…
nylen updated
4 years ago
-
We need to document the coding standards … :+1:
sqndr updated
8 years ago
-
1-it was be easy to understand and read this code but in some Pieces of code non understandable such as the service of show requests
-
I was wondering if there is any coding standard that you'd like us to conform to when making commits to the GWEN code. I noticed some recent code that was merged in had inconsistent if/else statement…
-
This is a discussion on coding standards for this project