|
2 | 2 |  |
3 | 3 |  |
4 | 4 |  |
5 | | - |
| 5 | + |
6 | 6 |
|
7 | | - |
| 7 | + |
8 | 8 |  |
9 | | - |
| 9 | + |
10 | 10 |  |
11 | 11 |
|
12 | 12 |  |
@@ -68,13 +68,13 @@ Code standard covers more than just ESLint: |
68 | 68 | - Code formats are mostly ensured by Prettier. |
69 | 69 | - Static analyze of the JavaScript and TypeScript Code, using ESLint. |
70 | 70 | - Prebuild check by TypeScript Compiling. |
71 | | -- Best practices are enforced by Stylelint. (TODO) |
| 71 | +- Best practices are enforced by Stylelint. |
72 | 72 | - Some conventions and project-specific rules are implemented by custom rules and scripts. |
73 | 73 | - Git commit should follow the conventional commits standard. |
74 | 74 |
|
75 | 75 | ## Test |
76 | 76 |
|
77 | | -The whole project has a 100% test coverage, with detailed tests. |
| 77 | +The whole project has a 100% unit test coverage, with detailed tests. |
78 | 78 | I totally understand the importance of complementary test coverage, and enforce it in my project. |
79 | 79 |
|
80 | 80 | ## Accessibility |
|
0 commit comments