Refresh aggregate infos after command execution

[codeliner]

This PR adds a quick fix for auto refreshing aggregate list and aggregate details after command execution. It is not perfect, because it is purely based on command dialog being closed.

A better way would be to refresh after successful command execution. This way we could automatically close the dialog and trigger refresh. In case command execution fails the dialog would stay open and no refresh is triggered. @martin-schilling this would be perfect case for an event dispatcher redux middleware (you remember our discussion about the topic?).

Anyway, I think the quick fix is ok for now. It definitely increases UX because at the moment you have to refresh the browser to see updates.

[martin-schilling]

Looks good and should to the job for now. I think, however, that I am going refactor it to keep this logic inside the sagas later to prevent unnecessary state from being passed around. Or was there a special reason you did it this way that I am not seeing?

[martin-schilling]

Oh seems like I missed your comment. Using an event dispatcher middleware, like we discussed, would work but you want to reload state anyway, right? Isn't that something that can simply be triggered through the redux saga handling the command exectution? https://github.com/event-engine/cockpit/blob/master/src/saga/executeCommandFlow.ts#L17

[codeliner]

Oh wait you're right! I was a bit too fast with my quick fix :D I'll check the saga option. Missed the fact that queries are dispatched from effect functions but state is selected from redux store. So dispatching same queries from a saga should refresh the components 👍

[codeliner]

Ok, let's do the refactoring later in the follow up #8
At the moment the saga does not have enough information. It only knows about the command, but not which aggregate data should be fetched again.

[martin-schilling]

Ok, let's do the refactoring later in the follow up

I already collected some other refactoring tasks for later. Maybe opening up a board to preserve those things would be a good idea?

It only knows about the command, but not which aggregate data should be fetched again.

Yes I thought about that too. I think it would probably be a good idea to trigger some action here https://github.com/event-engine/cockpit/blob/master/src/AggregateDetailsPage.tsx#L15-L17 to push this information into the redux store and use it as the source of truth. Then any sub-components would simply rely on that information instead of getting it from the parent through the props. The required information would then be available for the sagas too.
Do you have a better idea?