-
Notifications
You must be signed in to change notification settings - Fork 17
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
feat(schedule)!: show schedule errors and nest object #795
Conversation
whats the plan for adding the other changes made in go-vela/server#1108 like nested repos? |
I'll attach the nested Schedule and types migration changes to this PR |
|
||
msgRow = | ||
tr [ class "error-data", Util.testAttribute "schedules-error" ] | ||
[ td [ attribute "colspan" "6" ] |
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.
is this "6" supposed to match the number of columns?
if so maybe we can make the value dynamic depending on the number of headers?
[ td [ attribute "colspan" "6" ] | |
[ td [ attribute "colspan" (String.fromInt <| List.length tableHeaders) ] |
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.
im just nitpicking. i realize now that its hardcoded in some places, so whatever.
but i was thinking about this spot when i wrote that:
https://github.com/go-vela/ui/blob/main/src/elm/Components/Table.elm#L131
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.
I took that snippet from viewHookError
in src/elm/Pages/Org_/Repo_/Hooks.elm
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.
sweet, figured 👍
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.
looks good overall. nice job. only thing missing that i would like to see is a (cypress) test to make sure that error is shown when returned from a schedule call.
Good suggestion. I'll create one. |
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
Description
Whenever a user has a YAML bug in their pipeline, or any other build-breaking error that short-circuits pipeline execution, they can usually find these error in the Audit tab, where we populate the hook with the error message.
This is currently not available for schedules. Instead, the error is just logged.
Desired View
Related
go-vela/community#872