Skip to content
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

message keys/check names #21

Closed
larshp opened this issue Mar 26, 2020 · 12 comments
Closed

message keys/check names #21

larshp opened this issue Mar 26, 2020 · 12 comments

Comments

@larshp
Copy link
Member

larshp commented Mar 26, 2020

#13 (comment)

we need to improve messages text. All those shortcuts look strange inside sci

@sbcgua

@sbcgua
Copy link
Collaborator

sbcgua commented Mar 26, 2020

sample

image

@larshp
Copy link
Member Author

larshp commented Mar 26, 2020

the data type in SAP is 10 characters, whereas the rule key in abaplint is string

can do a 10 character hash, but not sure it will be better

@sbcgua
Copy link
Collaborator

sbcgua commented Mar 26, 2020

Hmm. But how other messages work ? (I have no idea about SCI internal :(( )

image

@larshp
Copy link
Member Author

larshp commented Mar 26, 2020

hmm, is the column in above screenshot the same as from the first screenshot? cannot tell as its not part of it

@sbcgua
Copy link
Collaborator

sbcgua commented Mar 26, 2020

Yes, it is the lower part. But! I didn't run it via SCI actually.

image

You mean this one has just 10 symbols ?

image

@larshp
Copy link
Member Author

larshp commented Mar 26, 2020

yes, message codes are only 10 characters, data element SCI_ERRC, and its used to group messages of the same type in code inspector = rules in abaplint

the middle screenshot looks like the message description/text, not the message code

@larshp
Copy link
Member Author

larshp commented Jun 29, 2020

see comment in abaplint/abaplint-sci-client#42

@larshp
Copy link
Member Author

larshp commented Jun 30, 2020

try again, latest version of the abap code

@sbcgua
Copy link
Collaborator

sbcgua commented Jul 2, 2020

will do, but probably need to downport first ... I'll have a look in the coming days

@sbcgua
Copy link
Collaborator

sbcgua commented Jul 17, 2020

hmmmm

image

though debuggin showed that actually it is exception in check->run with Max depth 0 reached for class ZCL_EDE_PARTNER. Exiting dependency walk

@larshp
Copy link
Member Author

larshp commented Sep 2, 2020

double click the line to show the message

@mbtools
Copy link
Contributor

mbtools commented Oct 22, 2020

This should work properly now

@larshp larshp closed this as completed Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants