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
As flows get executed by the platform, the user should have a real-time understanding of their status.
In the Dataset Flows View:
The status of the flow should update periodically without manual refreshing (Note: Implemented temporarily via timer-based polling)
There should be a refresh button to force manual refreshing of flow statuses without a page reload - DONE
If the latest dataset flow has failed, this should be indicated in the Dataset View component:
Note: the status of the flows should be visible for anonymous or logged users if canView permission is set (always set for public datasets, will not be set by default in future for private datasets).
the UI reads initial status of the flows, as currently, including tiles view, main table view, and history view
Refresh button also reads full status
but other than these, all intermediate changes should come incrementally (from subscription), and should be propagated into UI components without re-sending heavyweight requests
As flows get executed by the platform, the user should have a real-time understanding of their status.
Note: the status of the flows should be visible for anonymous or logged users if
canView
permission is set (always set for public datasets, will not be set by default in future for private datasets).Consider using GraphQL Subscriptions to implement these updates.
Internally, make sure:
Related BE ticket: kamu-data/kamu-cli#275
The text was updated successfully, but these errors were encountered: