I made a repository to try to figure out the best way to require prefech_related/select_related when fetching a model's related objects. I also want to figure out a good pattern for avoiding duplicated prefetch_related/select_related for multiple places in a codebase that need the related objects eager loaded in the same way.
It's a lot faster than the Python package I was using: https://github.com/mar10/wsgidav
Wsgidav is great though. It's super customizable and the documentation is great too.
It would be nice to know a better way to cache the ModelChoiceField’s queryset when it’s used in a form that runs “is_valid()” in a loop (like Formsets do). The best way I know how at the moment is by not using a ModelChoiceField at all. The solution requires using a ChoiceField, running the query for choices outside of the loop, then passing the choices into the form to override the ChoiceField choices.
Here’s an example:
I made a small example with it to show how it works with ModelChoiceFields: https://github.com/pawl/django_api_forms_modelchoicefield_example
Seems like a more lightweight version of DRF's serializers (but only for deserializing and validating) and with a similar API to Django's built-in forms.
Well, the author responded and it turns out it's definitely used (by vue magic): https://cli.vuejs.org/guide/html-and-static-assets.html
Oops, definitely should have googled "vue public/index.html" before making that pull request. I made another pull request to add a link about it to the django-vue-template docs: https://github.com/gtalarico/django-vue-template/pull/54
"Server side templating can work really well when the website is static. The problem is that as you add more and more dynamic elements, you either have to go to the server and re-render everything with every change (which can be slow), or you can make the changes on the client side with something like jQuery. But the latter option presents a challenge because you'll eventually find yourself duplicating functionality.
For example, imagine a to-do list website that you render on the server with a templating language. It fetches the user's to-do items from the database and then renders the list. Now let's say you want to let a user add a new item without re-rendering the entire page. You could use AJAX to tell the server to add the new item, but now you need to update your UI list accordingly. You could use jQuery to construct a new DOM element and append it, but now that list element exists in two different places: in your jQuery code and in your template on the server. If your website becomes very dynamic, this situation can get really unwieldy from a programming perspective.
Both Angular (from what I've read) and React (from personal experience) are highly suitable for creating single page apps, with the goal of creating a dynamic, fast, and maintainable website. There are other benefits, as well as downsides, to using Angular and React, but I hope this clears it up a little bit. Both of them make server side templating unnecessary by moving UI logic/rendering from your server to the client's browser. So a user who visits your React powered to-list website would get the React code as a JS bundle, it would make an AJAX call to your server to get just the data, and then it would render the UI based on the data." -/u/VertiGuo (https://www.reddit.com/r/node/comments/6t22cr/back_end_templating_engine_or_front_end_framework/dlhukkf/)
"for example putting together a form, and handle the response is easy, but if you have to manage a list of items where the user can add/remove items, or change the schema of items based on a selector (e.g. phone type or address) you have to split the logic, and put some on client side scripts, which can become very messy. not to mention live updates like chat, comments etc.
creating a separate backend and frontend solves this problem, as the backend's responsibility will be only manipulating the database, retrieve data and run jobs providing an api and the frontend's will be the only the representation of these data, providing the user interface. this separation lets developers use different technologies and languages on the two side, as well as specializing in these. for the beginning this approach is a bit hard to learn, but it will worth it on the long run." -/u/bdvx (https://www.reddit.com/r/webdev/comments/cbrdte/html_templating_vs_spa/etifiar/)
Otherwise, if you're starting a fresh project with a separate front-end, this is a good template: https://github.com/gtalarico/django-vue-template/