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/checks/deprecated-classes.md
+10-11Lines changed: 10 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,23 +12,22 @@ You can check the list of supported objects in the `constructor` of the `y_check
12
12
13
13
### How does the check work?
14
14
15
-
This check searches for the usage of deprecated classes.
15
+
This check searches for the usage of deprecated classes. For instance:
16
+
```abap
17
+
DATA aunit TYPE REF TO cl_aunit_assert.
18
+
```
16
19
17
20
### How to solve the issue?
18
21
19
-
Use the newer objects instead.
22
+
Reference non deprecated newer objects instead. For the above example, a corrected code would look like:
23
+
```abap
24
+
DATA aunit TYPE REF TO cl_abap_unit_assert.
25
+
```
20
26
21
27
### What to do in case of exception?
22
28
23
-
You can suppress Code Inspector findings generated by this check using the pseudo comment `"#EC DEPRECATED_CLAS`.
24
-
The pseudo comment must be placed right after the statement.
25
-
26
-
Before the check:
29
+
In very special and restricted cases (e.g.: Keep release compatibility on downports), you can suppress Code Inspector findings generated by this check using the pseudo comment `"#EC DEPRECATED_CLAS`. The pseudo comment must be placed right after the statement:
27
30
```abap
28
-
DATA aunit TYPE REF TO cl_aunit_assert.
31
+
DATA aunit TYPE REF TO cl_aunit_assert. "#EC DEPRECATED_CLAS`
0 commit comments