-
Notifications
You must be signed in to change notification settings - Fork 61
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
github actions: issue error if mismatch ABAP <> Schema #476
Conversation
I guess you mean if they "do not match" or "mismatch", don't you? ;) |
fixed 😁 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool.
Looks good to me.
@SAP/abap-file-formats-team Would someone else review this PR, too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :)
Suggestions:
More suggestions are welcome :) |
true, however, on longer term I'd suggest it to actually update the PR with the file but anyhow, no trouble renaming it for now |
"Validate JSON schema against ABAP type" sounds good to me.
However, the next check in the list is called "Validate JSON".
Maybe rename this one, too, so it's clear what each of them does?
|
I had this also in mind, but I think we can differentiate both. @larshp "Executive" Decision: (as requested by you ;)) |
updated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good to me. 👍
github action will now give an error if the ABAP code and generated schema does not match
Note that "Generate Schemas" is not a required status check, so it will not block merges
ENHO skipped due to #409