I think I solved one part. In the document it said :
“If your layout uses Vue Router sub-routes (recommended), then it makes sense to use Vue’s <router-view> component, which is just a placeholder where sub-routes are injected.”
I thought sub routes was /test and test/sub-route-page.
But that doesn’t seem to be the case, sub-routes = children pages
https://router.vuejs.org/en/essentials/nested-routes.html
I can’t figure out why the child page has a scroll bar.
Can we not do this?
<div v-for=“page in pages” v-bind:key =“page.key”>
<q-side-link item to={{page.path}} exact>
<q-item-main label>{{page.name}}</q-item-main>
</q-side-link>
</div>
I can’t seem to get the page value to use it on the to=.
I’m probably not doing the key right.
I think I solved one part. In the document it said :
“If your layout uses Vue Router sub-routes (recommended), then it makes sense to use Vue’s <router-view> component, which is just a placeholder where sub-routes are injected.”
I thought sub routes was /test and test/sub-route-page.
But that doesn’t seem to be the case, sub-routes = children pages
https://router.vuejs.org/en/essentials/nested-routes.html
I can’t figure out why the child page has a scroll bar.
Just trying to figure out how the Layout Component works.
I still don’t get the view code. hhr lpr llh
For the most part I have it how I want, but the right side bar seems to pass through the header when I open and close it. (Side bar is blow the header).
Not sure how to fix that.
How do I have the side bar start closed.
I can’t figure out how to load a menu page into the main view area. I tried setting up some routes /test/main that does take me to the page, but no menu at the top.
Not sure why, running quasar build it fails.
I can include the log if I need to.
~/dev/vueTest/Mobile-Apps/carrier-quasar $ quasar build
quasar-app@0.0.1 build /home/dev/vueTest/Mobile-Apps/carrier-quasar
node build/script.build.js
WARNING!
Do NOT use VueRouter’s “history” mode if
building for Cordova or Electron.
Cleaned build artifacts.
Building Quasar App with “mat” theme…
Build completed in 17.689s
Hash: df7151e820f066180baf
Version: webpack 3.11.0
Time: 17695ms
Asset Size Chunks Chunk Names
img/wheel.6a411cd.png 237 kB [emitted]
fonts/Roboto-Thin.90d3804.woff 87.8 kB [emitted]
fonts/Roboto-Regular.081b11e.woff 89.4 kB [emitted]
fonts/Roboto-Medium.303ded6.woff 89.7 kB [emitted]
fonts/Roboto-Bold.ad140ff.woff 89.2 kB [emitted]
fonts/MaterialIcons-Regular.012cf6a.woff 57.6 kB [emitted]
fonts/MuseoSans_500.62c0135.otf 62.5 kB [emitted]
img/login_carrier_back.b20aeb0.png 746 kB [emitted] [big]
img/EFS_Logo_Final_Color_White.9d3eeb8.png 76.4 kB [emitted]
fonts/Roboto-Light.37fbbba.woff 89.2 kB [emitted]
js/0.86059f383ec26c6c3631.js 20.1 kB 0 [emitted]
js/1.cb8865d99c116e668968.js 4.54 kB 1 [emitted]
js/2.6f5f624c4e4a32458425.js 1.97 kB 2 [emitted]
js/vendor.js 272 kB 3 [emitted] [big] vendor
js/app.js 1.03 kB 4 [emitted] app
js/manifest.js 1.44 kB 5 [emitted] manifest
app.667445a3ad49a7335de77cc5ca1ce32e.css 117 kB 4 [emitted] app
index.html 582 bytes [emitted]
ERROR in js/0.86059f383ec26c6c3631.js from UglifyJs
Name expected [js/0.86059f383ec26c6c3631.js:407,6]
npm ERR! Linux 3.13.0-24-generic
npm ERR! argv “/usr/bin/node” “/usr/bin/npm” “run” “build”
npm ERR! node v6.12.3
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! quasar-app@0.0.1 build: node build/script.build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the quasar-app@0.0.1 build script ‘node build/script.build.js’.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the quasar-app package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node build/script.build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs quasar-app
npm ERR! Or if that isn’t available, you can get their info via:
npm ERR! npm owner ls quasar-app
npm ERR! There is likely additional logging output above.
Kind of two parts.
What I need is some quasar test command. I think test would be closer to production then to dev.
Something like quasar test would build with a QA url as some variable.
Eventually will need this with cordova. quasar build android --QA
Really what is needed is a way to tell the vue code which server to point to.
Local host would be local host (or an ip address)
Dev would point to dev.server.com
Test would point to qa.server.com
prod would point to www.server.com
I know webpack can do this, Quasar seems to have its own configuration.
Another question is how to include this in some “services” javascript file. Vue doesn’t have services, sounds like just creating a JS file with some axios commands in. This is where I need to know which server I’m pointing to.
Thanks