On a sidenote, please feel free to visit our discord server. We are great at rubber duck debugging.

Glad it worked for you. One thing you should keep in mind though, is that as Babel moves away from their presets you will have much more granular control over the plugins and modules. I sense we are going to be seeing more issues like yours in the near future.

technically you could also make a so-called global mixin and integrate it as a plugin via the standard quasar.conf.js approach, but I highly recommend VUEX too.

why are you building quasar dev in your docker app? That is really for development only. If you want to reduce your size, just use the dist folder as your WORKDIR

Thanks for posting the solution!

There are literally dozens of ways to interpret your question @jake0124. If this is still part of your original question, then explain what you mean and how you think it should be implemented in a table. Also consider trying things out and telling us what you did and what is or isn’t working.

If this is a separate question not related to QTable, then ask a new question.

I have used JSDoc, and its good. Document your functions like any other JS. Some people might tell you to use typescript, as it is “self-documenting”, but I still think that having a JSDoc type reference is good thing.

@liuzhongshu - just to remind you: Quasar is moving very fast and we are closing in on our stable 1.0 release. 0.14 was a stage in the evolution of Quasar that I also enjoyed, but a lot has happened since then. Until we get to 1.0, EVERYTHING is subject to change and although the framework is pretty stable, you can expect some behaviours to change as we get bug reports and developer feedback.

good catch!!! @Hawkeye64

Or did you forget to add “addressbar-color” to the list of your custom plugins?
http://quasar-framework.org/guide/app-plugins.html