Loadingbar - disable per component/allow-list?
See original GitHub issueIs your feature request related to a problem? Please describe. I really like the loadingbar plugin, however it doesn’t play nicely when doing a lot of API requests.
For instance, I’m running a VOD app which receives segments every X seconds, leading to the loadingbar being activated all the time.
Describe the solution you’d like Allow to disable the loadingbar per component or allow/block-list.
Describe alternatives you’ve considered
config: {
loadingBar: {
skipHijack: true
},
},
However, this doesn’t integrate nicely with API requests and I need to manually calculate each loading.
Additional context N/A
Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (12 by maintainers)
Top Results From Across the Web
Remove Loading Bar (Front End) | Not Helpful - WordPress.org
Your plugin displays a “loading” or “progress” bar in the front end when comments are loaded on affected website pages (click here). This...
Read more >Possible to disable a progress bar in swing? - Stack Overflow
The disabled appearance is controlled by the UI delegate for a given Look & Feel. For example, the Mac's com.apple.laf.
Read more >Loading - Nuxt
Out of the box, Nuxt gives you its own loading progress bar component that's shown between routes. You can customize it, disable it...
Read more >Unified Agent - Disable Progress Bar Prints in the Log
To disable such prints, add the following command to the Unified Agent configuration file: showProgressBar=false.
Read more >How To Disable The Loading Bar | Bubble Tutorial
This quick tips shows you how to completely hide the Bubble loading bar on a page in 2 easy steps to regain control...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@maggie0002 No, because quasar.conf.js runs in a Nodejs context, and that function should be part of your UI code. Use the setDefaults() in a boot file instead.
You can use whatever your heart desires, as long as you return a
Boolean
value 🙂