I am upgrading my system to Quasar 1.0 in a GIT branch, and I had followed all upgrade guide steps, including upgrading Quasar-CLI (globally).
It works, but still, need a good amount of work to complete the upgrading.
But I also need to make system changes on the old develop branch, and the quasar dev stop working for the 0.17 code.
What do I have to do to run the 0.17 code with the new quasar-cli?
It is all working now, I believe that you updated the component but the not the documentation at the same time and this leads to some errors, but It is everything just fine as usual now!
Congratulations rstoenescu for your awesome work on Quasar framework! I’m now on my second project using Quasar and I became more and more fan of it!
Any way to force a fixed column width?
just set the style: 'width: 40px' do not work.
Setting the headerStyle prop also does not work.
min-width and max-width also do not work…
Is there any way to set a fixed column width?
Is there a way to create a date time input that allows user to type the date with keyboard and not only pick it with a mouse?
I believe that this is a quite common use case when you have a CRUD form with lots of input fields and if you are using keyboard only to fill the form and navigate between fields, it’s time-consuming to get a date from a calendar…
I know I can use a simple text field and validation, but I would like that DateTime widget to have an option to allow user type date (and show it in the calendar) or pick one with the mouse.
I have been trying to set fixed columns width with style and headerStyle and CSS min-width, width, and max-width and looks like these values are sometimes overwritten to make sure table fits on space/screen…
Still don’t know how to do it 
A working example would be just great!
Any way to force a fixed column width?
just set the style: 'width: 40px' do not work.
Setting the headerStyle prop also does not work.
min-width and max-width also do not work…
Is there any way to set a fixed column width?
Great Job @s-molinari!
Just one question. What are your thoughts about using TypeScript + Quasar + Apollo?
Do you have a good typing support from Apollo?
Regards
Marcelo
@metalsadman I am not proposing any breaking changes.
Add some preconfigured wrappers around QSelect to make easy to use would be good to framework environment (of course you can do it on a project basis, but why always create a component with a basic filter just like we had on 0.17?
If these components are on top of QSelect, no breaking changes. QSelect is almost a framework by it own now 
Also, I believe is possible to create a new component (no breaking changes) just for basic use cases.
I think the idea is to give more alternatives and expand the framework, not change the great job that exists now.
I also think that it gets too overcomplicated. 69 props, 15 slots, 13 methods… this single component has more options than almost all other form components together!
Not only too many props, but worst, a complex interaction between then… (like fill-input, use-input-hide-selected and multiple creates dozens of different behaviours)
It is amazing powerful now but drives me with overlapping functions between all behavior props.
Maybe one basic for small lists (where performance is not an issue, as QSelect now is optimized for performance (yeah ), but harder for basic use cases like a single select with filter…
Another good way is to create a QSimpleSelect more simil;ar to what we had in 0.17.xx
Anyway, Quasar still one of the best pieces of software I had worked it. 
As I understand from docs, factory prop is used to dynamically pass parameters to uploader, not to process the upload in this function (because Quasar will do a request using the values passed by the factory function)
This is not the same as using the global axios instance (plugin configured on boot).
If I manually handle the uploader inside the factory, how Quasar will know about it?
Are the docs incomplete or I just didn’t understand it?
I am having a similar issue.
I have a global axios configured to deal with authentication and QUploader uses direct XHRRequests.
Even if a do an ugly way to set all security headers in factory function, it gives weird errors os server side.
If I use the global axios for the same request it works… but then I can not use the (nice) QUploader UI.
There is any way to tell QUploader to use the global axios instance?
Solved.
I had to migrate from npm to yarn to install Quasar 1.0 (didn’t work with npm for me)
After that, I had to run yarn in the project directory before run Quasar 0.17
In my project, I was only able to instal Quasar CLI 1.0 using yarn (I was using npm, but it doesn’t work)
My Quasar 0.17 project just run after I updated the packages using yarn, even with no changes in the project, maybe something related to the newly installed packages…
After updating the packages of older projects, I am able to run Quasar CLI 0.17 and 1.0
I am upgrading my system to Quasar 1.0 in a GIT branch, and I had followed all upgrade guide steps, including upgrading Quasar-CLI (globally).
It works, but still, need a good amount of work to complete the upgrading.
But I also need to make system changes on the old develop branch, and the quasar dev stop working for the 0.17 code.
What do I have to do to run the 0.17 code with the new quasar-cli?