mirror of
https://github.com/django-components/django-components.git
synced 2025-08-04 06:18:17 +00:00
feat: Add support for HTML fragments (#845)
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
This commit is contained in:
parent
6681fc0085
commit
4dab940db8
26 changed files with 1225 additions and 246 deletions
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Authoring component libraries
|
||||
weight: 7
|
||||
weight: 8
|
||||
---
|
||||
|
||||
You can publish and share your components for others to use. Here are the steps to do so:
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Registering components
|
||||
weight: 4
|
||||
weight: 5
|
||||
---
|
||||
|
||||
In previous examples you could repeatedly see us using `@register()` to "register"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Lifecycle hooks
|
||||
weight: 3
|
||||
weight: 4
|
||||
---
|
||||
|
||||
_New in version 0.96_
|
||||
|
|
361
docs/concepts/advanced/html_tragments.md
Normal file
361
docs/concepts/advanced/html_tragments.md
Normal file
|
@ -0,0 +1,361 @@
|
|||
---
|
||||
title: HTML fragments
|
||||
weight: 2
|
||||
---
|
||||
|
||||
Django-components provides a seamless integration with HTML fragments ([HTML over the wire](https://hotwired.dev/)),
|
||||
whether you're using HTMX, AlpineJS, or vanilla JavaScript.
|
||||
|
||||
When you define a component that has extra JS or CSS, and you use django-components
|
||||
to render the fragment, django-components will:
|
||||
|
||||
- Automatically load the associated JS and CSS
|
||||
- Ensure that JS is loaded and executed only once even if the fragment is inserted multiple times
|
||||
|
||||
!!! info
|
||||
|
||||
**What are HTML fragments and "HTML over the wire"?**
|
||||
|
||||
It is one of the methods for updating the state in the browser UI upon user interaction.
|
||||
|
||||
How it works is that:
|
||||
|
||||
1. User makes an action - clicks a button or submits a form
|
||||
2. The action causes a request to be made from the client to the server.
|
||||
3. Server processes the request (e.g. form submission), and responds with HTML
|
||||
of some part of the UI (e.g. a new entry in a table).
|
||||
4. A library like HTMX, AlpineJS, or custom function inserts the new HTML into
|
||||
the correct place.
|
||||
|
||||
## Document and fragment types
|
||||
|
||||
Components support two modes of rendering - As a "document" or as a "fragment".
|
||||
|
||||
What's the difference?
|
||||
|
||||
### Document mode
|
||||
|
||||
Document mode assumes that the rendered components will be embedded into the HTML
|
||||
of the initial page load. This means that:
|
||||
|
||||
- The JS and CSS is embedded into the HTML as `<script>` and `<style>` tags
|
||||
(see [JS and CSS output locations](./rendering_js_css.md#js-and-css-output-locations))
|
||||
- Django-components injects a JS script for managing JS and CSS assets
|
||||
|
||||
A component is rendered as a "document" when:
|
||||
|
||||
- It is embedded inside a template as [`{% component %}`](../../reference/template_tags.md#component)
|
||||
- It is rendered with [`Component.render()`](../../../reference/api#django_components.Component.render)
|
||||
or [`Component.render_to_response()`](../../../reference/api#django_components.Component.render_to_response)
|
||||
with the `type` kwarg set to `"document"` (default)
|
||||
|
||||
Example:
|
||||
|
||||
```py
|
||||
MyTable.render(
|
||||
kwargs={...},
|
||||
)
|
||||
|
||||
# or
|
||||
|
||||
MyTable.render(
|
||||
kwargs={...},
|
||||
type="document",
|
||||
)
|
||||
```
|
||||
|
||||
### Fragment mode
|
||||
|
||||
Fragment mode assumes that the main HTML has already been rendered and loaded on the page.
|
||||
The component renders HTML that will be inserted into the page as a fragment, at a LATER time:
|
||||
|
||||
- JS and CSS is not directly embedded to avoid duplicately executing the same JS scripts.
|
||||
So template tags like [`{% component_js_dependencies %}`](../../reference/template_tags.md#component_js_dependencies)
|
||||
inside of fragments are ignored.
|
||||
- Instead, django-components appends the fragment's content with a JSON `<script>` to trigger a call
|
||||
to its asset manager JS script, which will load the JS and CSS smartly.
|
||||
- The asset manager JS script is assumed to be already loaded on the page.
|
||||
|
||||
A component is rendered as "fragment" when:
|
||||
|
||||
- It is rendered with [`Component.render()`](../../../reference/api#django_components.Component.render)
|
||||
or [`Component.render_to_response()`](../../../reference/api#django_components.Component.render_to_response)
|
||||
with the `type` kwarg set to `"fragment"`
|
||||
|
||||
Example:
|
||||
|
||||
```py
|
||||
MyTable.render(
|
||||
kwargs={...},
|
||||
type="fragment",
|
||||
)
|
||||
```
|
||||
|
||||
## Live examples
|
||||
|
||||
For live interactive examples, [start our demo project](../../overview/development.md#developing-against-live-django-app)
|
||||
(`sampleproject`).
|
||||
|
||||
Then navigate to these URLs:
|
||||
|
||||
- `/fragment/base/alpine`
|
||||
- `/fragment/base/htmx`
|
||||
- `/fragment/base/js`
|
||||
|
||||
## Example - HTMX
|
||||
|
||||
### 1. Define document HTML
|
||||
|
||||
```py title="[root]/components/demo.py"
|
||||
from django_components import Component, types
|
||||
|
||||
# HTML into which a fragment will be loaded using HTMX
|
||||
class MyPage(Component):
|
||||
def get(self, request):
|
||||
return self.render_to_response()
|
||||
|
||||
template = """
|
||||
{% load component_tags %}
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
{% component_css_dependencies %}
|
||||
<script src="https://unpkg.com/htmx.org@1.9.12"></script>
|
||||
</head>
|
||||
<body>
|
||||
<div id="target">OLD</div>
|
||||
|
||||
<button
|
||||
hx-get="/mypage/frag"
|
||||
hx-swap="outerHTML"
|
||||
hx-target="#target"
|
||||
>
|
||||
Click me!
|
||||
</button>
|
||||
|
||||
{% component_js_dependencies %}
|
||||
</body>
|
||||
</html>
|
||||
"""
|
||||
```
|
||||
|
||||
### 2. Define fragment HTML
|
||||
|
||||
```py title="[root]/components/demo.py"
|
||||
class Frag(Component):
|
||||
def get(self, request):
|
||||
return self.render_to_response(
|
||||
# IMPORTANT: Don't forget `type="fragment"`
|
||||
type="fragment",
|
||||
)
|
||||
|
||||
template = """
|
||||
<div class="frag">
|
||||
123
|
||||
<span id="frag-text"></span>
|
||||
</div>
|
||||
"""
|
||||
|
||||
js = """
|
||||
document.querySelector('#frag-text').textContent = 'xxx';
|
||||
"""
|
||||
|
||||
css = """
|
||||
.frag {
|
||||
background: blue;
|
||||
}
|
||||
"""
|
||||
```
|
||||
|
||||
### 3. Create view and URLs
|
||||
|
||||
```py title="[app]/urls.py"
|
||||
from django.urls import path
|
||||
|
||||
from components.demo import MyPage, Frag
|
||||
|
||||
urlpatterns = [
|
||||
path("mypage/", MyPage.as_view())
|
||||
path("mypage/frag", Frag.as_view()),
|
||||
]
|
||||
```
|
||||
|
||||
## Example - AlpineJS
|
||||
|
||||
### 1. Define document HTML
|
||||
|
||||
```py title="[root]/components/demo.py"
|
||||
from django_components import Component, types
|
||||
|
||||
# HTML into which a fragment will be loaded using AlpineJS
|
||||
class MyPage(Component):
|
||||
def get(self, request):
|
||||
return self.render_to_response()
|
||||
|
||||
template = """
|
||||
{% load component_tags %}
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
{% component_css_dependencies %}
|
||||
<script defer src="https://unpkg.com/alpinejs"></script>
|
||||
</head>
|
||||
<body x-data="{
|
||||
htmlVar: 'OLD',
|
||||
loadFragment: function () {
|
||||
const url = '/mypage/frag';
|
||||
fetch(url)
|
||||
.then(response => response.text())
|
||||
.then(html => {
|
||||
this.htmlVar = html;
|
||||
});
|
||||
}
|
||||
}">
|
||||
<div id="target" x-html="htmlVar">OLD</div>
|
||||
|
||||
<button @click="loadFragment">
|
||||
Click me!
|
||||
</button>
|
||||
|
||||
{% component_js_dependencies %}
|
||||
</body>
|
||||
</html>
|
||||
"""
|
||||
```
|
||||
|
||||
### 2. Define fragment HTML
|
||||
|
||||
```py title="[root]/components/demo.py"
|
||||
class Frag(Component):
|
||||
def get(self, request):
|
||||
# IMPORTANT: Don't forget `type="fragment"`
|
||||
return self.render_to_response(
|
||||
type="fragment",
|
||||
)
|
||||
|
||||
# NOTE: We wrap the actual fragment in a template tag with x-if="false" to prevent it
|
||||
# from being rendered until we have registered the component with AlpineJS.
|
||||
template = """
|
||||
<template x-if="false" data-name="frag">
|
||||
<div class="frag">
|
||||
123
|
||||
<span x-data="frag" x-text="fragVal">
|
||||
</span>
|
||||
</div>
|
||||
</template>
|
||||
"""
|
||||
|
||||
js = """
|
||||
Alpine.data('frag', () => ({
|
||||
fragVal: 'xxx',
|
||||
}));
|
||||
|
||||
// Now that the component has been defined in AlpineJS, we can "activate"
|
||||
// all instances where we use the `x-data="frag"` directive.
|
||||
document.querySelectorAll('[data-name="frag"]').forEach((el) => {
|
||||
el.setAttribute('x-if', 'true');
|
||||
});
|
||||
"""
|
||||
|
||||
css = """
|
||||
.frag {
|
||||
background: blue;
|
||||
}
|
||||
"""
|
||||
```
|
||||
|
||||
### 3. Create view and URLs
|
||||
|
||||
```py title="[app]/urls.py"
|
||||
from django.urls import path
|
||||
|
||||
from components.demo import MyPage, Frag
|
||||
|
||||
urlpatterns = [
|
||||
path("mypage/", MyPage.as_view())
|
||||
path("mypage/frag", Frag.as_view()),
|
||||
]
|
||||
```
|
||||
|
||||
## Example - Vanilla JS
|
||||
|
||||
### 1. Define document HTML
|
||||
|
||||
```py title="[root]/components/demo.py"
|
||||
from django_components import Component, types
|
||||
|
||||
# HTML into which a fragment will be loaded using JS
|
||||
class MyPage(Component):
|
||||
def get(self, request):
|
||||
return self.render_to_response()
|
||||
|
||||
template = """
|
||||
{% load component_tags %}
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
{% component_css_dependencies %}
|
||||
</head>
|
||||
<body>
|
||||
<div id="target">OLD</div>
|
||||
|
||||
<button>
|
||||
Click me!
|
||||
</button>
|
||||
<script>
|
||||
const url = `/mypage/frag`;
|
||||
document.querySelector('#loader').addEventListener('click', function () {
|
||||
fetch(url)
|
||||
.then(response => response.text())
|
||||
.then(html => {
|
||||
document.querySelector('#target').outerHTML = html;
|
||||
});
|
||||
});
|
||||
</script>
|
||||
|
||||
{% component_js_dependencies %}
|
||||
</body>
|
||||
</html>
|
||||
"""
|
||||
```
|
||||
|
||||
### 2. Define fragment HTML
|
||||
|
||||
```py title="[root]/components/demo.py"
|
||||
class Frag(Component):
|
||||
def get(self, request):
|
||||
return self.render_to_response(
|
||||
# IMPORTANT: Don't forget `type="fragment"`
|
||||
type="fragment",
|
||||
)
|
||||
|
||||
template = """
|
||||
<div class="frag">
|
||||
123
|
||||
<span id="frag-text"></span>
|
||||
</div>
|
||||
"""
|
||||
|
||||
js = """
|
||||
document.querySelector('#frag-text').textContent = 'xxx';
|
||||
"""
|
||||
|
||||
css = """
|
||||
.frag {
|
||||
background: blue;
|
||||
}
|
||||
"""
|
||||
```
|
||||
|
||||
### 3. Create view and URLs
|
||||
|
||||
```py title="[app]/urls.py"
|
||||
from django.urls import path
|
||||
|
||||
from components.demo import MyPage, Frag
|
||||
|
||||
urlpatterns = [
|
||||
path("mypage/", MyPage.as_view())
|
||||
path("mypage/frag", Frag.as_view()),
|
||||
]
|
||||
```
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Prop drilling and provide / inject
|
||||
weight: 2
|
||||
weight: 3
|
||||
---
|
||||
|
||||
_New in version 0.80_:
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Tag formatters
|
||||
weight: 6
|
||||
weight: 7
|
||||
---
|
||||
|
||||
## Customizing component tags with TagFormatter
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Typing and validation
|
||||
weight: 5
|
||||
weight: 6
|
||||
---
|
||||
|
||||
## Adding type hints with Generics
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue