dsl101

Sorry if I've misunderstood, but I've been caught by something similar too. Isn't the code from your first example: setTimeout(() => resolve('Hello ' + this.username + '!'), 1000) just not...

I'm not precious about the name of the option—`strict` came to mind simply because of the analogy with JS `use strict` and the fact it turns on a more strict...

I'm not sure I completely follow what you were trying to illustrate there—did you mean this new setting should be per group? If so, how about `assume-unused: ['data']` to indicate...

Although, I'm now not seeing the point of including `'data'` in the `groups:` setting—and I'm back to why this isn't really just a bug. If I _don't_ want to be...

When you say ”how to handle `return this`“, what are you expecting them to do? I still argue that warning about unused properties according to the existing settings should _not_...

Right, so there would be a default value of `stopReporting` which would match the current behaviour, and by setting that to an empty array, it would not stop reporting for...

Still hopeful for this, even though it's been sitting here for 5 months... Don't know if these would help? * [State & Getters](https://github.com/learningequality/kolibri/blob/9dfab81b98/packages/eslint-plugin-kolibri/lib/rules/vue-no-unused-vuex-properties.js) * [Actions & Mutations](https://github.com/learningequality/kolibri/blob/9dfab81b9849872d983907449cf743e2ca29ebb4/packages/eslint-plugin-kolibri/lib/rules/vue-no-unused-vuex-methods.js) I'm using a...

Thanks Andy—I will ask in the Vue & Quasar communities and, and definitely update here if I find anything. On Fri, 18 Jun 2021 at 23:27, Andy Wermke ***@***.***> wrote:...

Hmm. No luck so far with Vue or Quasar community. I did add some extra logging to see if the exact point of failure sheds any light. It looks like...

Yes. @davestewart's solution didn't work for me (there is nothing which can be 'dragged').