@Hawkeye64 : Great job, works fine again.

.eslintrc.js

// allow console.log during development only
‘no-console’: process.env.NODE_ENV === ‘production’ ? ‘error’ : ‘off’,

Running quasar build will result in something like this

ERROR in ./src/components/user/UserTabRoles.vue
Module Error (from ./node_modules/eslint-loader/index.js):

C:\Users\xxx\code\quasar\infosys\src\components\user\UserTabRoles.vue
210:25 error Unexpected console statement no-console
236:25 error Unexpected console statement no-console

2 problems (2 errors, 0 warnings)

After upgrading QCalendar colors from color schema (positive, negative,…) displayed differently.
Pkg quasar v1.4.3
Pkg @quasar/app v1.2.4
QCalendar v.1.0.9

Before:

After:

I found a solution:

Add ref and @finish to QUploader:

<q-uploader
    :factory="getUploadFactory"
    @uploaded="uploaded"
    @finish="finished"
    ref="uploader"
    label="Add new picture"
    accept=".jpg, .png, .gif, image/*"
    class="slide-image"
    square
    dark
/>

Reset QUploader:

finished () {
    this.$refs.uploader.reset()
}

Need this feature as well. There is the @finish() event and methods called reset() / removeUploadedFiles(). How can I call this methods from @finish()?

I want to use passport.js with passport-ldapauth to authenticate users in my SPA. Has anyone done this before and can post best practices with code examples?

Or change this line to

'no-console': process.env.NODE_ENV === 'production' ? 'off' : 'off',

If you inspect data (table data) after “linking” with QTable you’ll find some aditional things like getters, setters, etc. inside. To protect these additional things QTable seems to use Object.preventExtensions().

Here ist the original code:

<template>
  <div>
    <q-table
        :columns="columns"
        :data="books"
        row-key="id"
        selection="single"
        binary-state-sort
        dense
    />
  </div>
</template>

<script>
import gql from 'graphql-tag'

const BOOKS = gql`
  query {
    books {
      nodeId
      id
      title
      author
    }
  }
`

const BOOKS_SUBSCRIPTION = gql`
  subscription {
    listen (topic: "books") {
      relatedNode {
        ... on Book {
          nodeId
          id
          title
          author
        }
      }
    }
  }
`

export default {
  name: 'BooksSubscribeToMore',
  apollo: {
    books: {
      query: BOOKS,
      subscribeToMore: {
        document: BOOKS_SUBSCRIPTION,
        updateQuery: (previousResult, { subscriptionData }) => {
          if (previousResult.books.find(book => book.id === subscriptionData.data.listen.relatedNode.id)) {
            return previousResult
          }

          return {
            books: [...previousResult.books, subscriptionData.data.listen.relatedNode]
          }
        }
      }
    }
  },
  data () {
    return {
      columns: [
        { name: 'id', label: 'ID', field: 'id', sortable: true, required: true },
        { title: 'title', label: 'Title', field: 'title', align: 'left', sortable: true },
        { name: 'author', label: 'Author', field: 'author', align: 'left', sortable: true }
      ],
      books: []
    }
  }
}
</script>

The code with the watcher works fine but it doesn’t feel “smooth”.

This was my first approach resulting in the errors above.
After this I take a look at the structure of data (table data) and books.