-
-
Notifications
You must be signed in to change notification settings - Fork 150
Update partial rendering docs to cover Django 6.0's built-in support #564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
080f946
dcad704
48e6c02
b856a60
9c98e77
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -20,7 +20,6 @@ | |
| INSTALLED_APPS = [ | ||
| "example", | ||
| "django_htmx", | ||
| "template_partials", | ||
| "django.contrib.staticfiles", | ||
| ] | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
| @@ -1,3 +1,2 @@ | ||||
| django | ||||
| django-template-partials | ||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Did you test the example project with a fresh venv without django-template-partials installed? I think we need to drop django-htmx/example/example/settings.py Line 23 in 5ac0abc
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, I just ran manage.py check command. |
||||
| django~=6.0a1 | ||||
| faker | ||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,18 +1,12 @@ | ||
| # This file was autogenerated by uv via the following command: | ||
| # uv pip compile --universal requirements.in -o requirements.txt | ||
| asgiref==3.8.1 | ||
| # uv pip compile requirements.in -o requirements.txt | ||
| asgiref==3.9.2 | ||
| # via django | ||
| django==5.2 | ||
| # via | ||
| # -r requirements.in | ||
| # django-template-partials | ||
| django-template-partials==24.4 | ||
| django==6.0a1 | ||
| # via -r requirements.in | ||
| faker==37.1.0 | ||
| # via -r requirements.in | ||
| sqlparse==0.5.3 | ||
| # via django | ||
| tzdata==2025.2 | ||
| # via | ||
| # django | ||
| # faker | ||
| # via faker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we title this section "Using template partials" and then explain in terms of both
django-template-partialsand Django 6.0's new feature? I want it to still work for users who haven't upgraded to 6.0, especially since it's not even out yet!Perhaps explain the 6.0 way, then the differences in django-template-partials: install the app, use
{% load partial %}as well, ...