-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CHECK_63: Error message not displayed correctly #1112
Comments
guess something changed in the abapdoc api, try setting a breakpoint |
The check successfully reaches method
So it doesn't seem like this is a problem with the abap Doc API to me. Any other ideas? |
Ok, step by step a little further. :-) |
A PR is welcome. :-) |
I didn't submit a pull request because I'm not happy yet with how the text turns out. Compare it to check 001 for example: How can this text be changed? I tried to change insert_scimessage(
iv_code = '001'
iv_text = 'ABAP Doc parameter name is inconsistent' ). |
That's weird! I'll check the installation and report back. (Could take a while, I'm having some authorization problems right now...) |
Are we still talking about the same problem? I'd be actually okay with the way it already works in your previous screenshots, it just doesn't seem to work on my system. 😅 |
Right, so I have a bit more experience with ATC checks now and I think I know what's going on now.
I'll provide a pull request to fix this. |
I've changed the message from However, it doesn't work in ADT: If I change the error code from Restarting my own PC didn't help, and it also behaves the same for colleagues. Maybe there is some kind of additional caching for the ATC message check? I'll keep an eye on it. |
I suspect that this was the case. The error message is correctly displayed for |
I activated CHECK_63 (ABAP Doc - Check parameter consistency) but the errors are not displayed properly. The message of each finding is "Unknown error code" and the navigation always leads to the start of the class, not the abap Doc parameter.
Here's an example (the faulty parameter is
param_3
):Any idea why this happens? Thanks!
The text was updated successfully, but these errors were encountered: