You have to set definitions property:

<!-- HTML -->
<q-editor v-model="post.body" :definitions="definitions"/>

// script

data() {
    return {
        definitions: {
                insert_img: {
                    tip: 'Insertar Imagen',
                    icon: 'photo',
                    handler: this.insertImg // handler will call insertImg() method
                }
            }
        }
    },
    methods: {
        insertImg() { // insertImg method
            const post = this.post
            // create an input file element to open file dialog
            const input = document.createElement('input')
            input.type = 'file'
            input.accept = '.png, .jpg' // file extensions allowed
            let file
            input.onchange = _ => {
                const files = Array.from(input.files)
                file = files[0]
  
               // lets load the file as dataUrl
                const reader = new FileReader()
                let dataUrl = ''
                reader.onloadend = function() {
                    dataUrl = reader.result
                   
                    // append result to the body of your post
                    post.body += '<div><img src="' + dataUrl + '" /></div>' 
                }
                reader.readAsDataURL(file)
            }
            input.click()
        }
}

You can declare your <q-table> in a “more explicit” way by specifying the slot templates and omitting the select component of header or just set the hide-header property in case it isn’t indispensable.

<q-table
        title="Example"
        :data="data"
        :columns="columns"
        row-key="name"
        selection="multiple"
        :selected.sync="selected"
      >
  
        <template v-slot:header>
           <!-- your custom header here -->
        </template>
  
</q-table>

The best way I found is setting height with on component created with JavaScript. I’t worked for me.

<template>
    <q-carousel class="text-white" :height="windowHeight" arrows color="white" infinite autoplay>
        <q-carousel-slide :img-src="slide.imagen" v-for="(slide, index) in slides" :key="index">
            <div class="carousel-caption">
                <div class="carousel-title">
                    {{ slide.titulo }}
                </div>
                <div class="carousel-subtitle" v-html="slide.texto" />
            </div>
        </q-carousel-slide>
    </q-carousel>
</template>

<script>
export default {
    created() {
        this.windowHeight = window.innerHeight + 'px'
    }
}
</script>

@justdior let’s do it! Tell me more about it. What kind of error have you got?

Thank! It was a typo error

Documentations says:
"Icon sets are available through @quasar/extras package. You don’t need to import it in your app, just configure /quasar.conf.js "

But it isn’t enough. Node console says that an installation is needed.

Im trying to use QSelect component as autocomplete but I need that if there are no results, the v-model prop could be setted manually using what the user had writen.

@metalsadman thanks a lot. It works ok!

Has anybody idea how can I integrate Quasar v1 into a Laravel app? Up to this point I was working with the frontend code separated from the backend api, but I would like to bring all the frontend app into the Laravel resources folder and manage all the code as a single application, taking advantage of Laravel Mix. I found some sample repositories but all of them are about Quasar 0.17.

Try passing the number value as a directive adding a colon (:) before the component property like this

<q-autocomplete :min-characters="3" />

Could you please paste the entire component code including that between script tags?

date type is not a allowed feature of q-input component. You may use QDate component instead or QDatetime for 0.17.x versions.

Seems like you are talking about QAjaxBar component.
Check at your quasar.conf.js file and set the color property into the config collection:

config: {
      loadingBar: { 
           color: 'indigo-7' // --> from Quasar Color Palette 
      }
}

Sorry, what exactly do you mean with “route loading”?