After upgrading a large project from 0.17 to 1.9 quasar, Vue CLI plugin + typescript, I’m seeing a very strange thing - some of my custom components, for instance - <table-layout>, is used in two tables. One table is displayed just fine with no errors. The other, not displayed at all, and I am getting an error “unrecognized custom component <table-layout>. Are you sure you registered the component correctly… etc etc”
I’m have no idea why this is happening. Has anyone come across something similar?

I’ve recently upgraded from 0.17 to 1.9, using Vue CLI. I use Vue + Typescript.
Weirdly, some of my custom components are not recognized now. They are all registered in main.ts, I can’t figure out why some work and some don’t.
Any ideas?

When using q-autocomplete within a q-chips-input, you get unepected behaviour.
When clicking on the input line for the first time, you get the following stream of events -
focus (QChipsInput)-> click (QInputFrame) -> input (QPopover) -> show (QAutocomplete) -> show (QPopover)
Then, once you select one of the autocomplete options -
add (QChipsInput) -> selected (QAutocomplete) -> hide (QAutocomplete) -> hide (QPopover)
Now, the QChipsInput is still focused, a blinking cursor is visible on the input line. I want to get the options list to appear again, but when I click the input line, all I get is a click event click (QInputFrame), and nothing happens. In order to get the options list to appear again, I have to trigger a blur event first.
Is there a way to fix this?
Thanks!

This is actually a two-part request -
First, can you make it possible to set markers on sliders with step 0 for value, and a different step size for markers?
Secondly, can the markers have a label displaying the values they represent?

And, bonus request, it would be really great if hovering over the slider could trigger a tooltip label with the hovered area’s value.

Thanks!