No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. niklaszantner
    N
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 3
    • Best 1
    • Groups 0

    niklaszantner

    @niklaszantner

    1
    Reputation
    274
    Profile views
    3
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Website niklaszantner.de

    niklaszantner Follow

    Best posts made by niklaszantner

    • RE: Possible bug in current beta with q-input

      @n.taddei thank you very much!

      posted in Framework
      N
      niklaszantner

    Latest posts made by niklaszantner

    • RE: ~~Do not upgrade to Vue 2.4.x (yet)~~ Edit: Safe to upgrade

      I can confirm @LaurentPayot, even with https://github.com/vuejs/vue/issues/6093 fixed in vue 2.4.2 the described error still occurs.

      posted in Announcements
      N
      niklaszantner
    • RE: Possible bug in current beta with q-input

      @n.taddei thank you very much!

      posted in Framework
      N
      niklaszantner
    • Possible bug in current beta with q-input

      I did a rm -rdf node-modules && npm i && quasar dev today and found an interesting error.

      As soon as a q-input is rendered, following error occurs:

      [Vue warn]: Injection "__field" not found
      
      found in
      
      ---> <QInputFrame>
             <QInput>
               <QLayout>
                 <Index> at [DEV_DIR]/beta/src/components/Hello.vue
                   <App> at [DEV_DIR]/beta/src/App.vue
                     <Root>
      

      You can repdocue this by running quasar init default#beta beta-dir && cd beta-dir && npm i and adding a <q-input v-model="text" /> to src/components/Hello.vue (and of course import the component and adding it to the components object in the vue instance). Running quasar dev then yields the already shown error.

      Some questions by me:

      1. Can someone else reproduce that (yesterday everything worked fine, that’s why I am unsure about if this is an actual bug)?
      2. Am I missing something obvious (I started with quasar two weeks ago and moved to v0.14 yesterday)?
      3. If this is a bug, do I report it in the default https://github.com/quasarframework/quasar repo or is there something to consider / special when reporting beta bugs?

      Thanks for your help and nice to be part of the community 🙂

      posted in Framework
      N
      niklaszantner