I’ve been using them in conjunction for most projects.
As mentioned above REST is the way to go.
You’d use django-rest-framework as your backend API and Quasar as your frontend and deploy both separately.
If you’re unfamiliar with drf it’s worth getting to grips with Django first before jumping into RESTful APIs. Once your comfortable with Django you’d used drf in order to make API calls from your front end .
For example you can chose to use axios in your quasar app, which in turn would be used to make request to your REST API.
For example axios.get('http://localhost:8000/api/...)
This makes a GET request to your local Django server which returns some information.
Some additional notes:
Django rest is really powerful. Much like Django there are generic views and model “views” (serializers) that make things really easy. There are some great extensions for social auth like django-rest-auth
Pick the best tool for the job. NPM for global packages, Yarn for local packages. For now, this is the best set up. We do wish they both worked as expected for global and local packages, but the fact is right now, we help so many people with issues and a lot of times it’s migrating them to yarn for local packages and then things automagically work as expected.
I think the rules :rules="['date']" will cause this to be added. This is where the error messages go. Which are position: fixed because of the animation I think.
Might be interesting to read
search for bottom-slots
I was also looking into this forum tech. First impression was… oh, another simplified forum… but after registration and the first usage I have to admit - it is a really good choice! Sadly I do have other topics on my list first - but on longterm some kind of integration would be awesome. Even if I assume, theres not much relation and it is more a topic for the specific app someone wants and the integration will be more or less “quasar framework agnostic”. But still, this is just guessing at the current state of information - at least from my side.
If I may add: your fast response is VERY helpful, as it helps your users not wasting time in such topics. And I don’t take this for granted. With your replies to my - misplaced - reports you saved me some hours today. And I’m sure others feel alike.
@jasonl disabled is native, while disable is a quasar prop use to put a quasar component in a disabled state. v.017 https://quasar-framework.org/components/button.html#Vue-Properties and v1 https://v1.quasar-framework.org/vue-components/button#QBtn-API