You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When double-clicking on a graph node we're making two graph generation calls to the backend. Furthermore, when double clicking on an operation node, the initial request is corrupt.
We should only be making one, valid, graph generation call on a double-click.
The text was updated successfully, but these errors were encountered:
Pushing a new node graph URL will already cause a redux update when the
page initializes. So, remove the redundancy and prevent two calls to the
backend.
Furthermore, fix an issue on operation node double-click by properly
setting the target node params.
kiali/kiali#3649
* We don't need to both update the URL and update redux on a double-click
Pushing a new node graph URL will already cause a redux update when the
page initializes. So, remove the redundancy and prevent two calls to the
backend.
Furthermore, fix an issue on operation node double-click by properly
setting the target node params.
kiali/kiali#3649
When double-clicking on a graph node we're making two graph generation calls to the backend. Furthermore, when double clicking on an operation node, the initial request is corrupt.
We should only be making one, valid, graph generation call on a double-click.
The text was updated successfully, but these errors were encountered: