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
How do you envision this feature/change to look/work like?
During the development of my plugin card, for some reason, the build process once exceeded 40,000ms. When saving the code, there is no specific perception of whether everything is in the queue, or the prompt is being built. The most annoying thing is that after multiple hot reloads, I look at the terminal page 🟢 DONE | Extension re-packaged in, and it is difficult to tell whether the build is now completed. So I hope to add a loading information prompt at the beginning of the build/hot reload, and no longer display loading when the loading is completed or failed, to improve the perception of the build and hot reload.
What is the purpose of this change/feature? Why?
Provide a better user experience by letting users know that a build is in progress;
clearly indicate the start and end of a build;
and stop the loading animation in time when a build fails to avoid user confusion;
(OPTIONAL) Example implementations
Specifically, the functional implementation:
Display the loading animation when the build/hot reload starts in the terminal
Stop and remove the animation when the build succeeds or fails
Use the startLoading() and stopLoading() functions to control the loading animation
(OPTIONAL) Contribution
I would like to contribute to this RFC via a PR
Verify canary release
I verified that the issue exists in plasmo canary release
* feat: add build loading awareness in the terminal
- Import loading awareness animation for build process
- Start loading animation when build and rebuild starts
- Stop loading animation when build succeeds or fails
* refactor: improve loading animation code structure
- Move state management to a single state object
- Extract LOADING_TEXT to constants
- Add consistent bracket style
---------
Co-authored-by: L <[email protected]>
How do you envision this feature/change to look/work like?
During the development of my plugin card, for some reason, the build process once exceeded 40,000ms. When saving the code, there is no specific perception of whether everything is in the queue, or the prompt is being built. The most annoying thing is that after multiple hot reloads, I look at the terminal page 🟢 DONE | Extension re-packaged in, and it is difficult to tell whether the build is now completed. So I hope to add a loading information prompt at the beginning of the build/hot reload, and no longer display loading when the loading is completed or failed, to improve the perception of the build and hot reload.
What is the purpose of this change/feature? Why?
Provide a better user experience by letting users know that a build is in progress;
clearly indicate the start and end of a build;
and stop the loading animation in time when a build fails to avoid user confusion;
(OPTIONAL) Example implementations
Specifically, the functional implementation:
Display the loading animation when the build/hot reload starts in the terminal
Stop and remove the animation when the build succeeds or fails
Use the
startLoading()
andstopLoading()
functions to control the loading animation(OPTIONAL) Contribution
Verify canary release
plasmo
canary releaseCode of Conduct
The text was updated successfully, but these errors were encountered: