Does it work? What @jraez said should help.

If you really want to use the router, you can do that, too.
The code you showed is in a boot file, right? So I think your this.$router.push('/login') call doesn’t work because this.$router is not defined. Normally, you write that in a Vue component, where this refers to the component - but you are in a boot file.

This is how you can do it:

import axios from "axios"

export default ({ Vue, router }) => { // <-------- This is where the `router` comes from
  Vue.prototype.$axios = axios;

  // ... (your request interceptor here)

  axios.interceptors.response.use(response => {
    return response;
  }, error => {
    if (error.response.status === 401) {
      // ...
      router.push("/login"); // <----  note there is no `this`
    }
    // ...
  });
}

I’m facing the same problem. Company color is a dark brown… :|

My solution is: When I toggle darkmode on/off, I overwrite the colors using setBrand("primary", colorBasedOnDarkmodeSetting) and so on

The function is described here: https://quasar.dev/quasar-utils/color-utils

With “select all icon” you mean the checkbox in the table head that appears when you set selection="multiple" on the QTable, right?
I don’t know how to modify that, but you could use an external button and set the selected property to your whole table data array.

<q-table
    :data="tableData"
    selection="multiple"
    :selected.sync="selected"
    ....
</q-table>

<q-btn label="click me" @click="buttonClicked" />

{
    buttonClicked() {
        this.selected = this.tableData;
    }
}

@MKramer said in How to handle await/promise of async websocket object?:

The port of that server can change, so I created a global variable (which is defined in index.template.html, so it does not get renamed by the build process)

I’m afraid I don’t understand. What do you mean with getting renamed by the build process?

Why is your port number not available upon app start? Does it change over time or something?

Of course, the frontend somehow needs to know what port number the backend is running on and so on. But normally, it doesn’t need to wait for it… it should know value right away, for example using an environment variable.
Why do you need it to be asynchonous?

No need for async await.

In getReminder() replace:

documentClient.scan(params, function(err, data) {
   ...

With:

documentClient.scan(params, (err, data) => {
   ...

The difference is, that in a function using the function keyword, this has a different meaning as in a function using the arrow syntax.
You just discovered why arrow functions are so great – everything inside works as one would expect

If you are interested in more details, here is an article about it: https://medium.com/free-code-camp/learn-es6-the-dope-way-part-ii-arrow-functions-and-the-this-keyword-381ac7a32881#.59q9th108

That should solve your error. You’ll see, everything with the iteration and with how you are using .push() is fine.

@felice The error tells you that you are calling the .push function on something that is undefined. You don’t need a workaround, you need to call the function on the right object (that is, the array)

You were on the right track, it should work the way you did, except with .push instead of re-assigning a value to the property (what I said above).

Seems like there is some other problem with your code, but I can’t do much with what you showed us.

(3): Disabling expansion could be achieved with the following:

<q-tree
   ...
   :expanded.sync="expanded"
>

computed: {
    expanded: {
        get() {
            // return all keys
        },
        set(value) {
            // do noting
        }
    }
}

For the other points: It sounds like you are describing the “strict” tick-strategy with the following adjustment:

• When a node it ticked, tick all parent nodes up to the root node
  You could implement that in a watcher on the ticked property

In the code snippet that you provided, you are not using the .push method. In each iteration you are overwriting tableData with a single object.
Push is used like this:

this.tableData.push({ ... })

Making columns a computed property should do the trick

Yayyyy :DD Hey no problem… it was fun^^
No need to feel stupid there. It wasn’t really obvious because the pagination wasn’t visible.

Here is a tip / how I solve this kind of problem:
Remove everything from the code that is not needed to replicate the problem, feature by feature. And everytime test if you can reproduce the problem.
So when the problem doesn’t occur anymore, you know which part caused it. And if not, then you at least have a simpler and shorter version where you can spot it more easily