pellet
django-typescript-routes
pellet | django-typescript-routes | |
---|---|---|
2 | 1 | |
75 | 18 | |
- | - | |
2.7 | 4.7 | |
6 months ago | 9 months ago | |
Python | Python | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pellet
-
Django 5.0 Is Released
Simple middleware can warn you about lazy loading/N+1 queries. Most of the time people just forget it happens.
Try using: https://github.com/har777/pellet
-
Ban 1+N in Django
Self plug: Checkout https://github.com/har777/pellet to easily find and fix django N+1 issues.
I usually add it to existing integration tests so that they raise exceptions on N+1. If test coverage is low then I would suggest sending the N+1 metrics to something like datadog. That way your users using the product will reveal all the N+1 issues on your monitoring solution.
django-typescript-routes
-
Django 5.0 Is Released
I'll preface all of this with a couple esoteric design goals that I had in mind:
1. I actually _want_ an SPA. You might not need an SPA, if you don't need one then Vue/React/etc are overkill, etc.
2. I want to power as much of the SPA as I can using the same REST API as my core product, both for dogfooding reasons and for consolidation. Many people might argue that this is a bad idea.
---
With that in mind, some specific packages that I highly recommend:
1. Django-vite (https://github.com/MrBin99/django-vite). This makes it very easy to serve an SPA from the actual django response/request model
2. Some sort of way to get type information (if you're using TypeScript) into the frontend. I use a frankensteined system of the OpenAPI spec that django-ninja generates + openapi-typescript (https://github.com/drwpow/openapi-typescript). This means when I add, say, a new field to a response in Django, I immediately get typechecking for it in Vue — which has been _tremendously_ useful.
3. Django-typescript-routes (a package I extracted and open-sourced!: https://github.com/buttondown-email/django-typescript-routes) which gives your front-end routing information based on the Django router.
What are some alternatives?
django-orm-plus
openapi-typescript-codegen - NodeJS library that generates Typescript or Javascript clients based on the OpenAPI specification
nplusone - Auto-detecting the n+1 queries problem in Python
django-auto-prefetching - Automatic prefetching for Django
django-zen-queries - Explicit control over database query execution in Django applications
django-seal - Django application providing queryset sealing capability.
bullet - help to kill N+1 queries and unused eager loading
openapi-typescript - Generate TypeScript types from OpenAPI 3 specs
django-cacheops - A slick ORM cache with automatic granular event-driven invalidation.