I love it…a programmer saying “you can ‘simply’”.
Yes I can do that. As I explained it would be a pain to do that. It means I must rebuild that object for each specific page over and over from scratch as it’s used many places through out the site. In a super bad case I’d have to do that twice on the same page. If I could hide/remove in the dom instead then it’s just way way easier. disable already exits why not hide. Guess it’s on me to modify the component to my liking, but could be in the mix for future releases.
Thanks, guys. The concern my team has is that we have several components that are currently written in bootstrap that we want to bring into the Quasar app. Rewrites are always possible, of course, but we are trying to avoid that right now due to deadlines.
yes you are right. There are more changes than just in the index.html.
I made some more experiments and found an interesting fact: If I am loading a release build (which does not work properly) and than catch the content with:
I then can load that html code properly as index.html. So blink is self correcting all the .js calls, but the final “refresh” does not work. But I couldn’t find the call to the main page or an attempt to refresh that content, yet.
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