I’m trying to show some examples of quasar and vuejs.
Also adding some libraries to enhance.
I hope it help someone and make Quasar bigger.
I’m trying to show some examples of quasar and vuejs.
Also adding some libraries to enhance.
I hope it help someone and make Quasar bigger.
WORKING ALIAS
let path = require('path')
build: {
scopeHoisting: true,
vueRouterMode: 'history',
// gzip: true,
// analyze: true,
// extractCSS: false,
// useNotifier: false,
extendWebpack (cfg) {
cfg.module.rules.push({
enforce: 'pre',
test: /\.(js|vue)$/,
loader: 'eslint-loader',
exclude: /(node_modules|quasar)/
})
cfg.resolve.alias = {
...cfg.resolve.alias,
'@components': path.resolve(__dirname, './src/components'),
'@helpers': path.resolve(__dirname, './src/helpers'),
'@module1': path.resolve(__dirname, './src/domains/module1),
....
}
}
},
@Zyme
Try
<q-transition appear enter="fadeInLeft" leave="fadeOutRight" mode="out-in">
<router-view :key="$route.name" />
</q-transition>
Remember to read http://quasar-framework.org/components/transition.html for imports
Tks all. I will update to 0.14 after the release and finish the project tasks.
Lets keep helping quasar community grows!
Hi, im using collapsible inside <template>.
I will upload a video working when get back in company.
With litle css and no-margin / no-padding etc , works very good.
Additional to this, if you use VS Code and want CTRL + click - open the import file using alias.
Create a jsconfig.json in root folder of project and :
{
"compilerOptions": {
"baseUrl": "./",
"paths": {
"~/*": ["./src/*"],
"@components/*": ["./src/components/"],
"@helpers/*": ["./src/helpers/*"],
"@module1/*": ["./src/domains/module1/*"],
}
}
}
Reboot VSCode
@rstoenescu Focus on going man. Quasar needs to be know.
The community can wait a little bit for you to prepare.
Quasar rocks!
Hi!
Can use a direct v-model too.
<template slot="col-message" slot-scope="cell">
<q-input :v-model="table[cell.row.__index].message" ></q-input>
</template>
Hi @Mayank , hope i can help you
Where you start your vue ( main.js normaly) add :
quasar/dist/quasar.mat.css
) or require(quasar/dist/quasar.ios.css
)Now start you Vue whit :
Quasar.start(() => {
/* eslint-disable no-new */
new Vue({
el: '#q-app', // this ID must exist in your index.html
router,
render: h => h(App),
})
})
I’m using https://github.com/quasarframework/app-extension-dotenv/tree/dev/app-extension.
and i need an build android with staging config, but every build point to .env (production)
No @Hawkeye64 , i have read it. Tks
I need a stagging build.
I searched in docs, but didin’t find.
Can i set process.env.DEV = true on quasar build ?
or
set process.env.PROD = false on quasar build ?
Thanks!
Hi guys.
I’m migrating an application from 0.17 to 1+.
Why the ‘filter feature’ become so complex ? i understand the need of a complex function to handle the filtering. But most of cases just a filter like 0.17 works perfect.
Someone have a solution for it ? some forms have 4 5 selects with filter needing, it make alot of boilerplate code…
Yea man, i know, we must read docs before post something, but this project was compiling in early versions whitout manage any icons.
In upgrade docs dont mention this change of mandatory.
Tks for the help man, the problem is:
quasar docs must put this part https://quasar.dev/quasar-cli/developing-cordova-apps/app-icons-cordova
as mandatory to generate, in previus versions this are not.