@IvanGV
GH = Git Hub
https://github.com/quasarframework/quasar/issues

@Shoooryuken
This is a common Vue error. You should never modify the props.
Instead create a computed property which returns options and on update emit an event to parent.

Something on the line of this:

<template>
    <q-card>
        <q-dialog square full-width v-model="$_options" position="bottom" class="">
            <q-card-section class="row items-center">
                <div class="text-h6">{{ title }}</div>
                <q-space />
                <q-btn icon="close" flat round dense @click="close" />
            </q-card-section>
        <q-card-section class="items-center no-wrap">....</q-card-section>
    </q-card>
</template>
<script>
export default {
    props: {
        options: { type: Boolean, default: false }
    },
    computed: {
        $_options: {
            get: function () {
                return this.options;
            },
            set: function (val) {
                this.$emit('update-options', val);
            }
        }
    },
    methods: {
       activate: function (el) {
            this.$emit('update-options', false)
            this.filter = el
        },
        close () {
            this.$emit('update-options', false)
        }
    }
}...

https://forum.vuejs.org/t/vue-warn-avoid-mutating-a-prop-directly-since-the-value-will-be-overwritten-whenever-the-parent-component-re-renders/21757

@IvanGV btw there is a way of doing it if you are very keen : )
You have to create your own custom spinner component. There is a vague example here:
https://forum.quasar-framework.org/topic/4535/custome-spinner/3

is there a search in your docs? Perhaps I need new glasses, thanks

@adsaviation

Use Google site search
site:https://quasar-framework.org/ Autocomplete

https://www.google.com/search?q=site%3Ahttps%3A%2F%2Fquasar-framework.org%2F+Autocomplete&oq=site%3Ahttps%3A%2F%2Fquasar-framework.org%2F+Autocomplete&aqs=chrome..69i57j69i58.371j0j7&sourceid=chrome&ie=UTF-8

If you bookmark that search page all you have to do is retype the search keyword.

There is also the browser built in search I am sure you use it too. CTRL + F / CMD + F just to search the page. I use that a lot.

I love quasar too. I am not missing the search feature for the docs.

I was using yarn both globally and locally. Then two days ago I was following the upgrade guide to quasar 1.
https://v1.quasar-framework.org/start/upgrade-guide

And I could not get passed the line

module.exports = {
  presets: [
    '@quasar/babel-preset-app'
  ]
}

that is until switched to npm for global use. Why that is I have no idea : ) but now I have npm for global use and yarn for local / per project use.

Worth noting their suggestion:
6. We recommend yarn whenever possible because of its speed and efficient use. However, when using globals, we still recommend using npm, especially if you use nvm (Node Version Manager).

I would love not to have to deal with both.

Yes ! Thank you for that link. No need for the mixins and also it is not $props I need but $attrs. Sorry it is kind of ended up to be a question about Vue rather then Quasar.

So the final wrapper QInput for me looks like this

<template>
    <q-input
    :value="value"
    v-on="$listeners"
    v-bind="$attrs"
    @keyup.enter="updated"
    @blur="updated"
    @keydown.meta.83.prevent="updated"
    />
</template>

<script>

export default {
    props: ['value'],
    methods: {
        updated: function () {
            this.$emit('save');
        }
    }
};
</script>
```

This should really be part of Quasar I feel and not an extension. I am going to start bodging the drag and drop today into qTable to start with and then qTree. And many will end up doing the same because sooner or later you will need it. How else are you supposed to organise a tree for example ? There is not many other ways to do it.

@ssuess
I think the rules :rules="['date']" will cause this to be added. This is where the error messages go. Which are position: fixed because of the animation I think.

Might be interesting to read
https://github.com/quasarframework/quasar/issues/3357

See also
https://v1.quasar-framework.org/vue-components/input
search for bottom-slots

@leon I don’t know but if you need a file or two in the dist directory you can configure webpack to copy it there. In my case I needed the file .realsync.

extendWebpack (cfg) {
    cfg.module.rules.push({
        enforce: 'pre',
        test: /\.(js|vue)$/,
        loader: 'eslint-loader',
        exclude: /node_modules/,
        options: {
            fix: true
        }
    });
    if (cfg.output) {
        const CopyWebpackPlugin = require('copy-webpack-plugin');
        cfg.plugins.push(
            new CopyWebpackPlugin([{
                from: '.realsync',
                to: cfg.output.path
            }
            ])
        );
    }
}

@Cobeland As other say the beta changes are easy to deal with. I will be using it in production soon and not worried that it is in beta. For me changing from 0.17 to v1 was more of headache. But I guess it was expected that is why it is a major release.

I wouldn’t pressure them either about the beta status. They need the time to sort out all the small stuff.

@Suo I wouldn’t give up just yet. : ) You should try and wrap your head around it. What @metalsadman and @s-molinari is suggesting here is very well known way of doing this. And there is no reason why it shouldn’t work for you other than something trivial in your code.

@kasparesky I think that those events only get passed to the listeners if you pass them in on the first place when you use the functions on the drawer.
I might be wrong though … just a guess.
https://codepen.io/turigeza/pen/qBbYvXx?editors=1010

It kind of make sense. I mean if you set the model of the drawer what sort of event are you expecting to receive ? I don’t think there is way to know what event caused the model change.

So it seems
https://github.com/quasarframework/quasar/blob/dev/ui/src/components/drawer/QDrawer.js

@RNat
You mean you would like to override the data in the rows ? It is your rows you are loading which contain the model for your select and toggle components. So you have to make sure the rows contain those properties. If they don’t and you would like to set them you should do it when you load them. In your case here

rAccData() {
      return this.Acc.filter(a => a.testType === testTypeEnum.A1);
},

You could do something like

return this.Acc.filter(a => a.testType === testTypeEnum.A1).forEach(row => this.$set(row, 'rToggle', true))

Btw what is value="check" supposed to do ?

@amoss I use
https://atom.io/packages/linter-eslint for Atom
Maybe this one here for vscode.
https://github.com/microsoft/vscode-eslint will get you want you want or half way there anyway.
As @dobbel pointed out it doesn’t do properties or methods.
Isn’t it the default when you start a Quasar project to have this running with quasar dev ?

@Ewa If you put ref="domainInput" you should call this.$refs.domainInput.validate and not this.$refs.input.validate(...)

IN case anybody comes across this I have ended up disabling swipe on q-tab-panels on devices which are not touch enabled. I think it make more sense this way and you can select text this way too which also caused issue in the past.

<q-tab-panels class="col rounded-borders" v-model="_active_tab" animated keep-alive infinite :swipeable="$q.platform.has.touch">

@labs20 I know it’s not a solution you are asking for but why not go single column layout at this screen width ? It would be nicer looking and you could still see what is selected.

If you still prefer the ellipsis instead check out this pen.
https://codepen.io/turigeza/pen/oNbqeMb?editors=1010

<q-select v-model="model" :options="options" label="Standard">
  <template v-slot:selected-item="scope">
    <div class="ellipsis">{{scope.opt}}</div>
  </template>
</q-select>

@fly30

There is no drag and drop in Quasar. But with the list it is fairly easy to implement.

There is a feature requested for DND here:
https://github.com/quasarframework/quasar/issues/5890

@Stanley as per @metalsadman suggestion put a tabindex="-1" on the q-btn if you don’t want it to be user focusable by the tab key. But that way you can not access the dialog by keyboard (not good). The natural flow is q-input -> q-btn -> q-input -> q-btn.

Keep in mind you will still end up passing in some variable to valueHelp(helpId) because the help is not the same for every single input (I presume).

@Stanley Sure much better.