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
AssembleApp running on jupyter server goes through steps to submit feature: (1) extract code from payload, (2) fork upstream repo if applicable (3) clone to tmp (4) render feature module (5) copy code to feature module (6) commit files (7) push to origin (8) pull request to upstream
after failure or success, a new modal shows result to user
Desired behavior
user confirms they want to submit feature
UI immediately shows some sort of "processing" animation, ideally showing the actual steps the server is taking
after failure or success, the processing animation is replaced by the result modal
The text was updated successfully, but these errors were encountered:
I would like to approach implementing this behavior in two separate stages:
show a simple spinner while the feature is being submitted, just to communicate to the user that something is happening
this can be achieved my showing a modal immediately after the user confirms the feature in the dialog, instead of waiting for the api call
show detailed steps instead of a spinner:
when a feature is submitted to the extension backend, the state of the feature submission is kept track of in a global variable (or more specifically in a dictionary, to keep track of multiple submissions concurrently)
the feature submission endpoint returns a random uuid that can be used by the frontend to make repeated (~500ms) calls to the backend in order to fetch the state of the submission as it updates and update the animation accordingly.
Current behavior
Desired behavior
The text was updated successfully, but these errors were encountered: