Without knowing more about your specific problem, it seems you could do the action on data layer instead of UI.
Posts made by Arto
-
RE: Select all rows of the table
-
RE: How to use Vue Router inside Axios Interceptor
Hey
The way you import the router, it is not yet initialized.
Use the Quasarboot
function to access app context (including router).import { boot } from 'quasar/wrappers' export default boot(async ctx => { // here configure your axios instance await ctx.router.push('/path') Vue.prototype.$axios = axios })
-
RE: unexpected console statement errors in production build pwa after recent update
NPM works just fine. No need to create FUD.
This behaviour seems expected. Linter is checkingregister-service-worker.js
and has a no-console rule for production environment.
You can solve it by any of these (and probably other) means:- removing the logs
- disabling linter for that file (or only disable this specific rule)
- allowing all logs in production
- changing no-console severity to
warn
instead oferror
- not linting during build
…
profit?
-
RE: Quasar without the router
Turned out that mocking is enough to cheat Quasar. It senses that something is wrong
"export 'default' (imported as 'createRouter') was not found in 'app/src/router/index'
…but compiles. And yes, still too dirty.
-
RE: Backend for Quasar [SOLVED BY metalsadman]?
I will be, in near future, because Nest is interesting.
But can I ask why you even had this question? Quasar is quite backend agnostic in my experience. -
Quasar without the router
I wonder if it is possible to use Quasar/latest without the router?
I put together a simple app with only one view, and had no need for the router. Problem is that with every build, Quasar treats router as a dependency and throws. I can hack around it through modifying thegenerator.js
, but its obviously very dirty.
I haven’t tried, but imagine that mocking the router could work. But this is also too dirty for such a simple task.Is there maybe a way to disable the router as a dependency?
-
RE: Is there a 'Quasar way' of disabling browser pull-to-refresh?
Well, the best way to handle is
overscroll-behavior
. Problem with this is, that iOS does not support it. Still, right now it reduces my problem. -
Is there a 'Quasar way' of disabling browser pull-to-refresh?
Browsers have their native pull to refresh, which is something that I absolutely do not want in my swipe-heavy app.
Right now I have disabled it in quite standard way:body position: absolute overflow-y: hidden .app-wrapper position: absolute overflow: auto
This messes with Quasar’s scroll detection and my scroll events are not firing properly.
Any ideas how to solve it with the least amount of headache?