You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/advanced/insights/linting.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ outline: [2, 4]
5
5
6
6
The frontend JS code and the backend abap code are static code checked with every PR.
7
7
8
-
### Backend - abaplint
8
+
### abaplint
9
9
10
10
The project uses [abaplint](https://abaplint.app/) for static code analysis, ensuring code quality and adherence to ABAP best practices.
11
11
@@ -15,6 +15,9 @@ You can review the project-specific abaplint configuration [here.](https://githu
15
15
#### Dashboard
16
16
All statistics and results from the abaplint analysis are available on the abaplint dashboard [here.](https://abaplint.app/stats/abap2UI5/abap2UI5)
17
17
18
-
### Frontend - ui5lint
18
+
### ui5lint
19
19
20
-
The project uses the [ui5linter]((https://github.com/SAP/ui5-linter)) for static code analysis of frontend artifacts. The linter checks for issues such as deprecated API usage and ensures compatibility with UI5 2.x. The default configuration is applied.
20
+
The project uses the [ui5linter]((https://github.com/SAP/ui5-linter)) for static code analysis of frontend artifacts. The linter checks for issues such as deprecated API usage and ensures compatibility with UI5 2.x.
0 commit comments