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
Feature/14285 migrate event definitions page to new bulk friendly design #14502
Feature/14285 migrate event definitions page to new bulk friendly design #14502
Conversation
84bdaaa
to
116fca0
Compare
bce953a
to
ead564b
Compare
…ge-to-new-bulk-friendly-design
The UI doesn't adjust horizontally the way I'd expect. I can never get rid of the horizontal scroll bar, even in maximized view, because the Also: |
System Notification Events is still showing as disabled - should always be enabled. Note that this is not a scheduled event, so you can't use that as the conditional. |
Hi @patrickmann, thank you, I fixed that. |
a845172
to
720bcd0
Compare
@@ -0,0 +1,5 @@ | |||
type = "c" # One of: a(dded), c(hanged), d(eprecated), r(emoved), f(ixed), s(ecurity) | |||
message = "Changed event definitions and notifications to new paginated list and entity list ui component." |
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.
Still think the CL should mention bulk operations, since that is the new feature.
@Path("/bulk_schedule") | ||
@Consumes(MediaType.APPLICATION_JSON) | ||
@Timed | ||
@ApiOperation(value = "Enable a bulk of event definitions", response = BulkOperationResponse.class) |
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.
"Bulk" sounds strange in this context - "group" or "selection" or "multiple" would be better.
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 used bulk
to makes this consistent with bulk_delete
used here and in streams.
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.
That's fine. I just mean the string "Enable a bulk of event definitions"
. Bulk as a noun refers to a homogeneous mass, rather than a grouping of distinct elements.
If we want to stick with it, then I prefer e.g. "Enable event definitions in bulk"
@Path("/bulk_unschedule") | ||
@Consumes(MediaType.APPLICATION_JSON) | ||
@Timed | ||
@ApiOperation(value = "Disable a bulk of event definitions", response = BulkOperationResponse.class) |
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.
Replace "bulk" - see above
I can perform bulk disable on System Notification Events definition and get a success confirmation, even though it does not get disabled. For consistency, it should show a warning like it does for an attempted bulk delete. |
adjusted the swagger docs and added additional validation for disabling events in the backend |
Attempting to delete the System Event Definition is blocked with an appropriate error message. |
I think we should create a separate issue for handling this. When selecting multiple Event Definition and the System Event Definition, it shows the error message "One of the event definitions could not be deleted" which is expected, but in this case, it looks like something is broken - which is not. I think it's not blocking but would be nice to handle this case in the future. |
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.
Checked it again and looks good now! The build is still red though.
…ge-to-new-bulk-friendly-design
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 opened #14786 for the inconsistencies related to deleting System Notification event definition.
The rest looks good.
On save, the UI is passing back the "scheduled=false" param from the context. There's several ways we could fix this, but it's probably easiest to not throw an exception, but just ignore the unschedule call. This probably got broken with #14502
* Fix saving of system notification event definition On save, the UI is passing back the "scheduled=false" param from the context. There's several ways we could fix this, but it's probably easiest to not throw an exception, but just ignore the unschedule call. This probably got broken with #14502 * changelog
* Fix saving of system notification event definition On save, the UI is passing back the "scheduled=false" param from the context. There's several ways we could fix this, but it's probably easiest to not throw an exception, but just ignore the unschedule call. This probably got broken with #14502 * changelog (cherry picked from commit d1b77ed)
* Fix saving of system notification event definition On save, the UI is passing back the "scheduled=false" param from the context. There's several ways we could fix this, but it's probably easiest to not throw an exception, but just ignore the unschedule call. This probably got broken with #14502 * changelog (cherry picked from commit d1b77ed)
Migrate Event Definitions and Event Notifications to new Entity List
closes #14285
Description
paginated
endpoints for event definitions and notifications, deprecated old endpointsTypes of changes