diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_lg_first.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_lg_first.json
index 290df02e..1f008959 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_lg_first.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_lg_first.json	
@@ -1 +1 @@
-[[1566, [52121600.0, 54030336.0]], [1569, [52006912.0, 54030336.0]]]
\ No newline at end of file
+[[1662, [52920320.0, 54566912.0]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_lg_subsequent.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_lg_subsequent.json
index 424a9b9a..c9911668 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_lg_subsequent.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_lg_subsequent.json	
@@ -1 +1 @@
-[[1566, [52129792.0, 54525952.0]], [1569, [52019200.0, 54542336.0]]]
\ No newline at end of file
+[[1662, [53800960.0, 54734848.0]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_sm_first.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_sm_first.json
index 7acecff5..f5aeaa44 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_sm_first.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_sm_first.json	
@@ -1 +1 @@
-[[1566, [43671552.0, 43925504.0]], [1569, [43667456.0, 43921408.0]]]
\ No newline at end of file
+[[1662, [44191744.0, 44191744.0]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_sm_subsequent.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_sm_subsequent.json
index c3f72a92..8ed44e03 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_sm_subsequent.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.peakmem_render_sm_subsequent.json	
@@ -1 +1 @@
-[[1566, [43675648.0, 43929600.0]], [1569, [43671552.0, 43925504.0]]]
\ No newline at end of file
+[[1662, [44195840.0, 44187648.0]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_lg_first.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_lg_first.json
index 425e9982..6f59785c 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_lg_first.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_lg_first.json	
@@ -1 +1 @@
-[[1566, [0.06844023999997262, 0.25948228500001846]], [1569, [0.0695505670000216, 0.2585547080000197]]]
\ No newline at end of file
+[[1662, [0.06960565700001098, 0.25608221199996706]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_lg_subsequent.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_lg_subsequent.json
index 8b663f8a..a4389e86 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_lg_subsequent.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_lg_subsequent.json	
@@ -1 +1 @@
-[[1566, [0.03282115399997565, 0.1461098879999838]], [1569, [0.03280580699998836, 0.14556000400000357]]]
\ No newline at end of file
+[[1662, [0.03327357099999517, 0.1421111020000012]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_sm_first.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_sm_first.json
index 6e9d3388..5a45c35a 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_sm_first.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_sm_first.json	
@@ -1 +1 @@
-[[1566, [0.0035044859999970868, 0.004806205000022601]], [1569, [0.003512746000012612, 0.004752005000000281]]]
\ No newline at end of file
+[[1662, [0.0035443229999998493, 0.00467639600003622]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_sm_subsequent.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_sm_subsequent.json
index 82e38bbd..ba6f3dad 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_sm_subsequent.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_render_sm_subsequent.json	
@@ -1 +1 @@
-[[1566, [9.84330000051159e-05, 0.000542360999986613]], [1569, [9.899399998403169e-05, 0.0005454930000041713]]]
\ No newline at end of file
+[[1662, [0.00010400499999718704, 0.0005328339999977061]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_startup_lg.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_startup_lg.json
index 0594ba09..b35fcb73 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_startup_lg.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Components vs Django.timeraw_startup_lg.json	
@@ -1 +1 @@
-[[1566, [0.21055065100000547, 0.20605139500003133]], [1569, [0.20886826499997824, 0.20461195600000792]]]
\ No newline at end of file
+[[1662, [0.21775109000003567, 0.21398552899995593]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Other.timeraw_import_time.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Other.timeraw_import_time.json
index 6745b517..24d2f960 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Other.timeraw_import_time.json
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/Other.timeraw_import_time.json
@@ -1 +1 @@
-[[1566, 0.19086866300000338], [1569, 0.1891247499999622]]
\ No newline at end of file
+[[1662, 0.19832900800003017]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_lg_first.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_lg_first.json
index 8e5b192c..64ea38e1 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_lg_first.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_lg_first.json	
@@ -1 +1 @@
-[[1566, [54018048.0, 53542912.0]], [1569, [53940224.0, 53530624.0]]]
\ No newline at end of file
+[[1662, [54439936.0, 53968896.0]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_lg_subsequent.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_lg_subsequent.json
index 8b95c827..386515dd 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_lg_subsequent.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_lg_subsequent.json	
@@ -1 +1 @@
-[[1566, [54571008.0, 54530048.0]], [1569, [54566912.0, 54525952.0]]]
\ No newline at end of file
+[[1662, [54968320.0, 54792192.0]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_sm_first.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_sm_first.json
index 659eef5a..30df792a 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_sm_first.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_sm_first.json	
@@ -1 +1 @@
-[[1566, [43925504.0, 43925504.0]], [1569, [43921408.0, 43687936.0]]]
\ No newline at end of file
+[[1662, [44187648.0, 44183552.0]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_sm_subsequent.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_sm_subsequent.json
index b86ec5c4..a1e72486 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_sm_subsequent.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.peakmem_render_sm_subsequent.json	
@@ -1 +1 @@
-[[1566, [43929600.0, 43929600.0]], [1569, [43925504.0, 43925504.0]]]
\ No newline at end of file
+[[1662, [44187648.0, 44187648.0]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_lg_first.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_lg_first.json
index 2739c11b..305b8833 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_lg_first.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_lg_first.json	
@@ -1 +1 @@
-[[1566, [0.2582084590000022, 0.2630794039999955]], [1569, [0.2609166309999864, 0.26201485799998636]]]
\ No newline at end of file
+[[1662, [0.2574955810000006, 0.2591010970000127]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_lg_subsequent.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_lg_subsequent.json
index 141d447a..769a66bc 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_lg_subsequent.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_lg_subsequent.json	
@@ -1 +1 @@
-[[1566, [0.14612163999998984, 0.15001642000004267]], [1569, [0.14627813999999262, 0.15037803699999586]]]
\ No newline at end of file
+[[1662, [0.14273938200000202, 0.1464969190000147]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_sm_first.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_sm_first.json
index d8182ee1..2c73d728 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_sm_first.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_sm_first.json	
@@ -1 +1 @@
-[[1566, [0.004762013999993542, 0.004786298999988503]], [1569, [0.004790214000024662, 0.004819428000018888]]]
\ No newline at end of file
+[[1662, [0.004720848000005162, 0.004705489000002672]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_sm_subsequent.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_sm_subsequent.json
index 442fef79..00c84d15 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_sm_subsequent.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_render_sm_subsequent.json	
@@ -1 +1 @@
-[[1566, [0.0005448759999922004, 0.0005334049999987656]], [1569, [0.0005436999999801628, 0.0005416959999706705]]]
\ No newline at end of file
+[[1662, [0.0005377129999999397, 0.0005395769999836375]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_startup_lg.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_startup_lg.json
index f419689a..eca85d41 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_startup_lg.json	
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/isolated vs django modes.timeraw_startup_lg.json	
@@ -1 +1 @@
-[[1566, [0.2058522649999759, 0.2053180329999691]], [1569, [0.20448447999996233, 0.2037191150000126]]]
\ No newline at end of file
+[[1662, [0.21402431699999624, 0.21364062999998623]]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/summary.json b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/summary.json
index e10ed11d..e1e4deab 100644
--- a/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/summary.json
+++ b/dev/benchmarks/graphs/branch-master/django-5.1/djc-core-html-parser/machine-ci-linux/python-3.13/summary.json
@@ -1 +1 @@
-[{"name": "Components vs Django.peakmem_render_lg_first", "idx": 0, "pretty_name": "render - large - first render (mem)('django')", "last_rev": 1569, "last_value": 52064256.0, "last_err": 57344.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_lg_first", "idx": 1, "pretty_name": "render - large - first render (mem)('django-components')", "last_rev": 1569, "last_value": 54030336.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_lg_subsequent", "idx": 0, "pretty_name": "render - large - second render (mem)('django')", "last_rev": 1569, "last_value": 52074496.0, "last_err": 55296.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_lg_subsequent", "idx": 1, "pretty_name": "render - large - second render (mem)('django-components')", "last_rev": 1569, "last_value": 54534144.0, "last_err": 8192.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_sm_first", "idx": 0, "pretty_name": "render - small - first render (mem)('django')", "last_rev": 1569, "last_value": 43669504.0, "last_err": 2048.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_sm_first", "idx": 1, "pretty_name": "render - small - first render (mem)('django-components')", "last_rev": 1569, "last_value": 43923456.0, "last_err": 2048.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_sm_subsequent", "idx": 0, "pretty_name": "render - small - second render (mem)('django')", "last_rev": 1569, "last_value": 43673600.0, "last_err": 2048.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_sm_subsequent", "idx": 1, "pretty_name": "render - small - second render (mem)('django-components')", "last_rev": 1569, "last_value": 43927552.0, "last_err": 2048.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_lg_first", "idx": 0, "pretty_name": "render - large - first render('django')", "last_rev": 1569, "last_value": 0.0695505670000216, "last_err": 0.0, "prev_value": 0.06844023999997262, "change_rev": [1566, 1569]}, {"name": "Components vs Django.timeraw_render_lg_first", "idx": 1, "pretty_name": "render - large - first render('django-components')", "last_rev": 1569, "last_value": 0.2585547080000197, "last_err": 0.0, "prev_value": 0.25948228500001846, "change_rev": [1566, 1569]}, {"name": "Components vs Django.timeraw_render_lg_subsequent", "idx": 0, "pretty_name": "render - large - second render('django')", "last_rev": 1569, "last_value": 0.03280580699998836, "last_err": 6.2041063778393616e-06, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_lg_subsequent", "idx": 1, "pretty_name": "render - large - second render('django-components')", "last_rev": 1569, "last_value": 0.14556000400000357, "last_err": 0.0, "prev_value": 0.1461098879999838, "change_rev": [1566, 1569]}, {"name": "Components vs Django.timeraw_render_sm_first", "idx": 0, "pretty_name": "render - small - first render('django')", "last_rev": 1569, "last_value": 0.003512746000012612, "last_err": 0.0, "prev_value": 0.0035044859999970868, "change_rev": [1566, 1569]}, {"name": "Components vs Django.timeraw_render_sm_first", "idx": 1, "pretty_name": "render - small - first render('django-components')", "last_rev": 1569, "last_value": 0.004752005000000281, "last_err": 0.0, "prev_value": 0.004806205000022601, "change_rev": [1566, 1569]}, {"name": "Components vs Django.timeraw_render_sm_subsequent", "idx": 0, "pretty_name": "render - small - second render('django')", "last_rev": 1569, "last_value": 9.899399998403169e-05, "last_err": 0.0, "prev_value": 9.84330000051159e-05, "change_rev": [1566, 1569]}, {"name": "Components vs Django.timeraw_render_sm_subsequent", "idx": 1, "pretty_name": "render - small - second render('django-components')", "last_rev": 1569, "last_value": 0.0005454930000041713, "last_err": 0.0, "prev_value": 0.000542360999986613, "change_rev": [1566, 1569]}, {"name": "Components vs Django.timeraw_startup_lg", "idx": 0, "pretty_name": "startup - large('django')", "last_rev": 1569, "last_value": 0.20886826499997824, "last_err": 0.0, "prev_value": 0.21055065100000547, "change_rev": [1566, 1569]}, {"name": "Components vs Django.timeraw_startup_lg", "idx": 1, "pretty_name": "startup - large('django-components')", "last_rev": 1569, "last_value": 0.20461195600000792, "last_err": 0.0, "prev_value": 0.20605139500003133, "change_rev": [1566, 1569]}, {"name": "Other.timeraw_import_time", "idx": null, "pretty_name": "import time", "last_rev": 1569, "last_value": 0.1891247499999622, "last_err": 0.0, "prev_value": 0.19086866300000338, "change_rev": [1566, 1569]}, {"name": "isolated vs django modes.peakmem_render_lg_first", "idx": 0, "pretty_name": "render - large - first render (mem)('isolated')", "last_rev": 1569, "last_value": 53979136.0, "last_err": 38912.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_lg_first", "idx": 1, "pretty_name": "render - large - first render (mem)('django')", "last_rev": 1569, "last_value": 53536768.0, "last_err": 6144.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_lg_subsequent", "idx": 0, "pretty_name": "render - large - second render (mem)('isolated')", "last_rev": 1569, "last_value": 54568960.0, "last_err": 2048.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_lg_subsequent", "idx": 1, "pretty_name": "render - large - second render (mem)('django')", "last_rev": 1569, "last_value": 54528000.0, "last_err": 2048.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_sm_first", "idx": 0, "pretty_name": "render - small - first render (mem)('isolated')", "last_rev": 1569, "last_value": 43923456.0, "last_err": 2048.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_sm_first", "idx": 1, "pretty_name": "render - small - first render (mem)('django')", "last_rev": 1569, "last_value": 43806720.0, "last_err": 118784.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_sm_subsequent", "idx": 0, "pretty_name": "render - small - second render (mem)('isolated')", "last_rev": 1569, "last_value": 43927552.0, "last_err": 2048.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_sm_subsequent", "idx": 1, "pretty_name": "render - small - second render (mem)('django')", "last_rev": 1569, "last_value": 43927552.0, "last_err": 2048.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_lg_first", "idx": 0, "pretty_name": "render - large - first render('isolated')", "last_rev": 1569, "last_value": 0.2609166309999864, "last_err": 0.0, "prev_value": 0.2582084590000022, "change_rev": [1566, 1569]}, {"name": "isolated vs django modes.timeraw_render_lg_first", "idx": 1, "pretty_name": "render - large - first render('django')", "last_rev": 1569, "last_value": 0.26201485799998636, "last_err": 0.0, "prev_value": 0.2630794039999955, "change_rev": [1566, 1569]}, {"name": "isolated vs django modes.timeraw_render_lg_subsequent", "idx": 0, "pretty_name": "render - large - second render('isolated')", "last_rev": 1569, "last_value": 0.14612163999998984, "last_err": 7.454397835044414e-05, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_lg_subsequent", "idx": 1, "pretty_name": "render - large - second render('django')", "last_rev": 1569, "last_value": 0.15001642000004267, "last_err": 0.0001341061601557983, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_sm_first", "idx": 0, "pretty_name": "render - small - first render('isolated')", "last_rev": 1569, "last_value": 0.004790214000024662, "last_err": 0.0, "prev_value": 0.004762013999993542, "change_rev": [1566, 1569]}, {"name": "isolated vs django modes.timeraw_render_sm_first", "idx": 1, "pretty_name": "render - small - first render('django')", "last_rev": 1569, "last_value": 0.004819428000018888, "last_err": 0.0, "prev_value": 0.004786298999988503, "change_rev": [1566, 1569]}, {"name": "isolated vs django modes.timeraw_render_sm_subsequent", "idx": 0, "pretty_name": "render - small - second render('isolated')", "last_rev": 1569, "last_value": 0.0005448759999922004, "last_err": 4.3987187637440414e-07, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_sm_subsequent", "idx": 1, "pretty_name": "render - small - second render('django')", "last_rev": 1569, "last_value": 0.0005416959999706705, "last_err": 0.0, "prev_value": 0.0005334049999987656, "change_rev": [1566, 1569]}, {"name": "isolated vs django modes.timeraw_startup_lg", "idx": 0, "pretty_name": "startup - large('isolated')", "last_rev": 1569, "last_value": 0.20448447999996233, "last_err": 0.0, "prev_value": 0.2058522649999759, "change_rev": [1566, 1569]}, {"name": "isolated vs django modes.timeraw_startup_lg", "idx": 1, "pretty_name": "startup - large('django')", "last_rev": 1569, "last_value": 0.2037191150000126, "last_err": 0.0, "prev_value": 0.2053180329999691, "change_rev": [1566, 1569]}]
\ No newline at end of file
+[{"name": "Components vs Django.peakmem_render_lg_first", "idx": 0, "pretty_name": "render - large - first render (mem)('django')", "last_rev": 1662, "last_value": 52920320.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_lg_first", "idx": 1, "pretty_name": "render - large - first render (mem)('django-components')", "last_rev": 1662, "last_value": 54566912.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_lg_subsequent", "idx": 0, "pretty_name": "render - large - second render (mem)('django')", "last_rev": 1662, "last_value": 53800960.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_lg_subsequent", "idx": 1, "pretty_name": "render - large - second render (mem)('django-components')", "last_rev": 1662, "last_value": 54734848.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_sm_first", "idx": 0, "pretty_name": "render - small - first render (mem)('django')", "last_rev": 1662, "last_value": 44191744.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_sm_first", "idx": 1, "pretty_name": "render - small - first render (mem)('django-components')", "last_rev": 1662, "last_value": 44191744.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_sm_subsequent", "idx": 0, "pretty_name": "render - small - second render (mem)('django')", "last_rev": 1662, "last_value": 44195840.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.peakmem_render_sm_subsequent", "idx": 1, "pretty_name": "render - small - second render (mem)('django-components')", "last_rev": 1662, "last_value": 44187648.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_lg_first", "idx": 0, "pretty_name": "render - large - first render('django')", "last_rev": 1662, "last_value": 0.06960565700001098, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_lg_first", "idx": 1, "pretty_name": "render - large - first render('django-components')", "last_rev": 1662, "last_value": 0.25608221199996706, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_lg_subsequent", "idx": 0, "pretty_name": "render - large - second render('django')", "last_rev": 1662, "last_value": 0.03327357099999517, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_lg_subsequent", "idx": 1, "pretty_name": "render - large - second render('django-components')", "last_rev": 1662, "last_value": 0.1421111020000012, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_sm_first", "idx": 0, "pretty_name": "render - small - first render('django')", "last_rev": 1662, "last_value": 0.0035443229999998493, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_sm_first", "idx": 1, "pretty_name": "render - small - first render('django-components')", "last_rev": 1662, "last_value": 0.00467639600003622, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_sm_subsequent", "idx": 0, "pretty_name": "render - small - second render('django')", "last_rev": 1662, "last_value": 0.00010400499999718704, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_render_sm_subsequent", "idx": 1, "pretty_name": "render - small - second render('django-components')", "last_rev": 1662, "last_value": 0.0005328339999977061, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_startup_lg", "idx": 0, "pretty_name": "startup - large('django')", "last_rev": 1662, "last_value": 0.21775109000003567, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Components vs Django.timeraw_startup_lg", "idx": 1, "pretty_name": "startup - large('django-components')", "last_rev": 1662, "last_value": 0.21398552899995593, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "Other.timeraw_import_time", "idx": null, "pretty_name": "import time", "last_rev": 1662, "last_value": 0.19832900800003017, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_lg_first", "idx": 0, "pretty_name": "render - large - first render (mem)('isolated')", "last_rev": 1662, "last_value": 54439936.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_lg_first", "idx": 1, "pretty_name": "render - large - first render (mem)('django')", "last_rev": 1662, "last_value": 53968896.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_lg_subsequent", "idx": 0, "pretty_name": "render - large - second render (mem)('isolated')", "last_rev": 1662, "last_value": 54968320.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_lg_subsequent", "idx": 1, "pretty_name": "render - large - second render (mem)('django')", "last_rev": 1662, "last_value": 54792192.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_sm_first", "idx": 0, "pretty_name": "render - small - first render (mem)('isolated')", "last_rev": 1662, "last_value": 44187648.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_sm_first", "idx": 1, "pretty_name": "render - small - first render (mem)('django')", "last_rev": 1662, "last_value": 44183552.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_sm_subsequent", "idx": 0, "pretty_name": "render - small - second render (mem)('isolated')", "last_rev": 1662, "last_value": 44187648.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.peakmem_render_sm_subsequent", "idx": 1, "pretty_name": "render - small - second render (mem)('django')", "last_rev": 1662, "last_value": 44187648.0, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_lg_first", "idx": 0, "pretty_name": "render - large - first render('isolated')", "last_rev": 1662, "last_value": 0.2574955810000006, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_lg_first", "idx": 1, "pretty_name": "render - large - first render('django')", "last_rev": 1662, "last_value": 0.2591010970000127, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_lg_subsequent", "idx": 0, "pretty_name": "render - large - second render('isolated')", "last_rev": 1662, "last_value": 0.14273938200000202, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_lg_subsequent", "idx": 1, "pretty_name": "render - large - second render('django')", "last_rev": 1662, "last_value": 0.1464969190000147, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_sm_first", "idx": 0, "pretty_name": "render - small - first render('isolated')", "last_rev": 1662, "last_value": 0.004720848000005162, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_sm_first", "idx": 1, "pretty_name": "render - small - first render('django')", "last_rev": 1662, "last_value": 0.004705489000002672, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_sm_subsequent", "idx": 0, "pretty_name": "render - small - second render('isolated')", "last_rev": 1662, "last_value": 0.0005377129999999397, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_render_sm_subsequent", "idx": 1, "pretty_name": "render - small - second render('django')", "last_rev": 1662, "last_value": 0.0005395769999836375, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_startup_lg", "idx": 0, "pretty_name": "startup - large('isolated')", "last_rev": 1662, "last_value": 0.21402431699999624, "last_err": 0.0, "prev_value": null, "change_rev": null}, {"name": "isolated vs django modes.timeraw_startup_lg", "idx": 1, "pretty_name": "startup - large('django')", "last_rev": 1662, "last_value": 0.21364062999998623, "last_err": 0.0, "prev_value": null, "change_rev": null}]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_lg_first.json b/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_lg_first.json
index 803c0d30..bac348fb 100644
--- a/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_lg_first.json	
+++ b/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_lg_first.json	
@@ -1 +1 @@
-[[1566, 53067386.97974115], [1569, 53008970.27562818]]
\ No newline at end of file
+[[1662, 53737309.613078326]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_lg_subsequent.json b/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_lg_subsequent.json
index d6cec9e7..763d6ac1 100644
--- a/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_lg_subsequent.json	
+++ b/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_lg_subsequent.json	
@@ -1 +1 @@
-[[1566, 53314412.08868371], [1569, 53265830.36855053]]
\ No newline at end of file
+[[1662, 54265895.0709751]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_sm_first.json b/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_sm_first.json
index 2dd3c064..02cd8916 100644
--- a/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_sm_first.json	
+++ b/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_sm_first.json	
@@ -1 +1 @@
-[[1566, 43798343.942005485], [1569, 43794247.92479085]]
\ No newline at end of file
+[[1662, 44191743.99999999]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_sm_subsequent.json b/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_sm_subsequent.json
index 81ef5356..42602b0f 100644
--- a/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_sm_subsequent.json	
+++ b/dev/benchmarks/graphs/summary/Components vs Django.peakmem_render_sm_subsequent.json	
@@ -1 +1 @@
-[[1566, 43802439.95921688], [1569, 43798343.942005485]]
\ No newline at end of file
+[[1662, 44191743.81017703]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_lg_first.json b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_lg_first.json
index 0e11a019..4895fb7f 100644
--- a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_lg_first.json	
+++ b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_lg_first.json	
@@ -1 +1 @@
-[[1566, 0.13326301010086242], [1569, 0.13409931596367813]]
\ No newline at end of file
+[[1662, 0.13350944016163727]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_lg_subsequent.json b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_lg_subsequent.json
index 9ca315cc..86fb5933 100644
--- a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_lg_subsequent.json	
+++ b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_lg_subsequent.json	
@@ -1 +1 @@
-[[1566, 0.06924951360815947], [1569, 0.06910291888293614]]
\ No newline at end of file
+[[1662, 0.0687644082522681]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_sm_first.json b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_sm_first.json
index 272a72dc..dfd2cdda 100644
--- a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_sm_first.json	
+++ b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_sm_first.json	
@@ -1 +1 @@
-[[1566, 0.0041040563026955666], [1569, 0.0040856561964745545]]
\ No newline at end of file
+[[1662, 0.004071198582731586]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_sm_subsequent.json b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_sm_subsequent.json
index 1d520b59..cdc88d9b 100644
--- a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_sm_subsequent.json	
+++ b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_render_sm_subsequent.json	
@@ -1 +1 @@
-[[1566, 0.00023105458297652734], [1569, 0.00023238014982717938]]
\ No newline at end of file
+[[1662, 0.00023540900613243872]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_startup_lg.json b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_startup_lg.json
index e518a473..29de1006 100644
--- a/dev/benchmarks/graphs/summary/Components vs Django.timeraw_startup_lg.json	
+++ b/dev/benchmarks/graphs/summary/Components vs Django.timeraw_startup_lg.json	
@@ -1 +1 @@
-[[1566, 0.20828887477903343], [1569, 0.20672915674372966]]
\ No newline at end of file
+[[1662, 0.21586009863792485]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/Other.timeraw_import_time.json b/dev/benchmarks/graphs/summary/Other.timeraw_import_time.json
index 6745b517..24d2f960 100644
--- a/dev/benchmarks/graphs/summary/Other.timeraw_import_time.json
+++ b/dev/benchmarks/graphs/summary/Other.timeraw_import_time.json
@@ -1 +1 @@
-[[1566, 0.19086866300000338], [1569, 0.1891247499999622]]
\ No newline at end of file
+[[1662, 0.19832900800003017]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_lg_first.json b/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_lg_first.json
index 051be041..611a1352 100644
--- a/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_lg_first.json	
+++ b/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_lg_first.json	
@@ -1 +1 @@
-[[1566, 53779955.28517828], [1569, 53735033.72493383]]
\ No newline at end of file
+[[1662, 54203904.32644733]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_lg_subsequent.json b/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_lg_subsequent.json
index 5ef1e762..9675555e 100644
--- a/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_lg_subsequent.json	
+++ b/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_lg_subsequent.json	
@@ -1 +1 @@
-[[1566, 54550524.155578785], [1569, 54546428.1552901]]
\ No newline at end of file
+[[1662, 54880185.34368702]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_sm_first.json b/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_sm_first.json
index 1a487cdc..11ec6009 100644
--- a/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_sm_first.json	
+++ b/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_sm_first.json	
@@ -1 +1 @@
-[[1566, 43925504.00000001], [1569, 43804516.45360199]]
\ No newline at end of file
+[[1662, 44185599.95253766]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_sm_subsequent.json b/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_sm_subsequent.json
index 2e015085..5346f5e3 100644
--- a/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_sm_subsequent.json	
+++ b/dev/benchmarks/graphs/summary/isolated vs django modes.peakmem_render_sm_subsequent.json	
@@ -1 +1 @@
-[[1566, 43929599.99999999], [1569, 43925504.00000001]]
\ No newline at end of file
+[[1662, 44187648.0]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_lg_first.json b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_lg_first.json
index 843c675c..5c308443 100644
--- a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_lg_first.json	
+++ b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_lg_first.json	
@@ -1 +1 @@
-[[1566, 0.2606325526511949], [1569, 0.26146516789296487]]
\ No newline at end of file
+[[1662, 0.2582970915627115]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_lg_subsequent.json b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_lg_subsequent.json
index 4541392d..09ddd58c 100644
--- a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_lg_subsequent.json	
+++ b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_lg_subsequent.json	
@@ -1 +1 @@
-[[1566, 0.14805622350084952], [1569, 0.1483139223040422]]
\ No newline at end of file
+[[1662, 0.144605946222714]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_sm_first.json b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_sm_first.json
index 094a9bcc..5f633172 100644
--- a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_sm_first.json	
+++ b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_sm_first.json	
@@ -1 +1 @@
-[[1566, 0.004774141058462804], [1569, 0.004804798796807347]]
\ No newline at end of file
+[[1662, 0.004713162243622524]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_sm_subsequent.json b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_sm_subsequent.json
index 4aca4a4a..b462ba7b 100644
--- a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_sm_subsequent.json	
+++ b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_render_sm_subsequent.json	
@@ -1 +1 @@
-[[1566, 0.0005391099913516415], [1569, 0.0005426970749629188]]
\ No newline at end of file
+[[1662, 0.0005386441936864901]]
\ No newline at end of file
diff --git a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_startup_lg.json b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_startup_lg.json
index 07320514..9a5acd4f 100644
--- a/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_startup_lg.json	
+++ b/dev/benchmarks/graphs/summary/isolated vs django modes.timeraw_startup_lg.json	
@@ -1 +1 @@
-[[1566, 0.20558497546849924], [1569, 0.20410143874267547]]
\ No newline at end of file
+[[1662, 0.21383238744211777]]
\ No newline at end of file
diff --git a/dev/benchmarks/index.json b/dev/benchmarks/index.json
index 51fda184..232c5702 100644
--- a/dev/benchmarks/index.json
+++ b/dev/benchmarks/index.json
@@ -1 +1 @@
-{"project": "django-components", "project_url": "/django-components/", "show_commit_url": "#", "hash_length": 8, "revision_to_hash": {"1542": "0e41d072ceeb56d3347993fba0c4793bdced0f1f", "1547": "e04f07a327237d5d70f59e926e4e7b76b88393b9", "1550": "96d3318f118beb7e651e6e8e9151573250f9c910", "1553": "966af68377f38d1b884eb41f9cdb8741a5641661", "1556": "3050e89f725a4289c1ddb09f6e0b55100f0d38fb", "1559": "9ca429d0e92d1ca035bbae54016a815171f3b455", "1563": "9faf111550b4e4ca90bc4af5cb257b59ff686ff5", "1566": "852e1f3916c902fa92ea1066a4e299a012ffa2d9", "1569": "778068dd96aadef1a364504209afe8fb9442302e"}, "revision_to_date": {"1542": 1740175931000, "1547": 1740178203000, "1550": 1740178613000, "1553": 1740209008000, "1556": 1740210119000, "1559": 1740211594000, "1563": 1740212394000, "1566": 1740212920000, "1569": 1740213699000}, "params": {"machine": ["ci-linux"], "python": ["3.13"], "django": ["5.1"], "djc-core-html-parser": [""], "branch": ["master"]}, "graph_param_list": [{"machine": "ci-linux", "python": "3.13", "django": "5.1", "djc-core-html-parser": "", "branch": "master"}], "benchmarks": {"Components vs Django.peakmem_render_lg_first": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - large - first render (mem)\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        setup=lambda renderer: setup_templating_memory_benchmark(renderer, \"lg\", \"first\", \"isolated\"),\n    )\n    def peakmem_render_lg_first(self, renderer: TemplatingRenderer):\n        do_render()\n\nsetup=lambda renderer: setup_templating_memory_benchmark(renderer, \"lg\", \"first\", \"isolated\"),", "name": "Components vs Django.peakmem_render_lg_first", "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - large - first render (mem)", "type": "peakmemory", "unit": "bytes", "version": "301c396f017f45a5b3f71e85df58d15f54153fcfd951af7ef424641d4b31b528"}, "Components vs Django.peakmem_render_lg_subsequent": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - large - second render (mem)\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        setup=lambda renderer: setup_templating_memory_benchmark(renderer, \"lg\", \"subsequent\", \"isolated\"),\n    )\n    def peakmem_render_lg_subsequent(self, renderer: TemplatingRenderer):\n        do_render()\n\nsetup=lambda renderer: setup_templating_memory_benchmark(renderer, \"lg\", \"subsequent\", \"isolated\"),", "name": "Components vs Django.peakmem_render_lg_subsequent", "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - large - second render (mem)", "type": "peakmemory", "unit": "bytes", "version": "9a44e9999ef3ef42ea7e01323727490244febb43d66a87a4d8f88c6b8a133b8b"}, "Components vs Django.peakmem_render_sm_first": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - small - first render (mem)\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        setup=lambda renderer: setup_templating_memory_benchmark(renderer, \"sm\", \"first\", \"isolated\"),\n    )\n    def peakmem_render_sm_first(self, renderer: TemplatingRenderer):\n        do_render()\n\nsetup=lambda renderer: setup_templating_memory_benchmark(renderer, \"sm\", \"first\", \"isolated\"),", "name": "Components vs Django.peakmem_render_sm_first", "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - small - first render (mem)", "type": "peakmemory", "unit": "bytes", "version": "e93b7a5193681c883edf85bdb30b1bc0821263bf51033fdcee215b155085e036"}, "Components vs Django.peakmem_render_sm_subsequent": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - small - second render (mem)\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        setup=lambda renderer: setup_templating_memory_benchmark(renderer, \"sm\", \"subsequent\", \"isolated\"),\n    )\n    def peakmem_render_sm_subsequent(self, renderer: TemplatingRenderer):\n        do_render()\n\nsetup=lambda renderer: setup_templating_memory_benchmark(renderer, \"sm\", \"subsequent\", \"isolated\"),", "name": "Components vs Django.peakmem_render_sm_subsequent", "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - small - second render (mem)", "type": "peakmemory", "unit": "bytes", "version": "b46e0820b18950aa7cc5e61306ff3425b76b4da9dca42d64fae5b1d25c6c9026"}, "Components vs Django.timeraw_render_lg_first": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - large - first render\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        include_in_quick_benchmark=True,\n    )\n    def timeraw_render_lg_first(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"lg\", \"first\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_render_lg_first", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - large - first render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "be3bf6236960046a028b6ea007aad28b2337fc2b906b8ce317a09a5d4f1a6193", "warmup_time": -1}, "Components vs Django.timeraw_render_lg_subsequent": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - large - second render\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n    )\n    def timeraw_render_lg_subsequent(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"lg\", \"subsequent\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_render_lg_subsequent", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - large - second render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "b98221c11a0ee6e9de0778d416d31b9dd514a674d9017a2bb9b2fc1cd0f01920", "warmup_time": -1}, "Components vs Django.timeraw_render_sm_first": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - small - first render\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n    )\n    def timeraw_render_sm_first(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"sm\", \"first\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_render_sm_first", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - small - first render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "f1fc17e4a31c71f4d9265f1122da52e7cf57addb4dfa02606e303b33d6431b9b", "warmup_time": -1}, "Components vs Django.timeraw_render_sm_subsequent": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - small - second render\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n    )\n    def timeraw_render_sm_subsequent(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"sm\", \"subsequent\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_render_sm_subsequent", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - small - second render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "6fce1cd85a9344fee383b40a22f27862120b9488a628420625592dc14e0307d3", "warmup_time": -1}, "Components vs Django.timeraw_startup_lg": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"startup - large\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n    )\n    def timeraw_startup_lg(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"lg\", \"startup\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_startup_lg", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "startup - large", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "53151821c128ad0ecfb0707fff3146e1abd8d0bcfa301aa056b5d3fae3d793e2", "warmup_time": -1}, "Other.timeraw_import_time": {"code": "class OtherTests:\n    @benchmark(\n        pretty_name=\"import time\",\n        group_name=OTHER_GROUP,\n        number=1,\n        rounds=5,\n    )\n    def timeraw_import_time(self):\n        return prepare_templating_benchmark(\"django-components\", \"lg\", \"startup\", \"isolated\", imports_only=True)", "min_run_count": 2, "name": "Other.timeraw_import_time", "number": 1, "param_names": [], "params": [], "pretty_name": "import time", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "a0a1c1c0db22509410b946d0d4384b52ea4a09b47b6048d7d1cfb89b0c7fe5c3", "warmup_time": -1}, "isolated vs django modes.peakmem_render_lg_first": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - large - first render (mem)\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n        setup=lambda context_mode: setup_templating_memory_benchmark(\n            \"django-components\",\n            \"lg\",\n            \"first\",\n            context_mode,\n        ),\n    )\n    def peakmem_render_lg_first(self, context_mode: DjcContextMode):\n        do_render()\n\nsetup=lambda context_mode: setup_templating_memory_benchmark(\n    \"django-components\",\n    \"lg\",\n    \"first\",\n    context_mode,\n),", "name": "isolated vs django modes.peakmem_render_lg_first", "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - large - first render (mem)", "type": "peakmemory", "unit": "bytes", "version": "c4bf0016d48d210f08b8db733b57c7dcba1cebbf548c458b93b86ace387067e9"}, "isolated vs django modes.peakmem_render_lg_subsequent": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - large - second render (mem)\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n        setup=lambda context_mode: setup_templating_memory_benchmark(\n            \"django-components\",\n            \"lg\",\n            \"subsequent\",\n            context_mode,\n        ),\n    )\n    def peakmem_render_lg_subsequent(self, context_mode: DjcContextMode):\n        do_render()\n\nsetup=lambda context_mode: setup_templating_memory_benchmark(\n    \"django-components\",\n    \"lg\",\n    \"subsequent\",\n    context_mode,\n),", "name": "isolated vs django modes.peakmem_render_lg_subsequent", "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - large - second render (mem)", "type": "peakmemory", "unit": "bytes", "version": "65bb1b8586487197a79bb6073e4c71642877b845b6eb42d1bd32398299daffbf"}, "isolated vs django modes.peakmem_render_sm_first": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - small - first render (mem)\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n        setup=lambda context_mode: setup_templating_memory_benchmark(\"django-components\", \"sm\", \"first\", context_mode),\n    )\n    def peakmem_render_sm_first(self, context_mode: DjcContextMode):\n        do_render()\n\nsetup=lambda context_mode: setup_templating_memory_benchmark(\"django-components\", \"sm\", \"first\", context_mode),", "name": "isolated vs django modes.peakmem_render_sm_first", "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - small - first render (mem)", "type": "peakmemory", "unit": "bytes", "version": "c51b91fc583295776062822225e720b5ed71aef9c9288217c401c54283c62840"}, "isolated vs django modes.peakmem_render_sm_subsequent": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - small - second render (mem)\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n        setup=lambda context_mode: setup_templating_memory_benchmark(\n            \"django-components\",\n            \"sm\",\n            \"subsequent\",\n            context_mode,\n        ),\n    )\n    def peakmem_render_sm_subsequent(self, context_mode: DjcContextMode):\n        do_render()\n\nsetup=lambda context_mode: setup_templating_memory_benchmark(\n    \"django-components\",\n    \"sm\",\n    \"subsequent\",\n    context_mode,\n),", "name": "isolated vs django modes.peakmem_render_sm_subsequent", "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - small - second render (mem)", "type": "peakmemory", "unit": "bytes", "version": "54d747fb8f40179b7ff3d2fc49eb195909ad1c880b5ef7b82f82742b27b67260"}, "isolated vs django modes.timeraw_render_lg_first": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - large - first render\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_render_lg_first(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"lg\", \"first\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_render_lg_first", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - large - first render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "f94af83427c6346f88f8785a3cd2fc42415ac5a9fbbdb7de71d27e22e6a81699", "warmup_time": -1}, "isolated vs django modes.timeraw_render_lg_subsequent": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - large - second render\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_render_lg_subsequent(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"lg\", \"subsequent\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_render_lg_subsequent", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - large - second render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "9f7c2fde6b33f0451a1794ed903c48d96cd7822f67da502cec36fe8e977c2414", "warmup_time": -1}, "isolated vs django modes.timeraw_render_sm_first": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - small - first render\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_render_sm_first(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"sm\", \"first\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_render_sm_first", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - small - first render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "d15ca68909d7f1f43ff16863befb6f42681f17461417fc0069eefd6db3569296", "warmup_time": -1}, "isolated vs django modes.timeraw_render_sm_subsequent": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - small - second render\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_render_sm_subsequent(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"sm\", \"subsequent\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_render_sm_subsequent", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - small - second render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "7444bc9516dd087e3f420349345eae991ad6941bbd22fce45265b18034b7cf77", "warmup_time": -1}, "isolated vs django modes.timeraw_startup_lg": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"startup - large\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_startup_lg(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"lg\", \"startup\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_startup_lg", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "startup - large", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "eabe311ebee4a15c5816617be12f00ec30376f7506bd668219e1c50bc897c134", "warmup_time": -1}}, "machines": {"ci-linux": {"machine": "ci-linux", "version": 1}}, "tags": {"0.131": 1542, "0.133": 1547, "0.134": 1550, "0.135": 1553, "0.136": 1556, "0.137": 1559, "0.138": 1563, "0.139": 1566, "0.140": 1569}, "pages": [["", "Grid view", "Display as a agrid"], ["summarylist", "List view", "Display as a list"], ["regressions", "Show regressions", "Display information about recent regressions"]]}
\ No newline at end of file
+{"project": "django-components", "project_url": "/django-components/", "show_commit_url": "#", "hash_length": 8, "revision_to_hash": {"250": "45a18626d74b280aa05498aa380eba687010cc0f", "268": "c9f0068741871b24756045805aaab8fbf368601a", "343": "ed2cd57bdcc12bf390f42058061a6ed077e558b0", "359": "501a055fe21abb4c7ad9af1a3a1b42eea24afacf", "369": "1937d594100d0651b151c8edbe1189b5a88b358f", "380": "1d091f50999cca0fa8c7852da2ea71684eadda6d", "388": "f5c3f64c866d06dfa2435d1d18b936dddb9eb67c", "427": "24d9db39c3c55f5eb91c9ce2112ad22507ccdd60", "457": "9103eda2f4ed80f46ff03d215491009c5476b410", "487": "384ff79e0875ac3a64a2755010ef86ec09a090b5", "500": "c102019811586f40cb11952f283797ddee96de3c", "503": "a350ad1a869bb46c6bac093f54ac40ea85d8cd8f", "508": "16022429da16e459b8a1e6e9cd8ab41d95dcb59d", "536": "ea7beb518c435389d9daff7ea557eec9ddc2464e", "550": "2cfc7285e12677a54247e9998967081c0e031efc", "552": "fcbfae3c5f0611519636290ef99b25bc0a319825", "564": "316310e842f276fd43436b432781430bd255410b", "575": "e0a5c2a4bcf5e8f577e19333e3b719440c37b10b", "577": "c174aa9802cc73b5d8fef4b0c704de3fb68b1cbb", "598": "979781012532f18c147a570ff4441c65c7503b6f", "612": "9d7d0b40b9d3bbd8e5b754e3b1b20df982cdd184", "622": "24032ac2ea80627f0fdde88058a2c3fbcae0d3fe", "646": "4f1a8184465fc472995bc226bebd66c250d501f6", "651": "8ce649498ff63a64761c83cf713983b7e2f24b81", "663": "93facba53e050619a477fa214da89fccf118ec13", "675": "ea33e0db6c54486b67e2fa496ec1c3ec3de06ec7", "681": "6874b1531df0e8836000bbc76fcca5a3de42724a", "691": "9f4243232018708fdf330f0e922a09317c60234c", "704": "188a9dc7eef4c45ee4f87efa8a0d6728e94f210d", "724": "76a0cde3af7b3061127d149c138fbc78462a07fe", "729": "c932f28cb4840dc45d2d26b4d927c1480459272f", "742": "7058f05e0415965ddd162d0ba663c5106e7ffb66", "748": "95d6eacb5c03a611f92cd9a6e254cea7e0ce57eb", "752": "d512cfb0fec8a42ab58d2f106047fc4c0ec65427", "757": "04160f4e0b2ec4d901d6724c34ed8df883363064", "773": "20847b978b3ddb5979489fbb4bd8e971b9b16fbf", "775": "ae5cda9f727454a077ab16c51a237fec076bd442", "779": "cd791caa572c9acd6d56445c04d6c9b55a50c602", "787": "274be104789e31955f88e26f14c89ed648f25448", "806": "c3a80b729049b5ea1b4799e742e4100a7640efab", "845": "0abb5aa63ff0396328ef4dfdc2e78e872671f135", "855": "e4e787b29dc9cd2cf35ad02f22bad6fa15a7211c", "867": "e346c07298b268d9212fcf93d132968e69824730", "884": "2316f79dff66260b7a9fe91effb55c74524deca0", "887": "085c60a8c96442d9fd4f72d66a7eb295e7cfb2d9", "889": "ba86cee578490df944ad167674db32182b8bbf7b", "891": "dd292b03508b7c03b2ad4f9fb9c17dec747845ba", "898": "badffdda3538a8082137453c757509ed4f035a3e", "902": "c07f0e634121ced0119bb665ed544ca4447c416b", "904": "8bbe81d7171ec3512f250927653d8454c7ff005e", "908": "881c36219a45581086da35a17d3715ee0698ca88", "910": "9bfb50b8f27f7ff521226109ab30426633f6b514", "912": "3a7d5355cfa5d37641a4c80ee9fd2423cea10c1b", "930": "09a720009767f45bebcfa48f3587219c03082601", "935": "a4b4905bee778a51f9a99a042ce14ed2424cc9fb", "940": "31257a475dcfdacaaeb408f59ea92b736a668815", "942": "d47927054c820ecf3f9f97a62f03dfbb5496a11b", "956": "fbbbf6c694b8213832fc127ee8a3e31872308aff", "958": "d819f3ff491866abaeb9a7dbba6a6ca3c21da9f8", "960": "c202c5a901106392ccdde49100211182c986eca5", "965": "7bbfcf7565159d92de41bb0d738b7878d78f4533", "978": "b89c09aa5f13903b1d056c70afbfd327f0ed6362", "980": "03af25aad6841b6edb56c925d2599817e08ceb44", "982": "5cb649fae62a42e525c1ea9fb74d7838886cc1a8", "986": "f97717cdb35eaadb78b1f468728b1bd386e742d8", "1056": "b26a2011380c959bfc98043821f6b4aa337a281d", "1058": "8c5b088c31b7166932e18739f882c2eef632f3a4", "1060": "682bfc42397c0bdbeb1a2b6ccabb8aca89686d4f", "1089": "8f13a641ac096e93a0464f048a4fa53e591bb8db", "1098": "30d04fe1b053e6c5de0b6f34a7758a627517be8c", "1125": "f7846b9c0ae7a8fd0b7f6edf664316e485455e76", "1132": "a3d66586b19b7e2aacbf793edfba20bcd9858f4a", "1179": "0064de9c78db5eccc7c498e2a6d4c3c5ffa745ec", "1252": "d093bfb05212555e14c5cd46c94b0ba057cbeceb", "1270": "c0a4fd5f685d694218b583b2d0a3e8417925d53a", "1277": "2a4b0f52894d5d0bb8d325d6096a3950286db541", "1282": "5a23101038d7085959087b2352e71590eafe9529", "1287": "ce3305a5fff095e990707de851f85bc27120596c", "1312": "cdc830fca3bdd98669e0510841536be14d1bd728", "1328": "468a593a472c35379fe7567918e8a534b2d53748", "1337": "2f14e8e0908657459909c6338106e561edc5d0f4", "1352": "a5659691d0f947643ce6542b7f09075e3f931646", "1361": "aaeba99f54b206baed072ffd0572035ddf5118a7", "1366": "6813c9d7aa4acfb04df9665651a2864d04bbe8ba", "1381": "6681fc0085fdb4b76cb74c1bbf20d44fa22f40fe", "1387": "6bb73bd8afd350db84889efc09b74255cea08979", "1392": "c76f8198dd497b34735fc17a0f7a678bdd811a3f", "1447": "3bbd4326e6c1bfb4a02039e16021a3f720910308", "1488": "914576e68133bc6ec356f3918016c45691ed3534", "1505": "3d187d7abad80f8464bd70dfba847d27a8e173db", "1514": "e105500350a320dfccf36fc19cad7421d38c3736", "1546": "61515b34540d27311fc3286b50212c1e314ce39e", "1571": "691443a0a821eb1a02f9b42ad0e32bcd71d94943", "1591": "dcd4203eeadafc5d500b4b72c5cf04f1fe7317e7", "1662": "d0a42a2698f2ba21e7ab2dec750c5dbadeda0db5"}, "revision_to_date": {"250": 1630912817000, "268": 1631273531000, "343": 1654029104000, "359": 1657786741000, "369": 1657798498000, "380": 1658057264000, "388": 1658128984000, "427": 1670931380000, "457": 1673095465000, "487": 1675977478000, "500": 1678833725000, "503": 1678834812000, "508": 1679329468000, "536": 1680808865000, "550": 1681214445000, "552": 1681388770000, "564": 1682351069000, "575": 1684433482000, "577": 1684760359000, "598": 1693734426000, "612": 1695996512000, "622": 1696883504000, "646": 1702127213000, "651": 1702852887000, "663": 1705268832000, "675": 1705701480000, "681": 1706343740000, "691": 1706393538000, "704": 1707467055000, "724": 1708588716000, "729": 1708984309000, "742": 1709796107000, "748": 1710542375000, "752": 1711216985000, "757": 1711278671000, "773": 1711752109000, "775": 1711786713000, "779": 1712212506000, "787": 1712872453000, "806": 1713128940000, "845": 1713390260000, "855": 1713901297000, "867": 1714590581000, "884": 1714912319000, "887": 1715087715000, "889": 1715111097000, "891": 1715505986000, "898": 1716105516000, "902": 1716441018000, "904": 1716488913000, "908": 1717051130000, "910": 1717227227000, "912": 1717232115000, "930": 1718176374000, "935": 1718991590000, "940": 1720427258000, "942": 1720429478000, "956": 1722279535000, "958": 1722325182000, "960": 1722666822000, "965": 1722890429000, "978": 1723843975000, "980": 1723993321000, "982": 1724243667000, "986": 1724363119000, "1056": 1724732902000, "1058": 1724824521000, "1060": 1724924003000, "1089": 1725480929000, "1098": 1725655525000, "1125": 1726084755000, "1132": 1726347108000, "1179": 1728564427000, "1252": 1732525062000, "1270": 1732629701000, "1277": 1732644681000, "1282": 1732658332000, "1287": 1732726640000, "1312": 1733164405000, "1328": 1733471329000, "1337": 1733644953000, "1352": 1733834654000, "1361": 1734080521000, "1366": 1734245122000, "1381": 1734464187000, "1387": 1734600366000, "1392": 1734955786000, "1447": 1736287315000, "1488": 1737558545000, "1505": 1738157680000, "1514": 1738404847000, "1546": 1738662755000, "1571": 1739736734000, "1591": 1740050674000, "1662": 1742502414000}, "params": {"machine": ["ci-linux"], "python": ["3.13"], "django": ["5.1"], "djc-core-html-parser": [""], "branch": ["master"]}, "graph_param_list": [{"machine": "ci-linux", "python": "3.13", "django": "5.1", "djc-core-html-parser": "", "branch": "master"}], "benchmarks": {"Components vs Django.peakmem_render_lg_first": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - large - first render (mem)\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        setup=lambda renderer: setup_templating_memory_benchmark(renderer, \"lg\", \"first\", \"isolated\"),\n    )\n    def peakmem_render_lg_first(self, renderer: TemplatingRenderer):\n        do_render()\n\nsetup=lambda renderer: setup_templating_memory_benchmark(renderer, \"lg\", \"first\", \"isolated\"),", "name": "Components vs Django.peakmem_render_lg_first", "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - large - first render (mem)", "type": "peakmemory", "unit": "bytes", "version": "301c396f017f45a5b3f71e85df58d15f54153fcfd951af7ef424641d4b31b528"}, "Components vs Django.peakmem_render_lg_subsequent": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - large - second render (mem)\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        setup=lambda renderer: setup_templating_memory_benchmark(renderer, \"lg\", \"subsequent\", \"isolated\"),\n    )\n    def peakmem_render_lg_subsequent(self, renderer: TemplatingRenderer):\n        do_render()\n\nsetup=lambda renderer: setup_templating_memory_benchmark(renderer, \"lg\", \"subsequent\", \"isolated\"),", "name": "Components vs Django.peakmem_render_lg_subsequent", "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - large - second render (mem)", "type": "peakmemory", "unit": "bytes", "version": "9a44e9999ef3ef42ea7e01323727490244febb43d66a87a4d8f88c6b8a133b8b"}, "Components vs Django.peakmem_render_sm_first": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - small - first render (mem)\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        setup=lambda renderer: setup_templating_memory_benchmark(renderer, \"sm\", \"first\", \"isolated\"),\n    )\n    def peakmem_render_sm_first(self, renderer: TemplatingRenderer):\n        do_render()\n\nsetup=lambda renderer: setup_templating_memory_benchmark(renderer, \"sm\", \"first\", \"isolated\"),", "name": "Components vs Django.peakmem_render_sm_first", "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - small - first render (mem)", "type": "peakmemory", "unit": "bytes", "version": "e93b7a5193681c883edf85bdb30b1bc0821263bf51033fdcee215b155085e036"}, "Components vs Django.peakmem_render_sm_subsequent": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - small - second render (mem)\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        setup=lambda renderer: setup_templating_memory_benchmark(renderer, \"sm\", \"subsequent\", \"isolated\"),\n    )\n    def peakmem_render_sm_subsequent(self, renderer: TemplatingRenderer):\n        do_render()\n\nsetup=lambda renderer: setup_templating_memory_benchmark(renderer, \"sm\", \"subsequent\", \"isolated\"),", "name": "Components vs Django.peakmem_render_sm_subsequent", "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - small - second render (mem)", "type": "peakmemory", "unit": "bytes", "version": "b46e0820b18950aa7cc5e61306ff3425b76b4da9dca42d64fae5b1d25c6c9026"}, "Components vs Django.timeraw_render_lg_first": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - large - first render\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n        include_in_quick_benchmark=True,\n    )\n    def timeraw_render_lg_first(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"lg\", \"first\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_render_lg_first", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - large - first render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "be3bf6236960046a028b6ea007aad28b2337fc2b906b8ce317a09a5d4f1a6193", "warmup_time": -1}, "Components vs Django.timeraw_render_lg_subsequent": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - large - second render\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n    )\n    def timeraw_render_lg_subsequent(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"lg\", \"subsequent\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_render_lg_subsequent", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - large - second render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "b98221c11a0ee6e9de0778d416d31b9dd514a674d9017a2bb9b2fc1cd0f01920", "warmup_time": -1}, "Components vs Django.timeraw_render_sm_first": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - small - first render\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n    )\n    def timeraw_render_sm_first(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"sm\", \"first\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_render_sm_first", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - small - first render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "f1fc17e4a31c71f4d9265f1122da52e7cf57addb4dfa02606e303b33d6431b9b", "warmup_time": -1}, "Components vs Django.timeraw_render_sm_subsequent": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"render - small - second render\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n    )\n    def timeraw_render_sm_subsequent(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"sm\", \"subsequent\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_render_sm_subsequent", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "render - small - second render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "6fce1cd85a9344fee383b40a22f27862120b9488a628420625592dc14e0307d3", "warmup_time": -1}, "Components vs Django.timeraw_startup_lg": {"code": "class DjangoComponentsVsDjangoTests:\n    @benchmark(\n        pretty_name=\"startup - large\",\n        group_name=DJC_VS_DJ_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"renderer\": [\"django\", \"django-components\"],\n        },\n    )\n    def timeraw_startup_lg(self, renderer: TemplatingRenderer):\n        return prepare_templating_benchmark(renderer, \"lg\", \"startup\", \"isolated\")", "min_run_count": 2, "name": "Components vs Django.timeraw_startup_lg", "number": 1, "param_names": ["renderer"], "params": [["'django'", "'django-components'"]], "pretty_name": "startup - large", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "53151821c128ad0ecfb0707fff3146e1abd8d0bcfa301aa056b5d3fae3d793e2", "warmup_time": -1}, "Other.timeraw_import_time": {"code": "class OtherTests:\n    @benchmark(\n        pretty_name=\"import time\",\n        group_name=OTHER_GROUP,\n        number=1,\n        rounds=5,\n    )\n    def timeraw_import_time(self):\n        return prepare_templating_benchmark(\"django-components\", \"lg\", \"startup\", \"isolated\", imports_only=True)", "min_run_count": 2, "name": "Other.timeraw_import_time", "number": 1, "param_names": [], "params": [], "pretty_name": "import time", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "a0a1c1c0db22509410b946d0d4384b52ea4a09b47b6048d7d1cfb89b0c7fe5c3", "warmup_time": -1}, "isolated vs django modes.peakmem_render_lg_first": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - large - first render (mem)\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n        setup=lambda context_mode: setup_templating_memory_benchmark(\n            \"django-components\",\n            \"lg\",\n            \"first\",\n            context_mode,\n        ),\n    )\n    def peakmem_render_lg_first(self, context_mode: DjcContextMode):\n        do_render()\n\nsetup=lambda context_mode: setup_templating_memory_benchmark(\n    \"django-components\",\n    \"lg\",\n    \"first\",\n    context_mode,\n),", "name": "isolated vs django modes.peakmem_render_lg_first", "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - large - first render (mem)", "type": "peakmemory", "unit": "bytes", "version": "c4bf0016d48d210f08b8db733b57c7dcba1cebbf548c458b93b86ace387067e9"}, "isolated vs django modes.peakmem_render_lg_subsequent": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - large - second render (mem)\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n        setup=lambda context_mode: setup_templating_memory_benchmark(\n            \"django-components\",\n            \"lg\",\n            \"subsequent\",\n            context_mode,\n        ),\n    )\n    def peakmem_render_lg_subsequent(self, context_mode: DjcContextMode):\n        do_render()\n\nsetup=lambda context_mode: setup_templating_memory_benchmark(\n    \"django-components\",\n    \"lg\",\n    \"subsequent\",\n    context_mode,\n),", "name": "isolated vs django modes.peakmem_render_lg_subsequent", "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - large - second render (mem)", "type": "peakmemory", "unit": "bytes", "version": "65bb1b8586487197a79bb6073e4c71642877b845b6eb42d1bd32398299daffbf"}, "isolated vs django modes.peakmem_render_sm_first": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - small - first render (mem)\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n        setup=lambda context_mode: setup_templating_memory_benchmark(\"django-components\", \"sm\", \"first\", context_mode),\n    )\n    def peakmem_render_sm_first(self, context_mode: DjcContextMode):\n        do_render()\n\nsetup=lambda context_mode: setup_templating_memory_benchmark(\"django-components\", \"sm\", \"first\", context_mode),", "name": "isolated vs django modes.peakmem_render_sm_first", "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - small - first render (mem)", "type": "peakmemory", "unit": "bytes", "version": "c51b91fc583295776062822225e720b5ed71aef9c9288217c401c54283c62840"}, "isolated vs django modes.peakmem_render_sm_subsequent": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - small - second render (mem)\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n        setup=lambda context_mode: setup_templating_memory_benchmark(\n            \"django-components\",\n            \"sm\",\n            \"subsequent\",\n            context_mode,\n        ),\n    )\n    def peakmem_render_sm_subsequent(self, context_mode: DjcContextMode):\n        do_render()\n\nsetup=lambda context_mode: setup_templating_memory_benchmark(\n    \"django-components\",\n    \"sm\",\n    \"subsequent\",\n    context_mode,\n),", "name": "isolated vs django modes.peakmem_render_sm_subsequent", "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - small - second render (mem)", "type": "peakmemory", "unit": "bytes", "version": "54d747fb8f40179b7ff3d2fc49eb195909ad1c880b5ef7b82f82742b27b67260"}, "isolated vs django modes.timeraw_render_lg_first": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - large - first render\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_render_lg_first(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"lg\", \"first\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_render_lg_first", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - large - first render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "f94af83427c6346f88f8785a3cd2fc42415ac5a9fbbdb7de71d27e22e6a81699", "warmup_time": -1}, "isolated vs django modes.timeraw_render_lg_subsequent": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - large - second render\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_render_lg_subsequent(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"lg\", \"subsequent\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_render_lg_subsequent", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - large - second render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "9f7c2fde6b33f0451a1794ed903c48d96cd7822f67da502cec36fe8e977c2414", "warmup_time": -1}, "isolated vs django modes.timeraw_render_sm_first": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - small - first render\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_render_sm_first(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"sm\", \"first\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_render_sm_first", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - small - first render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "d15ca68909d7f1f43ff16863befb6f42681f17461417fc0069eefd6db3569296", "warmup_time": -1}, "isolated vs django modes.timeraw_render_sm_subsequent": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"render - small - second render\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_render_sm_subsequent(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"sm\", \"subsequent\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_render_sm_subsequent", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "render - small - second render", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "7444bc9516dd087e3f420349345eae991ad6941bbd22fce45265b18034b7cf77", "warmup_time": -1}, "isolated vs django modes.timeraw_startup_lg": {"code": "class IsolatedVsDjangoContextModesTests:\n    @benchmark(\n        pretty_name=\"startup - large\",\n        group_name=DJC_ISOLATED_VS_NON_GROUP,\n        number=1,\n        rounds=5,\n        params={\n            \"context_mode\": [\"isolated\", \"django\"],\n        },\n    )\n    def timeraw_startup_lg(self, context_mode: DjcContextMode):\n        return prepare_templating_benchmark(\"django-components\", \"lg\", \"startup\", context_mode)", "min_run_count": 2, "name": "isolated vs django modes.timeraw_startup_lg", "number": 1, "param_names": ["context_mode"], "params": [["'isolated'", "'django'"]], "pretty_name": "startup - large", "repeat": 0, "rounds": 5, "sample_time": 0.01, "type": "time", "unit": "seconds", "version": "eabe311ebee4a15c5816617be12f00ec30376f7506bd668219e1c50bc897c134", "warmup_time": -1}}, "machines": {"ci-linux": {"machine": "ci-linux", "version": 1}}, "tags": {"0.100": 1125, "0.101": 1132, "0.102": 1179, "0.110": 1252, "0.111": 1270, "0.112": 1277, "0.113": 1282, "0.114": 1287, "0.115": 1312, "0.116": 1328, "0.117": 1337, "0.118": 1352, "0.119": 1361, "0.120": 1366, "0.121": 1381, "0.122": 1387, "0.123": 1392, "0.124": 1447, "0.125": 1488, "0.126": 1505, "0.127": 1514, "0.128": 1546, "0.129": 1571, "0.130": 1591, "0.131": 1662, "0.16": 250, "0.17": 268, "0.26.2": 508, "0.27": 550, "0.27.1": 552, "0.27.2": 564, "0.28.0": 575, "0.28.1": 577, "0.67": 845, "0.68": 855, "0.70": 867, "0.71": 884, "0.72": 887, "0.73": 889, "0.74": 891, "0.75": 898, "0.76": 902, "0.77": 904, "0.78": 908, "0.79": 910, "0.80": 912, "0.81": 930, "0.82": 935, "0.83": 940, "0.84": 942, "0.85": 956, "0.86": 958, "0.87": 960, "0.88": 965, "0.89": 978, "0.90": 980, "0.91": 982, "0.92": 986, "0.93": 1056, "0.94": 1058, "0.95": 1060, "0.96": 1089, "0.97": 1098, "0.18": 343, "0.22": 388, "0.21": 380, "0.20": 369, "0.19": 359, "0.24": 457, "0.23": 427, "0.25": 487, "0.26": 500, "0.26.1": 503, "0.26.3": 536, "0.28.2": 598, "0.28.3": 612, "0.29": 622, "0.30": 646, "0.31": 651, "0.32": 663, "0.33": 675, "0.34": 681, "0.34.1": 691, "0.35": 704, "0.37": 724, "0.50": 729, "0.51": 742, "0.52": 748, "0.60": 752, "0.61": 757, "0.62": 773, "0.63": 775, "0.64": 779, "0.65": 787, "0.66": 806}, "pages": [["", "Grid view", "Display as a agrid"], ["summarylist", "List view", "Display as a list"], ["regressions", "Show regressions", "Display information about recent regressions"]]}
\ No newline at end of file
diff --git a/dev/benchmarks/info.json b/dev/benchmarks/info.json
index a707dbf2..5ec6f3d4 100644
--- a/dev/benchmarks/info.json
+++ b/dev/benchmarks/info.json
@@ -1,4 +1,4 @@
 {
     "asv-version": "0.6.4",
-    "timestamp": 1740214032970
+    "timestamp": 1742503708161
 }
\ No newline at end of file
diff --git a/dev/benchmarks/regressions.xml b/dev/benchmarks/regressions.xml
index 19490c4b..7c01a5ae 100644
--- a/dev/benchmarks/regressions.xml
+++ b/dev/benchmarks/regressions.xml
@@ -1,2 +1,2 @@
 <?xml version='1.0' encoding='utf-8'?>
-<feed xmlns="http://www.w3.org/2005/Atom"><id>tag:django-components.asv,1970-01-01:/cddbdcca8b398afd301fbfc73cc4d51103d4e3059c0e6b938d4c467ad3d1aa25</id><author><name>Airspeed Velocity</name></author><title xml:lang="en">django-components performance regressions</title><updated>2025-02-22T08:47:12Z</updated></feed>
\ No newline at end of file
+<feed xmlns="http://www.w3.org/2005/Atom"><id>tag:django-components.asv,1970-01-01:/cddbdcca8b398afd301fbfc73cc4d51103d4e3059c0e6b938d4c467ad3d1aa25</id><author><name>Airspeed Velocity</name></author><title xml:lang="en">django-components performance regressions</title><updated>2025-03-20T20:48:28Z</updated></feed>
\ No newline at end of file
diff --git a/dev/concepts/fundamentals/defining_js_css_html_files/index.html b/dev/concepts/fundamentals/defining_js_css_html_files/index.html
index af077635..5e636b8e 100644
--- a/dev/concepts/fundamentals/defining_js_css_html_files/index.html
+++ b/dev/concepts/fundamentals/defining_js_css_html_files/index.html
@@ -22,19 +22,21 @@
 <a id=__codelineno-2-7 name=__codelineno-2-7 href=#__codelineno-2-7></a>    <span class=n>js_file</span> <span class=o>=</span> <span class=s2>&quot;calendar/script.js&quot;</span>
 </code></pre></div> <div class="admonition important"> <p class=admonition-title>Important</p> <p><strong>File path resolution in-depth</strong></p> <p>At component class creation, django-components checks all file paths defined on the component (e.g. <code>Component.template_file</code>).</p> <p>For each file path, it checks if the file path is relative to the component's directory. And such file exists, the component's file path is re-written to be defined relative to a first matching directory in <a href=../../../reference/settings/#django_components.app_settings.ComponentsSettings.dirs><code>COMPONENTS.dirs</code></a> or <a href=../../../reference/settings/#django_components.app_settings.ComponentsSettings.app_dirs><code>COMPONENTS.app_dirs</code></a>.</p> <p><strong>Example:</strong></p> <div class=highlight><span class=filename>[root]/components/mytable/mytable.py</span><pre><span></span><code><a id=__codelineno-3-1 name=__codelineno-3-1 href=#__codelineno-3-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
 <a id=__codelineno-3-2 name=__codelineno-3-2 href=#__codelineno-3-2></a>    <span class=n>template_file</span> <span class=o>=</span> <span class=s2>&quot;mytable.html&quot;</span>
-</code></pre></div> <ol> <li>Component <code>MyTable</code> is defined in file <code>[root]/components/mytable/mytable.py</code>.</li> <li>The component's directory is thus <code>[root]/components/mytable/</code>.</li> <li>Because <code>MyTable.template_file</code> is <code>mytable.html</code>, django-components tries to resolve it as <code>[root]/components/mytable/mytable.html</code>.</li> <li>django-components checks the filesystem. If there's no such file, nothing happens.</li> <li>If there IS such file, django-components tries to rewrite the path.</li> <li>django-components searches <code>COMPONENTS.dirs</code> and <code>COMPONENTS.app_dirs</code> for a first directory that contains <code>[root]/components/mytable/mytable.html</code>.</li> <li>It comes across <code>[root]/components/</code>, which DOES contain the path to <code>mytable.html</code>.</li> <li>Thus, it rewrites <code>template_file</code> from <code>mytable.html</code> to <code>mytable/mytable.html</code>.</li> </ol> <p>NOTE: In case of ambiguity, the preference goes to resolving the files relative to the component's directory.</p> </div> <h2 id=defining-additional-js-and-css-files>Defining additional JS and CSS files<a class=headerlink href=#defining-additional-js-and-css-files title="Permanent link">¤</a></h2> <p>Each component can have only a single template, and single main JS and CSS. However, you can define additional JS or CSS using the nested <a href=../../../reference/api#django_components.Component.Media><code>Component.Media</code> class</a>.</p> <p>This <code>Media</code> class behaves similarly to <a href=https://docs.djangoproject.com/en/5.1/topics/forms/media/#assets-as-a-static-definition>Django's Media class</a>:</p> <ul> <li>Paths are generally handled as static file paths, and resolved URLs are rendered to HTML with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A path that starts with <code>http</code>, <code>https</code>, or <code>/</code> is considered a URL, skipping the static file resolution. This path is still rendered to HTML with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A <a href=https://docs.djangoproject.com/en/5.1/ref/utils/#django.utils.safestring.SafeString><code>SafeString</code></a>, or a function (with <code>__html__</code> method) is considered an already-formatted HTML tag, skipping both static file resolution and rendering with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>You can set <a href=../../../reference/api#django_components.ComponentMediaInput.extend><code>extend</code></a> to configure whether to inherit JS / CSS from parent components. See <a href=../../fundamentals/defining_js_css_html_files/#controlling-media-inheritance>Controlling Media Inheritance</a>.</li> </ul> <p>However, there's a few differences from Django's Media class:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list, or (CSS-only) a dictonary (See <a href=../../../reference/api#django_components.ComponentMediaInput><code>ComponentMediaInput</code></a>).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>, <a href=https://docs.djangoproject.com/en/5.1/ref/utils/#django.utils.safestring.SafeString><code>SafeString</code></a>, or a function (See <a href=../../../reference/api#django_components.ComponentMediaInputPath><code>ComponentMediaInputPath</code></a>).</li> </ol> <div class=highlight><pre><span></span><code><a id=__codelineno-4-1 name=__codelineno-4-1 href=#__codelineno-4-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
+</code></pre></div> <ol> <li>Component <code>MyTable</code> is defined in file <code>[root]/components/mytable/mytable.py</code>.</li> <li>The component's directory is thus <code>[root]/components/mytable/</code>.</li> <li>Because <code>MyTable.template_file</code> is <code>mytable.html</code>, django-components tries to resolve it as <code>[root]/components/mytable/mytable.html</code>.</li> <li>django-components checks the filesystem. If there's no such file, nothing happens.</li> <li>If there IS such file, django-components tries to rewrite the path.</li> <li>django-components searches <code>COMPONENTS.dirs</code> and <code>COMPONENTS.app_dirs</code> for a first directory that contains <code>[root]/components/mytable/mytable.html</code>.</li> <li>It comes across <code>[root]/components/</code>, which DOES contain the path to <code>mytable.html</code>.</li> <li>Thus, it rewrites <code>template_file</code> from <code>mytable.html</code> to <code>mytable/mytable.html</code>.</li> </ol> <p>NOTE: In case of ambiguity, the preference goes to resolving the files relative to the component's directory.</p> </div> <h2 id=defining-additional-js-and-css-files>Defining additional JS and CSS files<a class=headerlink href=#defining-additional-js-and-css-files title="Permanent link">¤</a></h2> <p>Each component can have only a single template, and single main JS and CSS. However, you can define additional JS or CSS using the nested <a href=../../../reference/api#django_components.Component.Media><code>Component.Media</code> class</a>.</p> <p>This <code>Media</code> class behaves similarly to <a href=https://docs.djangoproject.com/en/5.1/topics/forms/media/#assets-as-a-static-definition>Django's Media class</a>:</p> <ul> <li>Paths are generally handled as static file paths, and resolved URLs are rendered to HTML with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A path that starts with <code>http</code>, <code>https</code>, or <code>/</code> is considered a URL, skipping the static file resolution. This path is still rendered to HTML with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A <a href=https://docs.djangoproject.com/en/5.1/ref/utils/#django.utils.safestring.SafeString><code>SafeString</code></a>, or a function (with <code>__html__</code> method) is considered an already-formatted HTML tag, skipping both static file resolution and rendering with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>You can set <a href=../../../reference/api#django_components.ComponentMediaInput.extend><code>extend</code></a> to configure whether to inherit JS / CSS from parent components. See <a href=../../fundamentals/defining_js_css_html_files/#controlling-media-inheritance>Controlling Media Inheritance</a>.</li> </ul> <p>However, there's a few differences from Django's Media class:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list, or (CSS-only) a dictonary (See <a href=../../../reference/api#django_components.ComponentMediaInput><code>ComponentMediaInput</code></a>).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>, <a href=https://docs.djangoproject.com/en/5.1/ref/utils/#django.utils.safestring.SafeString><code>SafeString</code></a>, or a function (See <a href=../../../reference/api#django_components.ComponentMediaInputPath><code>ComponentMediaInputPath</code></a>).</li> <li>Individual JS / CSS files can be glob patterns, e.g. <code>*.js</code> or <code>styles/**/*.css</code>.</li> <li>If you set <a href=../../../reference/api/#django_components.ComponentMediaInput.extend><code>Media.extend</code></a> to a list, it should be a list of <a href=../../../reference/api/#django_components.Component><code>Component</code></a> classes.</li> </ol> <div class=highlight><pre><span></span><code><a id=__codelineno-4-1 name=__codelineno-4-1 href=#__codelineno-4-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
 <a id=__codelineno-4-2 name=__codelineno-4-2 href=#__codelineno-4-2></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
 <a id=__codelineno-4-3 name=__codelineno-4-3 href=#__codelineno-4-3></a>        <span class=n>js</span> <span class=o>=</span> <span class=p>[</span>
 <a id=__codelineno-4-4 name=__codelineno-4-4 href=#__codelineno-4-4></a>            <span class=s2>&quot;path/to/script.js&quot;</span><span class=p>,</span>
-<a id=__codelineno-4-5 name=__codelineno-4-5 href=#__codelineno-4-5></a>            <span class=s2>&quot;https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js&quot;</span><span class=p>,</span>  <span class=c1># AlpineJS</span>
-<a id=__codelineno-4-6 name=__codelineno-4-6 href=#__codelineno-4-6></a>        <span class=p>]</span>
-<a id=__codelineno-4-7 name=__codelineno-4-7 href=#__codelineno-4-7></a>        <span class=n>css</span> <span class=o>=</span> <span class=p>{</span>
-<a id=__codelineno-4-8 name=__codelineno-4-8 href=#__codelineno-4-8></a>            <span class=s2>&quot;all&quot;</span><span class=p>:</span> <span class=p>[</span>
-<a id=__codelineno-4-9 name=__codelineno-4-9 href=#__codelineno-4-9></a>                <span class=s2>&quot;path/to/style.css&quot;</span><span class=p>,</span>
-<a id=__codelineno-4-10 name=__codelineno-4-10 href=#__codelineno-4-10></a>                <span class=s2>&quot;https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css&quot;</span><span class=p>,</span>  <span class=c1># TailwindCSS</span>
-<a id=__codelineno-4-11 name=__codelineno-4-11 href=#__codelineno-4-11></a>            <span class=p>],</span>
-<a id=__codelineno-4-12 name=__codelineno-4-12 href=#__codelineno-4-12></a>            <span class=s2>&quot;print&quot;</span><span class=p>:</span> <span class=p>[</span><span class=s2>&quot;path/to/style2.css&quot;</span><span class=p>],</span>
-<a id=__codelineno-4-13 name=__codelineno-4-13 href=#__codelineno-4-13></a>        <span class=p>}</span>
+<a id=__codelineno-4-5 name=__codelineno-4-5 href=#__codelineno-4-5></a>            <span class=s2>&quot;path/to/*.js&quot;</span><span class=p>,</span>  <span class=c1># Or as a glob</span>
+<a id=__codelineno-4-6 name=__codelineno-4-6 href=#__codelineno-4-6></a>            <span class=s2>&quot;https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js&quot;</span><span class=p>,</span>  <span class=c1># AlpineJS</span>
+<a id=__codelineno-4-7 name=__codelineno-4-7 href=#__codelineno-4-7></a>        <span class=p>]</span>
+<a id=__codelineno-4-8 name=__codelineno-4-8 href=#__codelineno-4-8></a>        <span class=n>css</span> <span class=o>=</span> <span class=p>{</span>
+<a id=__codelineno-4-9 name=__codelineno-4-9 href=#__codelineno-4-9></a>            <span class=s2>&quot;all&quot;</span><span class=p>:</span> <span class=p>[</span>
+<a id=__codelineno-4-10 name=__codelineno-4-10 href=#__codelineno-4-10></a>                <span class=s2>&quot;path/to/style.css&quot;</span><span class=p>,</span>
+<a id=__codelineno-4-11 name=__codelineno-4-11 href=#__codelineno-4-11></a>                <span class=s2>&quot;path/to/*.css&quot;</span><span class=p>,</span>  <span class=c1># Or as a glob</span>
+<a id=__codelineno-4-12 name=__codelineno-4-12 href=#__codelineno-4-12></a>                <span class=s2>&quot;https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css&quot;</span><span class=p>,</span>  <span class=c1># TailwindCSS</span>
+<a id=__codelineno-4-13 name=__codelineno-4-13 href=#__codelineno-4-13></a>            <span class=p>],</span>
+<a id=__codelineno-4-14 name=__codelineno-4-14 href=#__codelineno-4-14></a>            <span class=s2>&quot;print&quot;</span><span class=p>:</span> <span class=p>[</span><span class=s2>&quot;path/to/style2.css&quot;</span><span class=p>],</span>
+<a id=__codelineno-4-15 name=__codelineno-4-15 href=#__codelineno-4-15></a>        <span class=p>}</span>
 </code></pre></div> <h2 id=configuring-css-media-types>Configuring CSS Media Types<a class=headerlink href=#configuring-css-media-types title="Permanent link">¤</a></h2> <p>You can define which stylesheets will be associated with which <a href=https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_media_queries/Using_media_queries#targeting_media_types>CSS Media types</a>. You do so by defining CSS files as a dictionary.</p> <p>See the corresponding <a href=https://docs.djangoproject.com/en/5.0/topics/forms/media/#css>Django Documentation</a>.</p> <p>Again, you can set either a single file or a list of files per media type:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-5-1 name=__codelineno-5-1 href=#__codelineno-5-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
 <a id=__codelineno-5-2 name=__codelineno-5-2 href=#__codelineno-5-2></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
 <a id=__codelineno-5-3 name=__codelineno-5-3 href=#__codelineno-5-3></a>        <span class=n>css</span> <span class=o>=</span> <span class=p>{</span>
@@ -198,4 +200,4 @@
 <a id=__codelineno-16-10 name=__codelineno-16-10 href=#__codelineno-16-10></a>        <span class=n>js</span> <span class=o>=</span> <span class=p>[</span><span class=s2>&quot;script.js&quot;</span><span class=p>]</span>
 <a id=__codelineno-16-11 name=__codelineno-16-11 href=#__codelineno-16-11></a>
 <a id=__codelineno-16-12 name=__codelineno-16-12 href=#__codelineno-16-12></a><span class=nb>print</span><span class=p>(</span><span class=n>MyComponent</span><span class=o>.</span><span class=n>media</span><span class=o>.</span><span class=n>_js</span><span class=p>)</span>  <span class=c1># [&quot;script.js&quot;, &quot;other1.js&quot;, &quot;other2.js&quot;]</span>
-</code></pre></div> <div class="admonition info"> <p class=admonition-title>Info</p> <p>The <code>extend</code> behaves consistently with <a href=https://docs.djangoproject.com/en/5.1/topics/forms/media/#extend>Django's Media class</a>, with one exception:</p> <ul> <li>When you set <code>extend</code> to a list, the list is expected to contain Component classes (or other classes that have a nested <code>Media</code> class).</li> </ul> </div> <aside class=md-source-file> <span class=md-source-file__fact> <span class=md-icon title="Last update"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg> </span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-timeago" title="February 23, 2025 21:44:12"><span class=timeago datetime=2025-02-23T21:44:12+00:00 locale=en></span></span><span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_date" title="February 23, 2025 21:44:12">2025-02-23</span> </span> <span class=md-source-file__fact> <span class=md-icon title=Contributors> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 4a4 4 0 0 1 4 4 4 4 0 0 1-4 4 4 4 0 0 1-4-4 4 4 0 0 1 4-4m0 10c4.42 0 8 1.79 8 4v2H4v-2c0-2.21 3.58-4 8-4"/></svg> </span> <nav> <a href=mailto:juraj.oravec.josefson@gmail.com>Juro Oravec</a> </nav> </span> </aside> </article> </div> <script>var tabs=__md_get("__tabs");if(Array.isArray(tabs))e:for(var set of document.querySelectorAll(".tabbed-set")){var labels=set.querySelector(".tabbed-labels");for(var tab of tabs)for(var label of labels.getElementsByTagName("label"))if(label.innerText.trim()===tab){var input=document.getElementById(label.htmlFor);input.checked=!0;continue e}}</script> <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script> </div> <button type=button class="md-top md-icon" data-md-component=top hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg> Back to top </button> </main> <footer class=md-footer> <nav class="md-footer__inner md-grid" aria-label=Footer> <a href=../html_attributes/ class="md-footer__link md-footer__link--prev" aria-label="Previous: HTML attributes"> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg> </div> <div class=md-footer__title> <span class=md-footer__direction> Previous </span> <div class=md-ellipsis> HTML attributes </div> </div> </a> <a href=../autodiscovery/ class="md-footer__link md-footer__link--next" aria-label="Next: Autodiscovery"> <div class=md-footer__title> <span class=md-footer__direction> Next </span> <div class=md-ellipsis> Autodiscovery </div> </div> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M4 11v2h12l-5.5 5.5 1.42 1.42L19.84 12l-7.92-7.92L10.5 5.5 16 11z"/></svg> </div> </a> </nav> <div class="md-footer-meta md-typeset"> <div class="md-footer-meta__inner md-grid"> <div class=md-copyright> Made with <a href=https://squidfunk.github.io/mkdocs-material/ target=_blank rel=noopener> Material for MkDocs </a> </div> <div class=md-social> <a href=https://github.com/django-components/django-components target=_blank rel=noopener title=github.com class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </a> <a href=https://pypi.org/project/django-components/ target=_blank rel=noopener title=pypi.org class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 448 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M439.8 200.5c-7.7-30.9-22.3-54.2-53.4-54.2h-40.1v47.4c0 36.8-31.2 67.8-66.8 67.8H172.7c-29.2 0-53.4 25-53.4 54.3v101.8c0 29 25.2 46 53.4 54.3 33.8 9.9 66.3 11.7 106.8 0 26.9-7.8 53.4-23.5 53.4-54.3v-40.7H226.2v-13.6h160.2c31.1 0 42.6-21.7 53.4-54.2 11.2-33.5 10.7-65.7 0-108.6M286.2 404c11.1 0 20.1 9.1 20.1 20.3 0 11.3-9 20.4-20.1 20.4-11 0-20.1-9.2-20.1-20.4.1-11.3 9.1-20.3 20.1-20.3M167.8 248.1h106.8c29.7 0 53.4-24.5 53.4-54.3V91.9c0-29-24.4-50.7-53.4-55.6-35.8-5.9-74.7-5.6-106.8.1-45.2 8-53.4 24.7-53.4 55.6v40.7h106.9v13.6h-147c-31.1 0-58.3 18.7-66.8 54.2-9.8 40.7-10.2 66.1 0 108.6 7.6 31.6 25.7 54.2 56.8 54.2H101v-48.8c0-35.3 30.5-66.4 66.8-66.4m-6.7-142.6c-11.1 0-20.1-9.1-20.1-20.3.1-11.3 9-20.4 20.1-20.4 11 0 20.1 9.2 20.1 20.4s-9 20.3-20.1 20.3"/></svg> </a> </div> </div> </div> </footer> </div> <div class=md-dialog data-md-component=dialog> <div class="md-dialog__inner md-typeset"></div> </div> <div class=md-progress data-md-component=progress role=progressbar></div> <script id=__config type=application/json>{"base": "../../..", "features": ["content.action.edit", "content.action.view", "content.code.annotate", "content.code.copy", "content.tabs.link", "navigation.expand", "navigation.footer", "navigation.instant", "navigation.instant.progress", "navigation.indexes", "navigation.sections", "navigation.tabs", "navigation.tracking", "navigation.top", "search.highlight", "search.share", "search.suggest", "toc.follow"], "search": "../../../assets/javascripts/workers/search.f8cc74c7.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"alias": true, "default": ["dev"], "provider": "mike"}}</script> <script src=../../../assets/javascripts/bundle.c8b220af.min.js></script> <script src=../../../assets/_markdown_exec_pyodide.js></script> <script src=../../../js/timeago.min.js></script> <script src=../../../js/timeago_mkdocs_material.js></script> </body> </html>
\ No newline at end of file
+</code></pre></div> <div class="admonition info"> <p class=admonition-title>Info</p> <p>The <code>extend</code> behaves consistently with <a href=https://docs.djangoproject.com/en/5.1/topics/forms/media/#extend>Django's Media class</a>, with one exception:</p> <ul> <li>When you set <code>extend</code> to a list, the list is expected to contain Component classes (or other classes that have a nested <code>Media</code> class).</li> </ul> </div> <aside class=md-source-file> <span class=md-source-file__fact> <span class=md-icon title="Last update"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg> </span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-timeago" title="March 21, 2025 09:23:38"><span class=timeago datetime=2025-03-21T09:23:38+00:00 locale=en></span></span><span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_date" title="March 21, 2025 09:23:38">2025-03-21</span> </span> <span class=md-source-file__fact> <span class=md-icon title=Contributors> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 4a4 4 0 0 1 4 4 4 4 0 0 1-4 4 4 4 0 0 1-4-4 4 4 0 0 1 4-4m0 10c4.42 0 8 1.79 8 4v2H4v-2c0-2.21 3.58-4 8-4"/></svg> </span> <nav> <a href=mailto:juraj.oravec.josefson@gmail.com>Juro Oravec</a> </nav> </span> </aside> </article> </div> <script>var tabs=__md_get("__tabs");if(Array.isArray(tabs))e:for(var set of document.querySelectorAll(".tabbed-set")){var labels=set.querySelector(".tabbed-labels");for(var tab of tabs)for(var label of labels.getElementsByTagName("label"))if(label.innerText.trim()===tab){var input=document.getElementById(label.htmlFor);input.checked=!0;continue e}}</script> <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script> </div> <button type=button class="md-top md-icon" data-md-component=top hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg> Back to top </button> </main> <footer class=md-footer> <nav class="md-footer__inner md-grid" aria-label=Footer> <a href=../html_attributes/ class="md-footer__link md-footer__link--prev" aria-label="Previous: HTML attributes"> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg> </div> <div class=md-footer__title> <span class=md-footer__direction> Previous </span> <div class=md-ellipsis> HTML attributes </div> </div> </a> <a href=../autodiscovery/ class="md-footer__link md-footer__link--next" aria-label="Next: Autodiscovery"> <div class=md-footer__title> <span class=md-footer__direction> Next </span> <div class=md-ellipsis> Autodiscovery </div> </div> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M4 11v2h12l-5.5 5.5 1.42 1.42L19.84 12l-7.92-7.92L10.5 5.5 16 11z"/></svg> </div> </a> </nav> <div class="md-footer-meta md-typeset"> <div class="md-footer-meta__inner md-grid"> <div class=md-copyright> Made with <a href=https://squidfunk.github.io/mkdocs-material/ target=_blank rel=noopener> Material for MkDocs </a> </div> <div class=md-social> <a href=https://github.com/django-components/django-components target=_blank rel=noopener title=github.com class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </a> <a href=https://pypi.org/project/django-components/ target=_blank rel=noopener title=pypi.org class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 448 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M439.8 200.5c-7.7-30.9-22.3-54.2-53.4-54.2h-40.1v47.4c0 36.8-31.2 67.8-66.8 67.8H172.7c-29.2 0-53.4 25-53.4 54.3v101.8c0 29 25.2 46 53.4 54.3 33.8 9.9 66.3 11.7 106.8 0 26.9-7.8 53.4-23.5 53.4-54.3v-40.7H226.2v-13.6h160.2c31.1 0 42.6-21.7 53.4-54.2 11.2-33.5 10.7-65.7 0-108.6M286.2 404c11.1 0 20.1 9.1 20.1 20.3 0 11.3-9 20.4-20.1 20.4-11 0-20.1-9.2-20.1-20.4.1-11.3 9.1-20.3 20.1-20.3M167.8 248.1h106.8c29.7 0 53.4-24.5 53.4-54.3V91.9c0-29-24.4-50.7-53.4-55.6-35.8-5.9-74.7-5.6-106.8.1-45.2 8-53.4 24.7-53.4 55.6v40.7h106.9v13.6h-147c-31.1 0-58.3 18.7-66.8 54.2-9.8 40.7-10.2 66.1 0 108.6 7.6 31.6 25.7 54.2 56.8 54.2H101v-48.8c0-35.3 30.5-66.4 66.8-66.4m-6.7-142.6c-11.1 0-20.1-9.1-20.1-20.3.1-11.3 9-20.4 20.1-20.4 11 0 20.1 9.2 20.1 20.4s-9 20.3-20.1 20.3"/></svg> </a> </div> </div> </div> </footer> </div> <div class=md-dialog data-md-component=dialog> <div class="md-dialog__inner md-typeset"></div> </div> <div class=md-progress data-md-component=progress role=progressbar></div> <script id=__config type=application/json>{"base": "../../..", "features": ["content.action.edit", "content.action.view", "content.code.annotate", "content.code.copy", "content.tabs.link", "navigation.expand", "navigation.footer", "navigation.instant", "navigation.instant.progress", "navigation.indexes", "navigation.sections", "navigation.tabs", "navigation.tracking", "navigation.top", "search.highlight", "search.share", "search.suggest", "toc.follow"], "search": "../../../assets/javascripts/workers/search.f8cc74c7.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"alias": true, "default": ["dev"], "provider": "mike"}}</script> <script src=../../../assets/javascripts/bundle.c8b220af.min.js></script> <script src=../../../assets/_markdown_exec_pyodide.js></script> <script src=../../../js/timeago.min.js></script> <script src=../../../js/timeago_mkdocs_material.js></script> </body> </html>
\ No newline at end of file
diff --git a/dev/getting_started/adding_js_and_css/index.html b/dev/getting_started/adding_js_and_css/index.html
index 14feb6b8..598fcf92 100644
--- a/dev/getting_started/adding_js_and_css/index.html
+++ b/dev/getting_started/adding_js_and_css/index.html
@@ -97,7 +97,7 @@
       a component is rendered on the page.
 
     This is not true for JS and CSS defined in `Media.js/css`, where the linked JS / CSS are rendered as is.
---> <h3 id=5-link-additional-js-and-css-to-a-component>5. Link additional JS and CSS to a component<a class=headerlink href=#5-link-additional-js-and-css-to-a-component title="Permanent link">¤</a></h3> <p>Your components may depend on third-party packages or styling, or other shared logic. To load these additional dependencies, you can use a nested <a href=../../reference/api#django_components.Component.Media><code>Media</code> class</a>.</p> <p>This <code>Media</code> class behaves similarly to <a href=https://docs.djangoproject.com/en/5.1/topics/forms/media/#assets-as-a-static-definition>Django's Media class</a>, with a few differences:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list, or (CSS-only) a dictonary (see below).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>, <a href=https://dev.to/doridoro/django-safestring-afj><code>SafeString</code></a>, or a function.</li> <li>If you set <code>Media.extend</code> to a list, it should be a list of <code>Component</code> classes.</li> </ol> <p><a href=../../concepts/fundamentals/defining_js_css_html_files>Learn more</a> about using Media.</p> <div class=highlight><span class=filename>[project root]/components/calendar/calendar.py</span><pre><span></span><code><a id=__codelineno-8-1 name=__codelineno-8-1 href=#__codelineno-8-1></a><span class=kn>from</span><span class=w> </span><span class=nn>django_components</span><span class=w> </span><span class=kn>import</span> <span class=n>Component</span>
+--> <h3 id=5-link-additional-js-and-css-to-a-component>5. Link additional JS and CSS to a component<a class=headerlink href=#5-link-additional-js-and-css-to-a-component title="Permanent link">¤</a></h3> <p>Your components may depend on third-party packages or styling, or other shared logic. To load these additional dependencies, you can use a nested <a href=../../reference/api#django_components.Component.Media><code>Media</code> class</a>.</p> <p>This <code>Media</code> class behaves similarly to <a href=https://docs.djangoproject.com/en/5.1/topics/forms/media/#assets-as-a-static-definition>Django's Media class</a>, with a few differences:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list, or (CSS-only) a dictonary (see below).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>, <a href=https://dev.to/doridoro/django-safestring-afj><code>SafeString</code></a>, or a function.</li> <li>Individual JS / CSS files can be glob patterns, e.g. <code>*.js</code> or <code>styles/**/*.css</code>.</li> <li>If you set <a href=../../reference/api/#django_components.ComponentMediaInput.extend><code>Media.extend</code></a> to a list, it should be a list of <a href=../../reference/api/#django_components.Component><code>Component</code></a> classes.</li> </ol> <p><a href=../../concepts/fundamentals/defining_js_css_html_files>Learn more</a> about using Media.</p> <div class=highlight><span class=filename>[project root]/components/calendar/calendar.py</span><pre><span></span><code><a id=__codelineno-8-1 name=__codelineno-8-1 href=#__codelineno-8-1></a><span class=kn>from</span><span class=w> </span><span class=nn>django_components</span><span class=w> </span><span class=kn>import</span> <span class=n>Component</span>
 <a id=__codelineno-8-2 name=__codelineno-8-2 href=#__codelineno-8-2></a>
 <a id=__codelineno-8-3 name=__codelineno-8-3 href=#__codelineno-8-3></a><span class=k>class</span><span class=w> </span><span class=nc>Calendar</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
 <a id=__codelineno-8-4 name=__codelineno-8-4 href=#__codelineno-8-4></a>    <span class=n>template_file</span> <span class=o>=</span> <span class=s2>&quot;calendar.html&quot;</span>
@@ -107,17 +107,19 @@
 <a id=__codelineno-8-8 name=__codelineno-8-8 href=#__codelineno-8-8></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>   <span class=c1># &lt;--- new</span>
 <a id=__codelineno-8-9 name=__codelineno-8-9 href=#__codelineno-8-9></a>        <span class=n>js</span> <span class=o>=</span> <span class=p>[</span>
 <a id=__codelineno-8-10 name=__codelineno-8-10 href=#__codelineno-8-10></a>            <span class=s2>&quot;path/to/shared.js&quot;</span><span class=p>,</span>
-<a id=__codelineno-8-11 name=__codelineno-8-11 href=#__codelineno-8-11></a>            <span class=s2>&quot;https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js&quot;</span><span class=p>,</span>  <span class=c1># AlpineJS</span>
-<a id=__codelineno-8-12 name=__codelineno-8-12 href=#__codelineno-8-12></a>        <span class=p>]</span>
-<a id=__codelineno-8-13 name=__codelineno-8-13 href=#__codelineno-8-13></a>        <span class=n>css</span> <span class=o>=</span> <span class=p>[</span>
-<a id=__codelineno-8-14 name=__codelineno-8-14 href=#__codelineno-8-14></a>            <span class=s2>&quot;path/to/shared.css&quot;</span><span class=p>,</span>
-<a id=__codelineno-8-15 name=__codelineno-8-15 href=#__codelineno-8-15></a>            <span class=s2>&quot;https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css&quot;</span><span class=p>,</span>  <span class=c1># Tailwind</span>
-<a id=__codelineno-8-16 name=__codelineno-8-16 href=#__codelineno-8-16></a>        <span class=p>]</span>
-<a id=__codelineno-8-17 name=__codelineno-8-17 href=#__codelineno-8-17></a>
-<a id=__codelineno-8-18 name=__codelineno-8-18 href=#__codelineno-8-18></a>    <span class=k>def</span><span class=w> </span><span class=nf>get_context_data</span><span class=p>(</span><span class=bp>self</span><span class=p>):</span>
-<a id=__codelineno-8-19 name=__codelineno-8-19 href=#__codelineno-8-19></a>        <span class=k>return</span> <span class=p>{</span>
-<a id=__codelineno-8-20 name=__codelineno-8-20 href=#__codelineno-8-20></a>            <span class=s2>&quot;date&quot;</span><span class=p>:</span> <span class=s2>&quot;1970-01-01&quot;</span><span class=p>,</span>
-<a id=__codelineno-8-21 name=__codelineno-8-21 href=#__codelineno-8-21></a>        <span class=p>}</span>
+<a id=__codelineno-8-11 name=__codelineno-8-11 href=#__codelineno-8-11></a>            <span class=s2>&quot;path/to/*.js&quot;</span><span class=p>,</span>  <span class=c1># Or as a glob</span>
+<a id=__codelineno-8-12 name=__codelineno-8-12 href=#__codelineno-8-12></a>            <span class=s2>&quot;https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js&quot;</span><span class=p>,</span>  <span class=c1># AlpineJS</span>
+<a id=__codelineno-8-13 name=__codelineno-8-13 href=#__codelineno-8-13></a>        <span class=p>]</span>
+<a id=__codelineno-8-14 name=__codelineno-8-14 href=#__codelineno-8-14></a>        <span class=n>css</span> <span class=o>=</span> <span class=p>[</span>
+<a id=__codelineno-8-15 name=__codelineno-8-15 href=#__codelineno-8-15></a>            <span class=s2>&quot;path/to/shared.css&quot;</span><span class=p>,</span>
+<a id=__codelineno-8-16 name=__codelineno-8-16 href=#__codelineno-8-16></a>            <span class=s2>&quot;path/to/*.css&quot;</span><span class=p>,</span>  <span class=c1># Or as a glob</span>
+<a id=__codelineno-8-17 name=__codelineno-8-17 href=#__codelineno-8-17></a>            <span class=s2>&quot;https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css&quot;</span><span class=p>,</span>  <span class=c1># Tailwind</span>
+<a id=__codelineno-8-18 name=__codelineno-8-18 href=#__codelineno-8-18></a>        <span class=p>]</span>
+<a id=__codelineno-8-19 name=__codelineno-8-19 href=#__codelineno-8-19></a>
+<a id=__codelineno-8-20 name=__codelineno-8-20 href=#__codelineno-8-20></a>    <span class=k>def</span><span class=w> </span><span class=nf>get_context_data</span><span class=p>(</span><span class=bp>self</span><span class=p>):</span>
+<a id=__codelineno-8-21 name=__codelineno-8-21 href=#__codelineno-8-21></a>        <span class=k>return</span> <span class=p>{</span>
+<a id=__codelineno-8-22 name=__codelineno-8-22 href=#__codelineno-8-22></a>            <span class=s2>&quot;date&quot;</span><span class=p>:</span> <span class=s2>&quot;1970-01-01&quot;</span><span class=p>,</span>
+<a id=__codelineno-8-23 name=__codelineno-8-23 href=#__codelineno-8-23></a>        <span class=p>}</span>
 </code></pre></div> <div class="admonition note"> <p class=admonition-title>Note</p> <p>Same as with the "primary" JS and CSS, the file paths files can be either:</p> <ol> <li>Relative to the Python component file (as seen above),</li> <li>Relative to any of the component directories as defined by <a href=../../reference/settings#django_components.app_settings.ComponentsSettings.dirs><code>COMPONENTS.dirs</code></a> and/or <a href=../../reference/settings#django_components.app_settings.ComponentsSettings.app_dirs><code>COMPONENTS.app_dirs</code></a> (e.g. <code>[your apps]/components</code> dir and <code>[project root]/components</code>)</li> </ol> </div> <div class="admonition info"> <p class=admonition-title>Info</p> <p>The <code>Media</code> nested class is shaped based on <a href=https://docs.djangoproject.com/en/5.1/topics/forms/media/ >Django's Media class</a>.</p> <p>As such, django-components allows multiple formats to define the nested Media class:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-9-1 name=__codelineno-9-1 href=#__codelineno-9-1></a><span class=c1># Single files</span>
 <a id=__codelineno-9-2 name=__codelineno-9-2 href=#__codelineno-9-2></a><span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
 <a id=__codelineno-9-3 name=__codelineno-9-3 href=#__codelineno-9-3></a>    <span class=n>js</span> <span class=o>=</span> <span class=s2>&quot;calendar.js&quot;</span>
@@ -170,4 +172,4 @@
 <a id=__codelineno-10-34 name=__codelineno-10-34 href=#__codelineno-10-34></a><span class=w>    </span><span class=p>&lt;/</span><span class=nt>script</span><span class=p>&gt;</span>
 <a id=__codelineno-10-35 name=__codelineno-10-35 href=#__codelineno-10-35></a>  <span class=p>&lt;/</span><span class=nt>body</span><span class=p>&gt;</span>
 <a id=__codelineno-10-36 name=__codelineno-10-36 href=#__codelineno-10-36></a><span class=p>&lt;/</span><span class=nt>html</span><span class=p>&gt;</span>
-</code></pre></div> <hr> <p>Now that we have a fully-defined component, <a href=../components_in_templates/ >next let's use it in a Django template ➡️</a>.</p> <aside class=md-source-file> <span class=md-source-file__fact> <span class=md-icon title="Last update"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg> </span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-timeago" title="March 17, 2025 07:55:42"><span class=timeago datetime=2025-03-17T07:55:42+00:00 locale=en></span></span><span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_date" title="March 17, 2025 07:55:42">2025-03-17</span> </span> <span class=md-source-file__fact> <span class=md-icon title=Contributors> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 4a4 4 0 0 1 4 4 4 4 0 0 1-4 4 4 4 0 0 1-4-4 4 4 0 0 1 4-4m0 10c4.42 0 8 1.79 8 4v2H4v-2c0-2.21 3.58-4 8-4"/></svg> </span> <nav> <a href=mailto:juraj.oravec.josefson@gmail.com>Juro Oravec</a> </nav> </span> </aside> </article> </div> <script>var tabs=__md_get("__tabs");if(Array.isArray(tabs))e:for(var set of document.querySelectorAll(".tabbed-set")){var labels=set.querySelector(".tabbed-labels");for(var tab of tabs)for(var label of labels.getElementsByTagName("label"))if(label.innerText.trim()===tab){var input=document.getElementById(label.htmlFor);input.checked=!0;continue e}}</script> <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script> </div> <button type=button class="md-top md-icon" data-md-component=top hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg> Back to top </button> </main> <footer class=md-footer> <nav class="md-footer__inner md-grid" aria-label=Footer> <a href=../your_first_component/ class="md-footer__link md-footer__link--prev" aria-label="Previous: Create your first component"> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg> </div> <div class=md-footer__title> <span class=md-footer__direction> Previous </span> <div class=md-ellipsis> Create your first component </div> </div> </a> <a href=../components_in_templates/ class="md-footer__link md-footer__link--next" aria-label="Next: Components in templates"> <div class=md-footer__title> <span class=md-footer__direction> Next </span> <div class=md-ellipsis> Components in templates </div> </div> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M4 11v2h12l-5.5 5.5 1.42 1.42L19.84 12l-7.92-7.92L10.5 5.5 16 11z"/></svg> </div> </a> </nav> <div class="md-footer-meta md-typeset"> <div class="md-footer-meta__inner md-grid"> <div class=md-copyright> Made with <a href=https://squidfunk.github.io/mkdocs-material/ target=_blank rel=noopener> Material for MkDocs </a> </div> <div class=md-social> <a href=https://github.com/django-components/django-components target=_blank rel=noopener title=github.com class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </a> <a href=https://pypi.org/project/django-components/ target=_blank rel=noopener title=pypi.org class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 448 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M439.8 200.5c-7.7-30.9-22.3-54.2-53.4-54.2h-40.1v47.4c0 36.8-31.2 67.8-66.8 67.8H172.7c-29.2 0-53.4 25-53.4 54.3v101.8c0 29 25.2 46 53.4 54.3 33.8 9.9 66.3 11.7 106.8 0 26.9-7.8 53.4-23.5 53.4-54.3v-40.7H226.2v-13.6h160.2c31.1 0 42.6-21.7 53.4-54.2 11.2-33.5 10.7-65.7 0-108.6M286.2 404c11.1 0 20.1 9.1 20.1 20.3 0 11.3-9 20.4-20.1 20.4-11 0-20.1-9.2-20.1-20.4.1-11.3 9.1-20.3 20.1-20.3M167.8 248.1h106.8c29.7 0 53.4-24.5 53.4-54.3V91.9c0-29-24.4-50.7-53.4-55.6-35.8-5.9-74.7-5.6-106.8.1-45.2 8-53.4 24.7-53.4 55.6v40.7h106.9v13.6h-147c-31.1 0-58.3 18.7-66.8 54.2-9.8 40.7-10.2 66.1 0 108.6 7.6 31.6 25.7 54.2 56.8 54.2H101v-48.8c0-35.3 30.5-66.4 66.8-66.4m-6.7-142.6c-11.1 0-20.1-9.1-20.1-20.3.1-11.3 9-20.4 20.1-20.4 11 0 20.1 9.2 20.1 20.4s-9 20.3-20.1 20.3"/></svg> </a> </div> </div> </div> </footer> </div> <div class=md-dialog data-md-component=dialog> <div class="md-dialog__inner md-typeset"></div> </div> <div class=md-progress data-md-component=progress role=progressbar></div> <script id=__config type=application/json>{"base": "../..", "features": ["content.action.edit", "content.action.view", "content.code.annotate", "content.code.copy", "content.tabs.link", "navigation.expand", "navigation.footer", "navigation.instant", "navigation.instant.progress", "navigation.indexes", "navigation.sections", "navigation.tabs", "navigation.tracking", "navigation.top", "search.highlight", "search.share", "search.suggest", "toc.follow"], "search": "../../assets/javascripts/workers/search.f8cc74c7.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"alias": true, "default": ["dev"], "provider": "mike"}}</script> <script src=../../assets/javascripts/bundle.c8b220af.min.js></script> <script src=../../assets/_markdown_exec_pyodide.js></script> <script src=../../js/timeago.min.js></script> <script src=../../js/timeago_mkdocs_material.js></script> </body> </html>
\ No newline at end of file
+</code></pre></div> <hr> <p>Now that we have a fully-defined component, <a href=../components_in_templates/ >next let's use it in a Django template ➡️</a>.</p> <aside class=md-source-file> <span class=md-source-file__fact> <span class=md-icon title="Last update"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg> </span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-timeago" title="March 21, 2025 09:23:38"><span class=timeago datetime=2025-03-21T09:23:38+00:00 locale=en></span></span><span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_date" title="March 21, 2025 09:23:38">2025-03-21</span> </span> <span class=md-source-file__fact> <span class=md-icon title=Contributors> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 4a4 4 0 0 1 4 4 4 4 0 0 1-4 4 4 4 0 0 1-4-4 4 4 0 0 1 4-4m0 10c4.42 0 8 1.79 8 4v2H4v-2c0-2.21 3.58-4 8-4"/></svg> </span> <nav> <a href=mailto:juraj.oravec.josefson@gmail.com>Juro Oravec</a> </nav> </span> </aside> </article> </div> <script>var tabs=__md_get("__tabs");if(Array.isArray(tabs))e:for(var set of document.querySelectorAll(".tabbed-set")){var labels=set.querySelector(".tabbed-labels");for(var tab of tabs)for(var label of labels.getElementsByTagName("label"))if(label.innerText.trim()===tab){var input=document.getElementById(label.htmlFor);input.checked=!0;continue e}}</script> <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script> </div> <button type=button class="md-top md-icon" data-md-component=top hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg> Back to top </button> </main> <footer class=md-footer> <nav class="md-footer__inner md-grid" aria-label=Footer> <a href=../your_first_component/ class="md-footer__link md-footer__link--prev" aria-label="Previous: Create your first component"> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg> </div> <div class=md-footer__title> <span class=md-footer__direction> Previous </span> <div class=md-ellipsis> Create your first component </div> </div> </a> <a href=../components_in_templates/ class="md-footer__link md-footer__link--next" aria-label="Next: Components in templates"> <div class=md-footer__title> <span class=md-footer__direction> Next </span> <div class=md-ellipsis> Components in templates </div> </div> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M4 11v2h12l-5.5 5.5 1.42 1.42L19.84 12l-7.92-7.92L10.5 5.5 16 11z"/></svg> </div> </a> </nav> <div class="md-footer-meta md-typeset"> <div class="md-footer-meta__inner md-grid"> <div class=md-copyright> Made with <a href=https://squidfunk.github.io/mkdocs-material/ target=_blank rel=noopener> Material for MkDocs </a> </div> <div class=md-social> <a href=https://github.com/django-components/django-components target=_blank rel=noopener title=github.com class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </a> <a href=https://pypi.org/project/django-components/ target=_blank rel=noopener title=pypi.org class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 448 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M439.8 200.5c-7.7-30.9-22.3-54.2-53.4-54.2h-40.1v47.4c0 36.8-31.2 67.8-66.8 67.8H172.7c-29.2 0-53.4 25-53.4 54.3v101.8c0 29 25.2 46 53.4 54.3 33.8 9.9 66.3 11.7 106.8 0 26.9-7.8 53.4-23.5 53.4-54.3v-40.7H226.2v-13.6h160.2c31.1 0 42.6-21.7 53.4-54.2 11.2-33.5 10.7-65.7 0-108.6M286.2 404c11.1 0 20.1 9.1 20.1 20.3 0 11.3-9 20.4-20.1 20.4-11 0-20.1-9.2-20.1-20.4.1-11.3 9.1-20.3 20.1-20.3M167.8 248.1h106.8c29.7 0 53.4-24.5 53.4-54.3V91.9c0-29-24.4-50.7-53.4-55.6-35.8-5.9-74.7-5.6-106.8.1-45.2 8-53.4 24.7-53.4 55.6v40.7h106.9v13.6h-147c-31.1 0-58.3 18.7-66.8 54.2-9.8 40.7-10.2 66.1 0 108.6 7.6 31.6 25.7 54.2 56.8 54.2H101v-48.8c0-35.3 30.5-66.4 66.8-66.4m-6.7-142.6c-11.1 0-20.1-9.1-20.1-20.3.1-11.3 9-20.4 20.1-20.4 11 0 20.1 9.2 20.1 20.4s-9 20.3-20.1 20.3"/></svg> </a> </div> </div> </div> </footer> </div> <div class=md-dialog data-md-component=dialog> <div class="md-dialog__inner md-typeset"></div> </div> <div class=md-progress data-md-component=progress role=progressbar></div> <script id=__config type=application/json>{"base": "../..", "features": ["content.action.edit", "content.action.view", "content.code.annotate", "content.code.copy", "content.tabs.link", "navigation.expand", "navigation.footer", "navigation.instant", "navigation.instant.progress", "navigation.indexes", "navigation.sections", "navigation.tabs", "navigation.tracking", "navigation.top", "search.highlight", "search.share", "search.suggest", "toc.follow"], "search": "../../assets/javascripts/workers/search.f8cc74c7.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"alias": true, "default": ["dev"], "provider": "mike"}}</script> <script src=../../assets/javascripts/bundle.c8b220af.min.js></script> <script src=../../assets/_markdown_exec_pyodide.js></script> <script src=../../js/timeago.min.js></script> <script src=../../js/timeago_mkdocs_material.js></script> </body> </html>
\ No newline at end of file
diff --git a/dev/reference/api/index.html b/dev/reference/api/index.html
index 3d794dab..dc580336 100644
--- a/dev/reference/api/index.html
+++ b/dev/reference/api/index.html
@@ -1041,7 +1041,7 @@
       instance-attribute
    (django_components.ComponentFileEntry.filepath)" href=#django_components.ComponentFileEntry.filepath>filepath</a></code></b> (<code><a class="autorefs autorefs-external" title=pathlib.Path href=https://docs.python.org/3.12/library/pathlib.html#pathlib.Path>Path</a></code>) – <div class=doc-md-description> </div> </li> </ul> <div class="doc doc-children"> <div class="doc doc-object doc-attribute"> <h3 id=django_components.ComponentFileEntry.dot_path class="doc doc-heading"> <code class="doc-symbol doc-symbol-heading doc-symbol-attribute"></code> <span class="doc doc-object-name doc-attribute-name">dot_path</span> <span class="doc doc-labels"> <small class="doc doc-label doc-label-instance-attribute"><code>instance-attribute</code></small> </span> <a href=#django_components.ComponentFileEntry.dot_path class=headerlink title="Permanent link">¤</a></h3> <div class="doc-signature highlight"><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=n>dot_path</span><span class=p>:</span> <span class=n><a class="autorefs autorefs-external" href=https://docs.python.org/3.12/library/stdtypes.html#str>str</a></span>
 </code></pre></div> <div class="doc doc-contents "> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/util/loader.py#L116 target=_blank>See source code</a></p> <p>The python import path for the module. E.g. <code>app.components.mycomp</code></p> </div> </div> <div class="doc doc-object doc-attribute"> <h3 id=django_components.ComponentFileEntry.filepath class="doc doc-heading"> <code class="doc-symbol doc-symbol-heading doc-symbol-attribute"></code> <span class="doc doc-object-name doc-attribute-name">filepath</span> <span class="doc doc-labels"> <small class="doc doc-label doc-label-instance-attribute"><code>instance-attribute</code></small> </span> <a href=#django_components.ComponentFileEntry.filepath class=headerlink title="Permanent link">¤</a></h3> <div class="doc-signature highlight"><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=n>filepath</span><span class=p>:</span> <span class=n><a class="autorefs autorefs-external" title=pathlib.Path href=https://docs.python.org/3.12/library/pathlib.html#pathlib.Path>Path</a></span>
-</code></pre></div> <div class="doc doc-contents "> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/util/loader.py#L118 target=_blank>See source code</a></p> <p>The filesystem path to the module. E.g. <code>/path/to/project/app/components/mycomp.py</code></p> </div> </div> </div> </div> </div> <div class="doc doc-object doc-class"> <h2 id=django_components.ComponentMediaInput class="doc doc-heading"> <code class="doc-symbol doc-symbol-heading doc-symbol-class"></code> <span class="doc doc-object-name doc-class-name">ComponentMediaInput</span> <a href=#django_components.ComponentMediaInput class=headerlink title="Permanent link">¤</a></h2> <div class="doc doc-contents first"> <p class="doc doc-class-bases">Bases: <code>typing.Protocol</code></p> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L70 target=_blank>See source code</a></p> <p>Defines JS and CSS media files associated with a <a href=../api#django_components.Component><code>Component</code></a>.</p> <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
+</code></pre></div> <div class="doc doc-contents "> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/util/loader.py#L118 target=_blank>See source code</a></p> <p>The filesystem path to the module. E.g. <code>/path/to/project/app/components/mycomp.py</code></p> </div> </div> </div> </div> </div> <div class="doc doc-object doc-class"> <h2 id=django_components.ComponentMediaInput class="doc doc-heading"> <code class="doc-symbol doc-symbol-heading doc-symbol-class"></code> <span class="doc doc-object-name doc-class-name">ComponentMediaInput</span> <a href=#django_components.ComponentMediaInput class=headerlink title="Permanent link">¤</a></h2> <div class="doc doc-contents first"> <p class="doc doc-class-bases">Bases: <code>typing.Protocol</code></p> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L86 target=_blank>See source code</a></p> <p>Defines JS and CSS media files associated with a <a href=../api#django_components.Component><code>Component</code></a>.</p> <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
 <a id=__codelineno-0-2 name=__codelineno-0-2 href=#__codelineno-0-2></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
 <a id=__codelineno-0-3 name=__codelineno-0-3 href=#__codelineno-0-3></a>        <span class=n>js</span> <span class=o>=</span> <span class=p>[</span>
 <a id=__codelineno-0-4 name=__codelineno-0-4 href=#__codelineno-0-4></a>            <span class=s2>&quot;path/to/script.js&quot;</span><span class=p>,</span>
@@ -1127,7 +1127,7 @@
    (django_components.component_media.ComponentMediaInputPath)" href=#django_components.ComponentMediaInputPath>ComponentMediaInputPath</a></span><span class=p>]]</span>
 <a id=__codelineno-0-4 name=__codelineno-0-4 href=#__codelineno-0-4></a>    <span class=p>]</span>
 <a id=__codelineno-0-5 name=__codelineno-0-5 href=#__codelineno-0-5></a><span class=p>]</span> <span class=o>=</span> <span class=kc>None</span>
-</code></pre></div> <div class="doc doc-contents "> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L91 target=_blank>See source code</a></p> <p>CSS files associated with a <a href=../api#django_components.Component><code>Component</code></a>.</p> <ul> <li> <p>If a string, it's assumed to be a path to a CSS file.</p> </li> <li> <p>If a list, each entry is assumed to be a path to a CSS file.</p> </li> <li> <p>If a dict, the keys are media types (e.g. "all", "print", "screen", etc.), and the values are either:</p> <ul> <li>A string, assumed to be a path to a CSS file.</li> <li>A list, each entry is assumed to be a path to a CSS file.</li> </ul> </li> </ul> <p>Each entry can be a string, bytes, SafeString, PathLike, or a callable that returns one of the former (see <a href=../api#django_components.ComponentMediaInputPath><code>ComponentMediaInputPath</code></a>).</p> <p>Examples: <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
+</code></pre></div> <div class="doc doc-contents "> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L107 target=_blank>See source code</a></p> <p>CSS files associated with a <a href=../api#django_components.Component><code>Component</code></a>.</p> <ul> <li> <p>If a string, it's assumed to be a path to a CSS file.</p> </li> <li> <p>If a list, each entry is assumed to be a path to a CSS file.</p> </li> <li> <p>If a dict, the keys are media types (e.g. "all", "print", "screen", etc.), and the values are either:</p> <ul> <li>A string, assumed to be a path to a CSS file.</li> <li>A list, each entry is assumed to be a path to a CSS file.</li> </ul> </li> </ul> <p>Each entry can be a string, bytes, SafeString, PathLike, or a callable that returns one of the former (see <a href=../api#django_components.ComponentMediaInputPath><code>ComponentMediaInputPath</code></a>).</p> <p>Examples: <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
 <a id=__codelineno-0-2 name=__codelineno-0-2 href=#__codelineno-0-2></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
 <a id=__codelineno-0-3 name=__codelineno-0-3 href=#__codelineno-0-3></a>        <span class=n>css</span> <span class=o>=</span> <span class=s2>&quot;path/to/style.css&quot;</span>
 </code></pre></div></p> <div class=highlight><pre><span></span><code><a id=__codelineno-1-1 name=__codelineno-1-1 href=#__codelineno-1-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
@@ -1146,7 +1146,7 @@
 <a id=__codelineno-3-5 name=__codelineno-3-5 href=#__codelineno-3-5></a>            <span class=s2>&quot;print&quot;</span><span class=p>:</span> <span class=s2>&quot;path/to/print.css&quot;</span><span class=p>,</span>
 <a id=__codelineno-3-6 name=__codelineno-3-6 href=#__codelineno-3-6></a>        <span class=p>}</span>
 </code></pre></div> </div> </div> <div class="doc doc-object doc-attribute"> <h3 id=django_components.ComponentMediaInput.extend class="doc doc-heading"> <code class="doc-symbol doc-symbol-heading doc-symbol-attribute"></code> <span class="doc doc-object-name doc-attribute-name">extend</span> <span class="doc doc-labels"> <small class="doc doc-label doc-label-class-attribute"><code>class-attribute</code></small> <small class="doc doc-label doc-label-instance-attribute"><code>instance-attribute</code></small> </span> <a href=#django_components.ComponentMediaInput.extend class=headerlink title="Permanent link">¤</a></h3> <div class="doc-signature highlight"><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=n>extend</span><span class=p>:</span> <span class=n><a class="autorefs autorefs-external" title=typing.Union href=https://docs.python.org/3.12/library/typing.html#typing.Union>Union</a></span><span class=p>[</span><span class=n><a class="autorefs autorefs-external" href=https://docs.python.org/3.12/library/functions.html#bool>bool</a></span><span class=p>,</span> <span class=n><a class="autorefs autorefs-external" title=typing.List href=https://docs.python.org/3.12/library/typing.html#typing.List>List</a></span><span class=p>[</span><span class=n><a class="autorefs autorefs-external" title=typing.Type href=https://docs.python.org/3.12/library/typing.html#typing.Type>Type</a></span><span class=p>[</span><span class=n><a class="autorefs autorefs-internal" title="            Component (django_components.component.Component)" href=#django_components.Component>Component</a></span><span class=p>]]]</span> <span class=o>=</span> <span class=kc>True</span>
-</code></pre></div> <div class="doc doc-contents "> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L176 target=_blank>See source code</a></p> <p>Configures whether the component should inherit the media files from the parent component.</p> <ul> <li>If <code>True</code>, the component inherits the media files from the parent component.</li> <li>If <code>False</code>, the component does not inherit the media files from the parent component.</li> <li>If a list of components classes, the component inherits the media files ONLY from these specified components.</li> </ul> <p>Read more in <a href=../../concepts/fundamentals/defining_js_css_html_files/#controlling-media-inheritance>Controlling Media Inheritance</a> section.</p> <p><strong>Example:</strong></p> <p>Disable media inheritance:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>ParentComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
+</code></pre></div> <div class="doc doc-contents "> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L192 target=_blank>See source code</a></p> <p>Configures whether the component should inherit the media files from the parent component.</p> <ul> <li>If <code>True</code>, the component inherits the media files from the parent component.</li> <li>If <code>False</code>, the component does not inherit the media files from the parent component.</li> <li>If a list of components classes, the component inherits the media files ONLY from these specified components.</li> </ul> <p>Read more in <a href=../../concepts/fundamentals/defining_js_css_html_files/#controlling-media-inheritance>Controlling Media Inheritance</a> section.</p> <p><strong>Example:</strong></p> <p>Disable media inheritance:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>ParentComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
 <a id=__codelineno-0-2 name=__codelineno-0-2 href=#__codelineno-0-2></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
 <a id=__codelineno-0-3 name=__codelineno-0-3 href=#__codelineno-0-3></a>        <span class=n>js</span> <span class=o>=</span> <span class=p>[</span><span class=s2>&quot;parent.js&quot;</span><span class=p>]</span>
 <a id=__codelineno-0-4 name=__codelineno-0-4 href=#__codelineno-0-4></a>
@@ -1179,7 +1179,7 @@
   
       module-attribute
    (django_components.component_media.ComponentMediaInputPath)" href=#django_components.ComponentMediaInputPath>ComponentMediaInputPath</a></span><span class=p>]]]</span> <span class=o>=</span> <span class=kc>None</span>
-</code></pre></div> <div class="doc doc-contents "> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L145 target=_blank>See source code</a></p> <p>JS files associated with a <a href=../api#django_components.Component><code>Component</code></a>.</p> <ul> <li> <p>If a string, it's assumed to be a path to a JS file.</p> </li> <li> <p>If a list, each entry is assumed to be a path to a JS file.</p> </li> </ul> <p>Each entry can be a string, bytes, SafeString, PathLike, or a callable that returns one of the former (see <a href=../api#django_components.ComponentMediaInputPath><code>ComponentMediaInputPath</code></a>).</p> <p>Examples: <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
+</code></pre></div> <div class="doc doc-contents "> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L161 target=_blank>See source code</a></p> <p>JS files associated with a <a href=../api#django_components.Component><code>Component</code></a>.</p> <ul> <li> <p>If a string, it's assumed to be a path to a JS file.</p> </li> <li> <p>If a list, each entry is assumed to be a path to a JS file.</p> </li> </ul> <p>Each entry can be a string, bytes, SafeString, PathLike, or a callable that returns one of the former (see <a href=../api#django_components.ComponentMediaInputPath><code>ComponentMediaInputPath</code></a>).</p> <p>Examples: <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
 <a id=__codelineno-0-2 name=__codelineno-0-2 href=#__codelineno-0-2></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
 <a id=__codelineno-0-3 name=__codelineno-0-3 href=#__codelineno-0-3></a>        <span class=n>js</span> <span class=o>=</span> <span class=s2>&quot;path/to/script.js&quot;</span>
 </code></pre></div></p> <div class=highlight><pre><span></span><code><a id=__codelineno-1-1 name=__codelineno-1-1 href=#__codelineno-1-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
@@ -1189,7 +1189,7 @@
 <a id=__codelineno-2-2 name=__codelineno-2-2 href=#__codelineno-2-2></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
 <a id=__codelineno-2-3 name=__codelineno-2-3 href=#__codelineno-2-3></a>        <span class=n>js</span> <span class=o>=</span> <span class=k>lambda</span><span class=p>:</span> <span class=p>[</span><span class=s2>&quot;path/to/script1.js&quot;</span><span class=p>,</span> <span class=s2>&quot;path/to/script2.js&quot;</span><span class=p>]</span>
 </code></pre></div> </div> </div> </div> </div> </div> <div class="doc doc-object doc-attribute"> <h2 id=django_components.ComponentMediaInputPath class="doc doc-heading"> <code class="doc-symbol doc-symbol-heading doc-symbol-attribute"></code> <span class="doc doc-object-name doc-attribute-name">ComponentMediaInputPath</span> <span class="doc doc-labels"> <small class="doc doc-label doc-label-module-attribute"><code>module-attribute</code></small> </span> <a href=#django_components.ComponentMediaInputPath class=headerlink title="Permanent link">¤</a></h2> <div class="doc-signature highlight"><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=n>ComponentMediaInputPath</span> <span class=o>=</span> <span class=n><a class="autorefs autorefs-external" title=typing.Union href=https://docs.python.org/3.12/library/typing.html#typing.Union>Union</a></span><span class=p>[</span><span class=n><a class="autorefs autorefs-external" href=https://docs.python.org/3.12/library/stdtypes.html#str>str</a></span><span class=p>,</span> <span class=n><a class="autorefs autorefs-external" href=https://docs.python.org/3.12/library/stdtypes.html#bytes>bytes</a></span><span class=p>,</span> <span class=n><span title=django.utils.safestring.SafeData>SafeData</span></span><span class=p>,</span> <span class=n><a class="autorefs autorefs-external" title=pathlib.Path href=https://docs.python.org/3.12/library/pathlib.html#pathlib.Path>Path</a></span><span class=p>,</span> <span class=n><a class="autorefs autorefs-external" title=os.PathLike href=https://docs.python.org/3.12/library/os.html#os.PathLike>PathLike</a></span><span class=p>,</span> <span class=n><a class="autorefs autorefs-external" title=typing.Callable href=https://docs.python.org/3.12/library/typing.html#typing.Callable>Callable</a></span><span class=p>[[],</span> <span class=n><a class="autorefs autorefs-external" title=typing.Union href=https://docs.python.org/3.12/library/typing.html#typing.Union>Union</a></span><span class=p>[</span><span class=n><a class="autorefs autorefs-external" href=https://docs.python.org/3.12/library/stdtypes.html#str>str</a></span><span class=p>,</span> <span class=n><a class="autorefs autorefs-external" href=https://docs.python.org/3.12/library/stdtypes.html#bytes>bytes</a></span><span class=p>,</span> <span class=n><span title=django.utils.safestring.SafeData>SafeData</span></span><span class=p>,</span> <span class=n><a class="autorefs autorefs-external" title=pathlib.Path href=https://docs.python.org/3.12/library/pathlib.html#pathlib.Path>Path</a></span><span class=p>,</span> <span class=n><a class="autorefs autorefs-external" title=os.PathLike href=https://docs.python.org/3.12/library/os.html#os.PathLike>PathLike</a></span><span class=p>]]]</span>
-</code></pre></div> <div class="doc doc-contents first"> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L29 target=_blank>See source code</a></p> <p>A type representing an entry in <a href=../api#django_components.ComponentMediaInput.js>Media.js</a> or <a href=../api#django_components.ComponentMediaInput.css>Media.css</a>.</p> <p>If an entry is a <a href=https://dev.to/doridoro/django-safestring-afj>SafeString</a> (or has <code>__html__</code> method), then entry is assumed to be a formatted HTML tag. Otherwise, it's assumed to be a path to a file.</p> <p><strong>Example:</strong></p> <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span>
+</code></pre></div> <div class="doc doc-contents first"> <p><a href=https://github.com/django-components/django-components/tree/master/src/django_components/component_media.py#L45 target=_blank>See source code</a></p> <p>A type representing an entry in <a href=../api#django_components.ComponentMediaInput.js>Media.js</a> or <a href=../api#django_components.ComponentMediaInput.css>Media.css</a>.</p> <p>If an entry is a <a href=https://dev.to/doridoro/django-safestring-afj>SafeString</a> (or has <code>__html__</code> method), then entry is assumed to be a formatted HTML tag. Otherwise, it's assumed to be a path to a file.</p> <p><strong>Example:</strong></p> <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span>
 <a id=__codelineno-0-2 name=__codelineno-0-2 href=#__codelineno-0-2></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
 <a id=__codelineno-0-3 name=__codelineno-0-3 href=#__codelineno-0-3></a>        <span class=n>js</span> <span class=o>=</span> <span class=p>[</span>
 <a id=__codelineno-0-4 name=__codelineno-0-4 href=#__codelineno-0-4></a>            <span class=s2>&quot;path/to/script.js&quot;</span><span class=p>,</span>
diff --git a/dev/release_notes/index.html b/dev/release_notes/index.html
index b54f8989..cee78a48 100644
--- a/dev/release_notes/index.html
+++ b/dev/release_notes/index.html
@@ -1,168 +1,172 @@
-<!doctype html><html lang=en class=no-js> <head><meta charset=utf-8><meta name=viewport content="width=device-width,initial-scale=1"><meta name=description content="A way to create simple reusable template components in Django."><link href=https://django-components.github.io/django-components/latest/release_notes/ rel=canonical><link href=../reference/testing_api/ rel=prev><link rel=icon href=../assets/images/favicon.png><meta name=generator content="mkdocs-1.6.1, mkdocs-material-9.6.9"><title>Release Notes - Django-Components</title><link rel=stylesheet href=../assets/stylesheets/main.4af4bdda.min.css><link rel=stylesheet href=../assets/stylesheets/palette.06af60db.min.css><link rel=preconnect href=https://fonts.gstatic.com crossorigin><link rel=stylesheet href="https://fonts.googleapis.com/css?family=Roboto:300,300i,400,400i,700,700i%7CRoboto+Mono:400,400i,700,700i&display=fallback"><style>:root{--md-text-font:"Roboto";--md-code-font:"Roboto Mono"}</style><link rel=stylesheet href=../assets/_markdown_exec_pyodide.css><link rel=stylesheet href=../assets/_mkdocstrings.css><link rel=stylesheet href=../css/timeago.css><link rel=stylesheet href=../css/style.css><script>__md_scope=new URL("..",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script><meta property=og:type content=website><meta property=og:title content="Release Notes - Django-Components"><meta property=og:description content="A way to create simple reusable template components in Django."><meta property=og:image content=https://django-components.github.io/django-components/latest/assets/images/social/release_notes.png><meta property=og:image:type content=image/png><meta property=og:image:width content=1200><meta property=og:image:height content=630><meta content=https://django-components.github.io/django-components/latest/release_notes/ property=og:url><meta name=twitter:card content=summary_large_image><meta name=twitter:title content="Release Notes - Django-Components"><meta name=twitter:description content="A way to create simple reusable template components in Django."><meta name=twitter:image content=https://django-components.github.io/django-components/latest/assets/images/social/release_notes.png></head> <body dir=ltr data-md-color-scheme=default data-md-color-primary=indigo data-md-color-accent=indigo> <input class=md-toggle data-md-toggle=drawer type=checkbox id=__drawer autocomplete=off> <input class=md-toggle data-md-toggle=search type=checkbox id=__search autocomplete=off> <label class=md-overlay for=__drawer></label> <div data-md-component=skip> <a href=#release-notes class=md-skip> Skip to content </a> </div> <div data-md-component=announce> </div> <div data-md-color-scheme=default data-md-component=outdated hidden> </div> <header class=md-header data-md-component=header> <nav class="md-header__inner md-grid" aria-label=Header> <a href=.. title=Django-Components class="md-header__button md-logo" aria-label=Django-Components data-md-component=logo> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 8a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3 3 3 0 0 0 3 3m0 3.54C9.64 9.35 6.5 8 3 8v11c3.5 0 6.64 1.35 9 3.54 2.36-2.19 5.5-3.54 9-3.54V8c-3.5 0-6.64 1.35-9 3.54"/></svg> </a> <label class="md-header__button md-icon" for=__drawer> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M3 6h18v2H3zm0 5h18v2H3zm0 5h18v2H3z"/></svg> </label> <div class=md-header__title data-md-component=header-title> <div class=md-header__ellipsis> <div class=md-header__topic> <span class=md-ellipsis> Django-Components </span> </div> <div class=md-header__topic data-md-component=header-topic> <span class=md-ellipsis> Release Notes </span> </div> </div> </div> <form class=md-header__option data-md-component=palette> <input class=md-option data-md-color-media=(prefers-color-scheme) data-md-color-scheme=default data-md-color-primary=indigo data-md-color-accent=indigo aria-label="Switch to light mode" type=radio name=__palette id=__palette_0> <label class="md-header__button md-icon" title="Switch to light mode" for=__palette_1 hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="m14.3 16-.7-2h-3.2l-.7 2H7.8L11 7h2l3.2 9zM20 8.69V4h-4.69L12 .69 8.69 4H4v4.69L.69 12 4 15.31V20h4.69L12 23.31 15.31 20H20v-4.69L23.31 12zm-9.15 3.96h2.3L12 9z"/></svg> </label> <input class=md-option data-md-color-media="(prefers-color-scheme: light)" data-md-color-scheme=default data-md-color-primary=teal data-md-color-accent=indigo aria-label="Switch to dark mode" type=radio name=__palette id=__palette_1> <label class="md-header__button md-icon" title="Switch to dark mode" for=__palette_2 hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="m17.75 4.09-2.53 1.94.91 3.06-2.63-1.81-2.63 1.81.91-3.06-2.53-1.94L12.44 4l1.06-3 1.06 3zm3.5 6.91-1.64 1.25.59 1.98-1.7-1.17-1.7 1.17.59-1.98L15.75 11l2.06-.05L18.5 9l.69 1.95zm-2.28 4.95c.83-.08 1.72 1.1 1.19 1.85-.32.45-.66.87-1.08 1.27C15.17 23 8.84 23 4.94 19.07c-3.91-3.9-3.91-10.24 0-14.14.4-.4.82-.76 1.27-1.08.75-.53 1.93.36 1.85 1.19-.27 2.86.69 5.83 2.89 8.02a9.96 9.96 0 0 0 8.02 2.89m-1.64 2.02a12.08 12.08 0 0 1-7.8-3.47c-2.17-2.19-3.33-5-3.49-7.82-2.81 3.14-2.7 7.96.31 10.98 3.02 3.01 7.84 3.12 10.98.31"/></svg> </label> <input class=md-option data-md-color-media="(prefers-color-scheme: dark)" data-md-color-scheme=slate data-md-color-primary=teal data-md-color-accent=indigo aria-label="Switch to light mode" type=radio name=__palette id=__palette_2> <label class="md-header__button md-icon" title="Switch to light mode" for=__palette_0 hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 7a5 5 0 0 1 5 5 5 5 0 0 1-5 5 5 5 0 0 1-5-5 5 5 0 0 1 5-5m0 2a3 3 0 0 0-3 3 3 3 0 0 0 3 3 3 3 0 0 0 3-3 3 3 0 0 0-3-3m0-7 2.39 3.42C13.65 5.15 12.84 5 12 5s-1.65.15-2.39.42zM3.34 7l4.16-.35A7.2 7.2 0 0 0 5.94 8.5c-.44.74-.69 1.5-.83 2.29zm.02 10 1.76-3.77a7.131 7.131 0 0 0 2.38 4.14zM20.65 7l-1.77 3.79a7.02 7.02 0 0 0-2.38-4.15zm-.01 10-4.14.36c.59-.51 1.12-1.14 1.54-1.86.42-.73.69-1.5.83-2.29zM12 22l-2.41-3.44c.74.27 1.55.44 2.41.44.82 0 1.63-.17 2.37-.44z"/></svg> </label> </form> <script>var palette=__md_get("__palette");if(palette&&palette.color){if("(prefers-color-scheme)"===palette.color.media){var media=matchMedia("(prefers-color-scheme: light)"),input=document.querySelector(media.matches?"[data-md-color-media='(prefers-color-scheme: light)']":"[data-md-color-media='(prefers-color-scheme: dark)']");palette.color.media=input.getAttribute("data-md-color-media"),palette.color.scheme=input.getAttribute("data-md-color-scheme"),palette.color.primary=input.getAttribute("data-md-color-primary"),palette.color.accent=input.getAttribute("data-md-color-accent")}for(var[key,value]of Object.entries(palette.color))document.body.setAttribute("data-md-color-"+key,value)}</script> <label class="md-header__button md-icon" for=__search> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg> </label> <div class=md-search data-md-component=search role=dialog> <label class=md-search__overlay for=__search></label> <div class=md-search__inner role=search> <form class=md-search__form name=search> <input type=text class=md-search__input name=query aria-label=Search placeholder=Search autocapitalize=off autocorrect=off autocomplete=off spellcheck=false data-md-component=search-query required> <label class="md-search__icon md-icon" for=__search> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg> </label> <nav class=md-search__options aria-label=Search> <a href=javascript:void(0) class="md-search__icon md-icon" title=Share aria-label=Share data-clipboard data-clipboard-text data-md-component=search-share tabindex=-1> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M18 16.08c-.76 0-1.44.3-1.96.77L8.91 12.7c.05-.23.09-.46.09-.7s-.04-.47-.09-.7l7.05-4.11c.54.5 1.25.81 2.04.81a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3c0 .24.04.47.09.7L8.04 9.81C7.5 9.31 6.79 9 6 9a3 3 0 0 0-3 3 3 3 0 0 0 3 3c.79 0 1.5-.31 2.04-.81l7.12 4.15c-.05.21-.08.43-.08.66 0 1.61 1.31 2.91 2.92 2.91s2.92-1.3 2.92-2.91A2.92 2.92 0 0 0 18 16.08"/></svg> </a> <button type=reset class="md-search__icon md-icon" title=Clear aria-label=Clear tabindex=-1> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M19 6.41 17.59 5 12 10.59 6.41 5 5 6.41 10.59 12 5 17.59 6.41 19 12 13.41 17.59 19 19 17.59 13.41 12z"/></svg> </button> </nav> <div class=md-search__suggest data-md-component=search-suggest></div> </form> <div class=md-search__output> <div class=md-search__scrollwrap tabindex=0 data-md-scrollfix> <div class=md-search-result data-md-component=search-result> <div class=md-search-result__meta> Initializing search </div> <ol class=md-search-result__list role=presentation></ol> </div> </div> </div> </div> </div> <div class=md-header__source> <a href=https://github.com/django-components/django-components title="Go to repository" class=md-source data-md-component=source> <div class="md-source__icon md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </div> <div class=md-source__repository> django-components/django-components </div> </a> </div> </nav> </header> <div class=md-container data-md-component=container> <nav class=md-tabs aria-label=Tabs data-md-component=tabs> <div class=md-grid> <ul class=md-tabs__list> <li class=md-tabs__item> <a href=../overview/welcome/ class=md-tabs__link> Overview </a> </li> <li class=md-tabs__item> <a href=../getting_started/your_first_component/ class=md-tabs__link> Getting Started </a> </li> <li class=md-tabs__item> <a href=../concepts/fundamentals/single_file_components/ class=md-tabs__link> Concepts </a> </li> <li class=md-tabs__item> <a href=../guides/setup/syntax_highlight/ class=md-tabs__link> Guides </a> </li> <li class=md-tabs__item> <a href=../reference/api/ class=md-tabs__link> API Documentation </a> </li> <li class="md-tabs__item md-tabs__item--active"> <a href=./ class=md-tabs__link> Release Notes </a> </li> </ul> </div> </nav> <main class=md-main data-md-component=main> <div class="md-main__inner md-grid"> <div class="md-sidebar md-sidebar--primary" data-md-component=sidebar data-md-type=navigation> <div class=md-sidebar__scrollwrap> <div class=md-sidebar__inner> <nav class="md-nav md-nav--primary md-nav--lifted" aria-label=Navigation data-md-level=0> <label class=md-nav__title for=__drawer> <a href=.. title=Django-Components class="md-nav__button md-logo" aria-label=Django-Components data-md-component=logo> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 8a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3 3 3 0 0 0 3 3m0 3.54C9.64 9.35 6.5 8 3 8v11c3.5 0 6.64 1.35 9 3.54 2.36-2.19 5.5-3.54 9-3.54V8c-3.5 0-6.64 1.35-9 3.54"/></svg> </a> Django-Components </label> <div class=md-nav__source> <a href=https://github.com/django-components/django-components title="Go to repository" class=md-source data-md-component=source> <div class="md-source__icon md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </div> <div class=md-source__repository> django-components/django-components </div> </a> </div> <ul class=md-nav__list data-md-scrollfix> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_1> <label class=md-nav__link for=__nav_1 id=__nav_1_label tabindex=0> <span class=md-ellipsis> Overview </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_1_label aria-expanded=false> <label class=md-nav__title for=__nav_1> <span class="md-nav__icon md-icon"></span> Overview </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../overview/welcome/ class=md-nav__link> <span class=md-ellipsis> Welcome to Django Components </span> </a> </li> <li class=md-nav__item> <a href=../overview/compatibility/ class=md-nav__link> <span class=md-ellipsis> Compatibility </span> </a> </li> <li class=md-nav__item> <a href=../overview/installation/ class=md-nav__link> <span class=md-ellipsis> Installation </span> </a> </li> <li class=md-nav__item> <a href=../overview/security_notes/ class=md-nav__link> <span class=md-ellipsis> Security notes 🚨 </span> </a> </li> <li class=md-nav__item> <a href=../overview/community/ class=md-nav__link> <span class=md-ellipsis> Community </span> </a> </li> <li class=md-nav__item> <a href=../overview/contributing/ class=md-nav__link> <span class=md-ellipsis> Contributing </span> </a> </li> <li class=md-nav__item> <a href=../overview/development/ class=md-nav__link> <span class=md-ellipsis> Development </span> </a> </li> <li class=md-nav__item> <a href=../overview/performance/ class=md-nav__link> <span class=md-ellipsis> Performance </span> </a> </li> <li class=md-nav__item> <a href=../overview/code_of_conduct/ class=md-nav__link> <span class=md-ellipsis> Code of Conduct </span> </a> </li> <li class=md-nav__item> <a href=../overview/license/ class=md-nav__link> <span class=md-ellipsis> License </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_2> <label class=md-nav__link for=__nav_2 id=__nav_2_label tabindex=0> <span class=md-ellipsis> Getting Started </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_2_label aria-expanded=false> <label class=md-nav__title for=__nav_2> <span class="md-nav__icon md-icon"></span> Getting Started </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../getting_started/your_first_component/ class=md-nav__link> <span class=md-ellipsis> Create your first component </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/adding_js_and_css/ class=md-nav__link> <span class=md-ellipsis> Adding JS and CSS </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/components_in_templates/ class=md-nav__link> <span class=md-ellipsis> Components in templates </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/parametrising_components/ class=md-nav__link> <span class=md-ellipsis> Parametrising components </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/adding_slots/ class=md-nav__link> <span class=md-ellipsis> Adding slots </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/rendering_components/ class=md-nav__link> <span class=md-ellipsis> Rendering components </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_3> <label class=md-nav__link for=__nav_3 id=__nav_3_label tabindex=0> <span class=md-ellipsis> Concepts </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_3_label aria-expanded=false> <label class=md-nav__title for=__nav_3> <span class="md-nav__icon md-icon"></span> Concepts </label> <ul class=md-nav__list data-md-scrollfix> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_3_1> <label class=md-nav__link for=__nav_3_1 id=__nav_3_1_label tabindex=0> <span class=md-ellipsis> Fundamentals </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_3_1_label aria-expanded=false> <label class=md-nav__title for=__nav_3_1> <span class="md-nav__icon md-icon"></span> Fundamentals </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../concepts/fundamentals/single_file_components/ class=md-nav__link> <span class=md-ellipsis> Single-file components </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/components_in_python/ class=md-nav__link> <span class=md-ellipsis> Components in Python </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/access_component_input/ class=md-nav__link> <span class=md-ellipsis> Accessing component inputs </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/component_context_scope/ class=md-nav__link> <span class=md-ellipsis> Component context and scope </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/template_tag_syntax/ class=md-nav__link> <span class=md-ellipsis> Template tag syntax </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/slots/ class=md-nav__link> <span class=md-ellipsis> Slots </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/html_attributes/ class=md-nav__link> <span class=md-ellipsis> HTML attributes </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/defining_js_css_html_files/ class=md-nav__link> <span class=md-ellipsis> Defining HTML / JS / CSS files </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/autodiscovery/ class=md-nav__link> <span class=md-ellipsis> Autodiscovery </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/components_as_views/ class=md-nav__link> <span class=md-ellipsis> Components as views </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/http_request/ class=md-nav__link> <span class=md-ellipsis> HTTP Request </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/subclassing_components/ class=md-nav__link> <span class=md-ellipsis> Subclassing components </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_3_2> <label class=md-nav__link for=__nav_3_2 id=__nav_3_2_label tabindex=0> <span class=md-ellipsis> Advanced </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_3_2_label aria-expanded=false> <label class=md-nav__title for=__nav_3_2> <span class="md-nav__icon md-icon"></span> Advanced </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../concepts/advanced/rendering_js_css/ class=md-nav__link> <span class=md-ellipsis> Rendering JS / CSS </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/html_fragments/ class=md-nav__link> <span class=md-ellipsis> HTML fragments </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/provide_inject/ class=md-nav__link> <span class=md-ellipsis> Prop drilling and provide / inject </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/hooks/ class=md-nav__link> <span class=md-ellipsis> Lifecycle hooks </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/component_registry/ class=md-nav__link> <span class=md-ellipsis> Registering components </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/typing_and_validation/ class=md-nav__link> <span class=md-ellipsis> Typing and validation </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/template_tags/ class=md-nav__link> <span class=md-ellipsis> Custom template tags </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/tag_formatter/ class=md-nav__link> <span class=md-ellipsis> Tag formatters </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/extensions/ class=md-nav__link> <span class=md-ellipsis> Extensions </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/testing/ class=md-nav__link> <span class=md-ellipsis> Testing </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/authoring_component_libraries/ class=md-nav__link> <span class=md-ellipsis> Authoring component libraries </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_4> <label class=md-nav__link for=__nav_4 id=__nav_4_label tabindex=0> <span class=md-ellipsis> Guides </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_4_label aria-expanded=false> <label class=md-nav__title for=__nav_4> <span class="md-nav__icon md-icon"></span> Guides </label> <ul class=md-nav__list data-md-scrollfix> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_4_1> <label class=md-nav__link for=__nav_4_1 id=__nav_4_1_label tabindex=0> <span class=md-ellipsis> Setup </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_4_1_label aria-expanded=false> <label class=md-nav__title for=__nav_4_1> <span class="md-nav__icon md-icon"></span> Setup </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../guides/setup/syntax_highlight/ class=md-nav__link> <span class=md-ellipsis> Syntax highlighting </span> </a> </li> <li class=md-nav__item> <a href=../guides/setup/caching/ class=md-nav__link> <span class=md-ellipsis> Caching </span> </a> </li> <li class=md-nav__item> <a href=../guides/setup/development_server/ class=md-nav__link> <span class=md-ellipsis> Development server </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_4_2> <label class=md-nav__link for=__nav_4_2 id=__nav_4_2_label tabindex=0> <span class=md-ellipsis> Other </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_4_2_label aria-expanded=false> <label class=md-nav__title for=__nav_4_2> <span class="md-nav__icon md-icon"></span> Other </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../guides/other/troubleshooting/ class=md-nav__link> <span class=md-ellipsis> Troubleshooting </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_4_3> <label class=md-nav__link for=__nav_4_3 id=__nav_4_3_label tabindex=0> <span class=md-ellipsis> Dev Guides </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_4_3_label aria-expanded=false> <label class=md-nav__title for=__nav_4_3> <span class="md-nav__icon md-icon"></span> Dev Guides </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../guides/devguides/dependency_mgmt/ class=md-nav__link> <span class=md-ellipsis> JS and CSS rendering </span> </a> </li> <li class=md-nav__item> <a href=../guides/devguides/slot_rendering/ class=md-nav__link> <span class=md-ellipsis> Slot rendering </span> </a> </li> <li class=md-nav__item> <a href=../guides/devguides/slots_and_blocks/ class=md-nav__link> <span class=md-ellipsis> Using slot and block tags </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_5> <label class=md-nav__link for=__nav_5 id=__nav_5_label tabindex=0> <span class=md-ellipsis> API Documentation </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_5_label aria-expanded=false> <label class=md-nav__title for=__nav_5> <span class="md-nav__icon md-icon"></span> API Documentation </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../reference/api/ class=md-nav__link> <span class=md-ellipsis> API </span> </a> </li> <li class=md-nav__item> <a href=../reference/commands/ class=md-nav__link> <span class=md-ellipsis> Commands </span> </a> </li> <li class=md-nav__item> <a href=../reference/components/ class=md-nav__link> <span class=md-ellipsis> Components </span> </a> </li> <li class=md-nav__item> <a href=../reference/exceptions/ class=md-nav__link> <span class=md-ellipsis> Exceptions </span> </a> </li> <li class=md-nav__item> <a href=../reference/extension_hooks/ class=md-nav__link> <span class=md-ellipsis> Extension hooks </span> </a> </li> <li class=md-nav__item> <a href=../reference/middlewares/ class=md-nav__link> <span class=md-ellipsis> Middlewares </span> </a> </li> <li class=md-nav__item> <a href=../reference/settings/ class=md-nav__link> <span class=md-ellipsis> Settings </span> </a> </li> <li class=md-nav__item> <a href=../reference/signals/ class=md-nav__link> <span class=md-ellipsis> Signals </span> </a> </li> <li class=md-nav__item> <a href=../reference/tag_formatters/ class=md-nav__link> <span class=md-ellipsis> Tag formatters </span> </a> </li> <li class=md-nav__item> <a href=../reference/template_tags/ class=md-nav__link> <span class=md-ellipsis> Template tags </span> </a> </li> <li class=md-nav__item> <a href=../reference/template_vars/ class=md-nav__link> <span class=md-ellipsis> Template vars </span> </a> </li> <li class=md-nav__item> <a href=../reference/urls/ class=md-nav__link> <span class=md-ellipsis> URLs </span> </a> </li> <li class=md-nav__item> <a href=../reference/testing_api/ class=md-nav__link> <span class=md-ellipsis> Testing API </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--active"> <input class="md-nav__toggle md-toggle" type=checkbox id=__toc> <label class="md-nav__link md-nav__link--active" for=__toc> <span class=md-ellipsis> Release Notes </span> <span class="md-nav__icon md-icon"></span> </label> <a href=./ class="md-nav__link md-nav__link--active"> <span class=md-ellipsis> Release Notes </span> </a> <nav class="md-nav md-nav--secondary" aria-label="Table of contents"> <label class=md-nav__title for=__toc> <span class="md-nav__icon md-icon"></span> Table of contents </label> <ul class=md-nav__list data-md-component=toc data-md-scrollfix> <li class=md-nav__item> <a href=#v0131 class=md-nav__link> <span class=md-ellipsis> v0.131 </span> </a> <nav class=md-nav aria-label=v0.131> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> <li class=md-nav__item> <a href=#internal class=md-nav__link> <span class=md-ellipsis> Internal </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0130 class=md-nav__link> <span class=md-ellipsis> v0.130 </span> </a> <nav class=md-nav aria-label=v0.130> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_1 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0129 class=md-nav__link> <span class=md-ellipsis> v0.129 </span> </a> <nav class=md-nav aria-label=v0.129> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0128 class=md-nav__link> <span class=md-ellipsis> v0.128 </span> </a> <nav class=md-nav aria-label=v0.128> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_2 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_1 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> <li class=md-nav__item> <a href=#perf class=md-nav__link> <span class=md-ellipsis> Perf </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0127 class=md-nav__link> <span class=md-ellipsis> v0.127 </span> </a> <nav class=md-nav aria-label=v0.127> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_1 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0126 class=md-nav__link> <span class=md-ellipsis> v0.126 </span> </a> <nav class=md-nav aria-label=v0.126> <ul class=md-nav__list> <li class=md-nav__item> <a href=#refactor_2 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0125 class=md-nav__link> <span class=md-ellipsis> v0.125 </span> </a> <nav class=md-nav aria-label=v0.125> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_3 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_3 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0124 class=md-nav__link> <span class=md-ellipsis> v0.124 </span> </a> <nav class=md-nav aria-label=v0.124> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_4 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_4 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0123 class=md-nav__link> <span class=md-ellipsis> v0.123 </span> </a> <nav class=md-nav aria-label=v0.123> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_2 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0122 class=md-nav__link> <span class=md-ellipsis> v0.122 </span> </a> <nav class=md-nav aria-label=v0.122> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_5 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0121 class=md-nav__link> <span class=md-ellipsis> v0.121 </span> </a> <nav class=md-nav aria-label=v0.121> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_3 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0120 class=md-nav__link> <span class=md-ellipsis> v0.120 </span> </a> <nav class=md-nav aria-label=v0.120> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_4 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0119 class=md-nav__link> <span class=md-ellipsis> v0.119 </span> </a> <nav class=md-nav aria-label=v0.119> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_5 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_5 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0118 class=md-nav__link> <span class=md-ellipsis> v0.118 </span> </a> <nav class=md-nav aria-label=v0.118> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_6 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0117 class=md-nav__link> <span class=md-ellipsis> v0.117 </span> </a> <nav class=md-nav aria-label=v0.117> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_6 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_6 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0116 class=md-nav__link> <span class=md-ellipsis> v0.116 </span> </a> <nav class=md-nav aria-label=v0.116> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_7 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0115 class=md-nav__link> <span class=md-ellipsis> v0.115 </span> </a> <nav class=md-nav aria-label=v0.115> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_8 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0114 class=md-nav__link> <span class=md-ellipsis> v0.114 </span> </a> <nav class=md-nav aria-label=v0.114> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_9 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0113 class=md-nav__link> <span class=md-ellipsis> v0.113 </span> </a> <nav class=md-nav aria-label=v0.113> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_10 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0112 class=md-nav__link> <span class=md-ellipsis> v0.112 </span> </a> <nav class=md-nav aria-label=v0.112> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_11 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0111 class=md-nav__link> <span class=md-ellipsis> v0.111 </span> </a> <nav class=md-nav aria-label=v0.111> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_12 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0110 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.110 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.110"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#general class=md-nav__link> <span class=md-ellipsis> General </span> </a> <nav class=md-nav aria-label=General> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes class=md-nav__link> <span class=md-ellipsis> 🚨📢 BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_7 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_7 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#tags class=md-nav__link> <span class=md-ellipsis> Tags </span> </a> <nav class=md-nav aria-label=Tags> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_1 class=md-nav__link> <span class=md-ellipsis> 🚨📢 BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#fix_13 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_8 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#slots class=md-nav__link> <span class=md-ellipsis> Slots </span> </a> <nav class=md-nav aria-label=Slots> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_8 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#fix_14 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_9 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0100 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.100 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.100"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_2 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_9 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_10 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v097 class=md-nav__link> <span class=md-ellipsis> v0.97 </span> </a> <nav class=md-nav aria-label=v0.97> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_15 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_11 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v096 class=md-nav__link> <span class=md-ellipsis> v0.96 </span> </a> <nav class=md-nav aria-label=v0.96> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_10 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#095 class=md-nav__link> <span class=md-ellipsis> 0.95 </span> </a> <nav class=md-nav aria-label=0.95> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_11 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_12 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v094 class=md-nav__link> <span class=md-ellipsis> v0.94 </span> </a> <nav class=md-nav aria-label=v0.94> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_12 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v093 class=md-nav__link> <span class=md-ellipsis> v0.93 </span> </a> <nav class=md-nav aria-label=v0.93> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_13 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v092 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.92 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.92"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_3 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_14 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v090 class=md-nav__link> <span class=md-ellipsis> v0.90 </span> </a> <nav class=md-nav aria-label=v0.90> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_15 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v085 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.85 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.85"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_4 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v081 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.81 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.81"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_5 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_16 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v080 class=md-nav__link> <span class=md-ellipsis> v0.80 </span> </a> <nav class=md-nav aria-label=v0.80> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_17 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v079 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.79 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.79"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_6 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v077 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.77 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.77"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking class=md-nav__link> <span class=md-ellipsis> BREAKING </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v074 class=md-nav__link> <span class=md-ellipsis> v0.74 </span> </a> <nav class=md-nav aria-label=v0.74> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_18 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v070 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.70 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.70"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_7 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v067 class=md-nav__link> <span class=md-ellipsis> v0.67 </span> </a> <nav class=md-nav aria-label=v0.67> <ul class=md-nav__list> <li class=md-nav__item> <a href=#refactor_13 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v050 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.50 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.50"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_8 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v034 class=md-nav__link> <span class=md-ellipsis> v0.34 </span> </a> <nav class=md-nav aria-label=v0.34> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_19 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v028 class=md-nav__link> <span class=md-ellipsis> v0.28 </span> </a> <nav class=md-nav aria-label=v0.28> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_20 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v027 class=md-nav__link> <span class=md-ellipsis> v0.27 </span> </a> <nav class=md-nav aria-label=v0.27> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_21 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v026 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.26 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.26"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_9 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v022 class=md-nav__link> <span class=md-ellipsis> v0.22 </span> </a> <nav class=md-nav aria-label=v0.22> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_22 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v017 class=md-nav__link> <span class=md-ellipsis> v0.17 </span> </a> <nav class=md-nav aria-label=v0.17> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_10 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> </ul> </nav> </div> </div> </div> <div class="md-sidebar md-sidebar--secondary" data-md-component=sidebar data-md-type=toc> <div class=md-sidebar__scrollwrap> <div class=md-sidebar__inner> <nav class="md-nav md-nav--secondary" aria-label="Table of contents"> <label class=md-nav__title for=__toc> <span class="md-nav__icon md-icon"></span> Table of contents </label> <ul class=md-nav__list data-md-component=toc data-md-scrollfix> <li class=md-nav__item> <a href=#v0131 class=md-nav__link> <span class=md-ellipsis> v0.131 </span> </a> <nav class=md-nav aria-label=v0.131> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> <li class=md-nav__item> <a href=#internal class=md-nav__link> <span class=md-ellipsis> Internal </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0130 class=md-nav__link> <span class=md-ellipsis> v0.130 </span> </a> <nav class=md-nav aria-label=v0.130> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_1 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0129 class=md-nav__link> <span class=md-ellipsis> v0.129 </span> </a> <nav class=md-nav aria-label=v0.129> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0128 class=md-nav__link> <span class=md-ellipsis> v0.128 </span> </a> <nav class=md-nav aria-label=v0.128> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_2 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_1 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> <li class=md-nav__item> <a href=#perf class=md-nav__link> <span class=md-ellipsis> Perf </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0127 class=md-nav__link> <span class=md-ellipsis> v0.127 </span> </a> <nav class=md-nav aria-label=v0.127> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_1 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0126 class=md-nav__link> <span class=md-ellipsis> v0.126 </span> </a> <nav class=md-nav aria-label=v0.126> <ul class=md-nav__list> <li class=md-nav__item> <a href=#refactor_2 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0125 class=md-nav__link> <span class=md-ellipsis> v0.125 </span> </a> <nav class=md-nav aria-label=v0.125> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_3 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_3 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0124 class=md-nav__link> <span class=md-ellipsis> v0.124 </span> </a> <nav class=md-nav aria-label=v0.124> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_4 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_4 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0123 class=md-nav__link> <span class=md-ellipsis> v0.123 </span> </a> <nav class=md-nav aria-label=v0.123> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_2 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0122 class=md-nav__link> <span class=md-ellipsis> v0.122 </span> </a> <nav class=md-nav aria-label=v0.122> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_5 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0121 class=md-nav__link> <span class=md-ellipsis> v0.121 </span> </a> <nav class=md-nav aria-label=v0.121> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_3 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0120 class=md-nav__link> <span class=md-ellipsis> v0.120 </span> </a> <nav class=md-nav aria-label=v0.120> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_4 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0119 class=md-nav__link> <span class=md-ellipsis> v0.119 </span> </a> <nav class=md-nav aria-label=v0.119> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_5 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_5 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0118 class=md-nav__link> <span class=md-ellipsis> v0.118 </span> </a> <nav class=md-nav aria-label=v0.118> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_6 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0117 class=md-nav__link> <span class=md-ellipsis> v0.117 </span> </a> <nav class=md-nav aria-label=v0.117> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_6 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_6 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0116 class=md-nav__link> <span class=md-ellipsis> v0.116 </span> </a> <nav class=md-nav aria-label=v0.116> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_7 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0115 class=md-nav__link> <span class=md-ellipsis> v0.115 </span> </a> <nav class=md-nav aria-label=v0.115> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_8 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0114 class=md-nav__link> <span class=md-ellipsis> v0.114 </span> </a> <nav class=md-nav aria-label=v0.114> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_9 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0113 class=md-nav__link> <span class=md-ellipsis> v0.113 </span> </a> <nav class=md-nav aria-label=v0.113> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_10 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0112 class=md-nav__link> <span class=md-ellipsis> v0.112 </span> </a> <nav class=md-nav aria-label=v0.112> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_11 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0111 class=md-nav__link> <span class=md-ellipsis> v0.111 </span> </a> <nav class=md-nav aria-label=v0.111> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_12 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0110 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.110 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.110"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#general class=md-nav__link> <span class=md-ellipsis> General </span> </a> <nav class=md-nav aria-label=General> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes class=md-nav__link> <span class=md-ellipsis> 🚨📢 BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_7 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_7 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#tags class=md-nav__link> <span class=md-ellipsis> Tags </span> </a> <nav class=md-nav aria-label=Tags> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_1 class=md-nav__link> <span class=md-ellipsis> 🚨📢 BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#fix_13 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_8 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#slots class=md-nav__link> <span class=md-ellipsis> Slots </span> </a> <nav class=md-nav aria-label=Slots> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_8 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#fix_14 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_9 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0100 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.100 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.100"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_2 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_9 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_10 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v097 class=md-nav__link> <span class=md-ellipsis> v0.97 </span> </a> <nav class=md-nav aria-label=v0.97> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_15 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_11 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v096 class=md-nav__link> <span class=md-ellipsis> v0.96 </span> </a> <nav class=md-nav aria-label=v0.96> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_10 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#095 class=md-nav__link> <span class=md-ellipsis> 0.95 </span> </a> <nav class=md-nav aria-label=0.95> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_11 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_12 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v094 class=md-nav__link> <span class=md-ellipsis> v0.94 </span> </a> <nav class=md-nav aria-label=v0.94> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_12 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v093 class=md-nav__link> <span class=md-ellipsis> v0.93 </span> </a> <nav class=md-nav aria-label=v0.93> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_13 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v092 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.92 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.92"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_3 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_14 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v090 class=md-nav__link> <span class=md-ellipsis> v0.90 </span> </a> <nav class=md-nav aria-label=v0.90> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_15 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v085 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.85 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.85"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_4 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v081 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.81 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.81"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_5 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_16 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v080 class=md-nav__link> <span class=md-ellipsis> v0.80 </span> </a> <nav class=md-nav aria-label=v0.80> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_17 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v079 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.79 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.79"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_6 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v077 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.77 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.77"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking class=md-nav__link> <span class=md-ellipsis> BREAKING </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v074 class=md-nav__link> <span class=md-ellipsis> v0.74 </span> </a> <nav class=md-nav aria-label=v0.74> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_18 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v070 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.70 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.70"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_7 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v067 class=md-nav__link> <span class=md-ellipsis> v0.67 </span> </a> <nav class=md-nav aria-label=v0.67> <ul class=md-nav__list> <li class=md-nav__item> <a href=#refactor_13 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v050 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.50 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.50"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_8 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v034 class=md-nav__link> <span class=md-ellipsis> v0.34 </span> </a> <nav class=md-nav aria-label=v0.34> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_19 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v028 class=md-nav__link> <span class=md-ellipsis> v0.28 </span> </a> <nav class=md-nav aria-label=v0.28> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_20 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v027 class=md-nav__link> <span class=md-ellipsis> v0.27 </span> </a> <nav class=md-nav aria-label=v0.27> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_21 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v026 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.26 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.26"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_9 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v022 class=md-nav__link> <span class=md-ellipsis> v0.22 </span> </a> <nav class=md-nav aria-label=v0.22> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_22 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v017 class=md-nav__link> <span class=md-ellipsis> v0.17 </span> </a> <nav class=md-nav aria-label=v0.17> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_10 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> </ul> </nav> </div> </div> </div> <div class=md-content data-md-component=content> <article class="md-content__inner md-typeset"> <a href=https://github.com/django-components/django-components/edit/master/docs/release_notes.md title="Edit this page" class="md-content__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4zm10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1z"/></svg> </a> <a href=https://github.com/django-components/django-components/raw/master/docs/release_notes.md title="View source of this page" class="md-content__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M17 18c.56 0 1 .44 1 1s-.44 1-1 1-1-.44-1-1 .44-1 1-1m0-3c-2.73 0-5.06 1.66-6 4 .94 2.34 3.27 4 6 4s5.06-1.66 6-4c-.94-2.34-3.27-4-6-4m0 6.5a2.5 2.5 0 0 1-2.5-2.5 2.5 2.5 0 0 1 2.5-2.5 2.5 2.5 0 0 1 2.5 2.5 2.5 2.5 0 0 1-2.5 2.5M9.27 20H6V4h7v5h5v4.07c.7.08 1.36.25 2 .49V8l-6-6H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h4.5a8.2 8.2 0 0 1-1.23-2"/></svg> </a> <h1 id=release-notes>Release notes<a class=headerlink href=#release-notes title="Permanent link">¤</a></h1> <h2 id=v0131>v0.131<a class=headerlink href=#v0131 title="Permanent link">¤</a></h2> <h4 id=feat>Feat<a class=headerlink href=#feat title="Permanent link">¤</a></h4> <ul> <li> <p>Support for extensions (plugins) for django-components!</p> <ul> <li>Hook into lifecycle events of django-components</li> <li>Pre-/post-process component inputs, outputs, and templates</li> <li>Add extra methods or attributes to Components</li> <li>Add custom extension-specific CLI commands</li> <li>Add custom extension-specific URL routes</li> </ul> <p>Read more on <a href=https://django-components.github.io/django-components/0.131/concepts/advanced/extensions/ >Extensions</a>.</p> </li> <li> <p>New CLI commands:</p> <ul> <li><code>components list</code> - List all components</li> <li><code>components create &lt;name&gt;</code> - Create a new component (supersedes <code>startcomponent</code>)</li> <li><code>components upgrade</code> - Upgrade a component (supersedes <code>upgradecomponent</code>)</li> <li><code>components ext list</code> - List all extensions</li> <li><code>components ext run &lt;extension&gt; &lt;command&gt;</code> - Run a command added by an extension</li> </ul> </li> <li> <p><code>@djc_test</code> decorator for writing tests that involve Components.</p> <ul> <li>The decorator manages global state, ensuring that tests don't leak.</li> <li>If using <code>pytest</code>, the decorator allows you to parametrize Django or Components settings.</li> <li>The decorator also serves as a stand-in for Django's <code>@override_settings</code>.</li> </ul> <p>See the API reference for <a href=https://django-components.github.io/django-components/0.131/reference/testing_api/#djc_test><code>@djc_test</code></a> for more details.</p> </li> <li> <p><code>ComponentRegistry</code> now has a <code>has()</code> method to check if a component is registered without raising an error.</p> </li> <li> <p>Get all created <code>Component</code> classes with <code>all_components()</code>.</p> </li> <li> <p>Get all created <code>ComponentRegistry</code> instances with <code>all_registries()</code>.</p> </li> </ul> <h4 id=refactor>Refactor<a class=headerlink href=#refactor title="Permanent link">¤</a></h4> <ul> <li> <p>The <code>startcomponent</code> and <code>upgradecomponent</code> commands are deprecated, and will be removed in v1.</p> <p>Instead, use <code>components create &lt;name&gt;</code> and <code>components upgrade</code>.</p> </li> </ul> <h4 id=internal>Internal<a class=headerlink href=#internal title="Permanent link">¤</a></h4> <ul> <li>Settings are now loaded only once, and thus are considered immutable once loaded. Previously, django-components would load settings from <code>settings.COMPONENTS</code> on each access. The new behavior aligns with Django's settings.</li> </ul> <h2 id=v0130>v0.130<a class=headerlink href=#v0130 title="Permanent link">¤</a></h2> <h4 id=feat_1>Feat<a class=headerlink href=#feat_1 title="Permanent link">¤</a></h4> <ul> <li> <p>Access the HttpRequest object under <code>Component.request</code>.</p> <p>To pass the request object to a component, either: - Render a template or component with <code>RequestContext</code>, - Or set the <code>request</code> kwarg to <code>Component.render()</code> or <code>Component.render_to_response()</code>.</p> <p>Read more on <a href=https://django-components.github.io/django-components/0.130/concepts/fundamentals/http_request/ >HttpRequest</a>.</p> </li> <li> <p>Access the context processors data under <code>Component.context_processors_data</code>.</p> <p>Context processors data is available only when the component has access to the <code>request</code> object, either by: - Passing the request to <code>Component.render()</code> or <code>Component.render_to_response()</code>, - Or by rendering a template or component with <code>RequestContext</code>, - Or being nested in another component that has access to the request object.</p> <p>The data from context processors is automatically available within the component's template.</p> <p>Read more on <a href=https://django-components.github.io/django-components/0.130/concepts/fundamentals/http_request/ >HttpRequest</a>.</p> </li> </ul> <h2 id=v0129>v0.129<a class=headerlink href=#v0129 title="Permanent link">¤</a></h2> <h4 id=fix>Fix<a class=headerlink href=#fix title="Permanent link">¤</a></h4> <ul> <li>Fix thread unsafe media resolve validation by moving it to ComponentMedia <code>__post_init</code> (<a href=https://github.com/django-components/django-components/pull/977>#977</a></li> <li>Fix bug: Relative path in extends and include does not work when using template_file (<a href=https://github.com/django-components/django-components/pull/976>#976</a></li> <li>Fix error when template cache setting (<code>template_cache_size</code>) is set to 0 (<a href=https://github.com/django-components/django-components/pull/974>#974</a></li> </ul> <h2 id=v0128>v0.128<a class=headerlink href=#v0128 title="Permanent link">¤</a></h2> <h4 id=feat_2>Feat<a class=headerlink href=#feat_2 title="Permanent link">¤</a></h4> <ul> <li> <p>Configurable cache - Set <a href=https://django-components.github.io/django-components/0.128/reference/settings/#django_components.app_settings.ComponentsSettings.cache><code>COMPONENTS.cache</code></a> to change where and how django-components caches JS and CSS files. (<a href=https://github.com/django-components/django-components/pull/946>#946</a>)</p> <p>Read more on <a href=https://django-components.github.io/django-components/0.128/guides/setup/caching>Caching</a>.</p> </li> <li> <p>Highlight coponents and slots in the UI - We've added two boolean settings <a href=https://django-components.github.io/django-components/0.128/reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_components><code>COMPONENTS.debug_highlight_components</code></a> and <a href=https://django-components.github.io/django-components/0.128/reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_slots><code>COMPONENTS.debug_highlight_slots</code></a>, which can be independently set to <code>True</code>. First will wrap components in a blue border, the second will wrap slots in a red border. (<a href=https://github.com/django-components/django-components/pull/942>#942</a>)</p> <p>Read more on <a href=https://django-components.github.io/django-components/0.128/guides/other/troubleshooting/#component-and-slot-highlighting>Troubleshooting</a>.</p> </li> </ul> <h4 id=refactor_1>Refactor<a class=headerlink href=#refactor_1 title="Permanent link">¤</a></h4> <ul> <li>Removed use of eval for node validation (<a href=https://github.com/django-components/django-components/pull/944>#944</a>)</li> </ul> <h4 id=perf>Perf<a class=headerlink href=#perf title="Permanent link">¤</a></h4> <ul> <li> <p>Components can now be infinitely nested. (<a href=https://github.com/django-components/django-components/pull/936>#936</a>)</p> </li> <li> <p>Component input validation is now 6-7x faster on CPython and PyPy. This previously made up 10-30% of the total render time. (<a href=https://github.com/django-components/django-components/pull/945>#945</a>)</p> </li> </ul> <h2 id=v0127>v0.127<a class=headerlink href=#v0127 title="Permanent link">¤</a></h2> <h4 id=fix_1>Fix<a class=headerlink href=#fix_1 title="Permanent link">¤</a></h4> <ul> <li>Fix component rendering when using <code>{% cache %}</code> with remote cache and multiple web servers (<a href=https://github.com/django-components/django-components/issues/930>#930</a>)</li> </ul> <h2 id=v0126>v0.126<a class=headerlink href=#v0126 title="Permanent link">¤</a></h2> <h4 id=refactor_2>Refactor<a class=headerlink href=#refactor_2 title="Permanent link">¤</a></h4> <ul> <li>Replaced <a href=https://www.crummy.com/software/BeautifulSoup/bs4/doc/ >BeautifulSoup4</a> with a custom HTML parser.</li> <li>The heuristic for inserting JS and CSS dependenies into the default place has changed.<ul> <li>JS is still inserted at the end of the <code>&lt;body&gt;</code>, and CSS at the end of <code>&lt;head&gt;</code>.</li> <li>However, we find end of <code>&lt;body&gt;</code> by searching for <strong>last</strong> occurrence of <code>&lt;/body&gt;</code></li> <li>And for the end of <code>&lt;head&gt;</code> we search for the <strong>first</strong> occurrence of <code>&lt;/head&gt;</code></li> </ul> </li> </ul> <h2 id=v0125>v0.125<a class=headerlink href=#v0125 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - We migrated from <code>EmilStenstrom/django-components</code> to <code>django-components/django-components</code>.</p> <p><strong>Repo name and documentation URL changed. Package name remains the same.</strong></p> <p>If you see any broken links or other issues, please report them in <a href=https://github.com/django-components/django-components/issues/922>#922</a>.</p> <h4 id=feat_3>Feat<a class=headerlink href=#feat_3 title="Permanent link">¤</a></h4> <ul> <li><code>@template_tag</code> and <code>BaseNode</code> - A decorator and a class that allow you to define custom template tags that will behave similarly to django-components' own template tags.</li> </ul> <p>Read more on <a href=https://django-components.github.io/django-components/0.125/concepts/advanced/template_tags/ >Template tags</a>.</p> <p>Template tags defined with <code>@template_tag</code> and <code>BaseNode</code> will have the following features:</p> <ul> <li> <p>Accepting args, kwargs, and flags.</p> </li> <li> <p>Allowing literal lists and dicts as inputs as:</p> <p><code>key=[1, 2, 3]</code> or <code>key={"a": 1, "b": 2}</code> - Using template tags tag inputs as:</p> <p><code>{% my_tag key="{% lorem 3 w %}" / %}</code> - Supporting the flat dictionary definition:</p> <p><code>attr:key=value</code> - Spreading args and kwargs with <code>...</code>:</p> <p><code>{% my_tag ...args ...kwargs / %}</code> - Being able to call the template tag as:</p> <p><code>{% my_tag %} ... {% endmy_tag %}</code> or <code>{% my_tag / %}</code></p> </li> </ul> <h4 id=refactor_3>Refactor<a class=headerlink href=#refactor_3 title="Permanent link">¤</a></h4> <ul> <li> <p>Refactored template tag input validation. When you now call template tags like <code>{% slot %}</code>, <code>{% fill %}</code>, <code>{% html_attrs %}</code>, and others, their inputs are now validated the same way as Python function inputs are.</p> <p>So, for example</p> <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;my_slot&quot;</span> <span class=nv>name</span><span class=o>=</span><span class=s2>&quot;content&quot;</span> <span class=o>/</span> <span class=cp>%}</span>
-</code></pre></div> <p>will raise an error, because the positional argument <code>name</code> is given twice.</p> <p>NOTE: Special kwargs whose keys are not valid Python variable names are not affected by this change. So when you define:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-1-1 name=__codelineno-1-1 href=#__codelineno-1-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=nv>data-id</span><span class=o>=</span><span class=m>123</span> <span class=o>/</span> <span class=cp>%}</span>
-</code></pre></div> <p>The <code>data-id</code> will still be accepted as a valid kwarg, assuming that your <code>get_context_data()</code> accepts <code>**kwargs</code>:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-2-1 name=__codelineno-2-1 href=#__codelineno-2-1></a><span class=k>def</span><span class=w> </span><span class=nf>get_context_data</span><span class=p>(</span><span class=bp>self</span><span class=p>,</span> <span class=o>**</span><span class=n>kwargs</span><span class=p>):</span>
-<a id=__codelineno-2-2 name=__codelineno-2-2 href=#__codelineno-2-2></a>    <span class=k>return</span> <span class=p>{</span>
-<a id=__codelineno-2-3 name=__codelineno-2-3 href=#__codelineno-2-3></a>        <span class=s2>&quot;data_id&quot;</span><span class=p>:</span> <span class=n>kwargs</span><span class=p>[</span><span class=s2>&quot;data-id&quot;</span><span class=p>],</span>
-<a id=__codelineno-2-4 name=__codelineno-2-4 href=#__codelineno-2-4></a>    <span class=p>}</span>
-</code></pre></div> </li> </ul> <h2 id=v0124>v0.124<a class=headerlink href=#v0124 title="Permanent link">¤</a></h2> <h4 id=feat_4>Feat<a class=headerlink href=#feat_4 title="Permanent link">¤</a></h4> <ul> <li> <p>Instead of inlining the JS and CSS under <code>Component.js</code> and <code>Component.css</code>, you can move them to their own files, and link the JS/CSS files with <code>Component.js_file</code> and <code>Component.css_file</code>.</p> <p>Even when you specify the JS/CSS with <code>Component.js_file</code> or <code>Component.css_file</code>, then you can still access the content under <code>Component.js</code> or <code>Component.css</code> - behind the scenes, the content of the JS/CSS files will be set to <code>Component.js</code> / <code>Component.css</code> upon first access.</p> <p>The same applies to <code>Component.template_file</code>, which will populate <code>Component.template</code> upon first access.</p> <p>With this change, the role of <code>Component.js/css</code> and the JS/CSS in <code>Component.Media</code> has changed:</p> <ul> <li>The JS/CSS defined in <code>Component.js/css</code> or <code>Component.js/css_file</code> is the "main" JS/CSS</li> <li>The JS/CSS defined in <code>Component.Media.js/css</code> are secondary or additional</li> </ul> <p>See the updated <a href=https://django-components.github.io/django-components/0.124/getting_started/adding_js_and_css/ >"Getting Started" tutorial</a></p> </li> </ul> <h4 id=refactor_4>Refactor<a class=headerlink href=#refactor_4 title="Permanent link">¤</a></h4> <ul> <li> <p>The canonical way to define a template file was changed from <code>template_name</code> to <code>template_file</code>, to align with the rest of the API.</p> <p><code>template_name</code> remains for backwards compatibility. When you get / set <code>template_name</code>, internally this is proxied to <code>template_file</code>.</p> </li> <li> <p>The undocumented <code>Component.component_id</code> was removed. Instead, use <code>Component.id</code>. Changes:</p> <ul> <li>While <code>component_id</code> was unique every time you instantiated <code>Component</code>, the new <code>id</code> is unique every time you render the component (e.g. with <code>Component.render()</code>)</li> <li>The new <code>id</code> is available only during render, so e.g. from within <code>get_context_data()</code></li> </ul> </li> <li> <p>Component's HTML / CSS / JS are now resolved and loaded lazily. That is, if you specify <code>template_name</code>/<code>template_file</code>, <code>js_file</code>, <code>css_file</code>, or <code>Media.js/css</code>, the file paths will be resolved only once you:</p> <ol> <li>Try to access component's HTML / CSS / JS, or</li> <li>Render the component.</li> </ol> <p>Read more on <a href=https://django-components.github.io/django-components/0.124/concepts/fundamentals/defining_js_css_html_files/#customize-how-paths-are-rendered-into-html-tags>Accessing component's HTML / JS / CSS</a>.</p> </li> <li> <p>Component inheritance:</p> <ul> <li>When you subclass a component, the JS and CSS defined on parent's <code>Media</code> class is now inherited by the child component.</li> <li>You can disable or customize Media inheritance by setting <code>extend</code> attribute on the <code>Component.Media</code> nested class. This work similarly to Django's <a href=https://docs.djangoproject.com/en/5.1/topics/forms/media/#extend><code>Media.extend</code></a>.</li> <li>When child component defines either <code>template</code> or <code>template_file</code>, both of parent's <code>template</code> and <code>template_file</code> are ignored. The same applies to <code>js_file</code> and <code>css_file</code>.</li> </ul> </li> <li> <p>Autodiscovery now ignores files and directories that start with an underscore (<code>_</code>), except <code>__init__.py</code></p> </li> <li> <p>The <a href=https://docs.djangoproject.com/en/5.1/topics/signals/ >Signals</a> emitted by or during the use of django-components are now documented, together the <code>template_rendered</code> signal.</p> </li> </ul> <h2 id=v0123>v0.123<a class=headerlink href=#v0123 title="Permanent link">¤</a></h2> <h4 id=fix_2>Fix<a class=headerlink href=#fix_2 title="Permanent link">¤</a></h4> <ul> <li>Fix edge cases around rendering components whose templates used the <code>{% extends %}</code> template tag (<a href=https://github.com/django-components/django-components/pull/859>#859</a>)</li> </ul> <h2 id=v0122>v0.122<a class=headerlink href=#v0122 title="Permanent link">¤</a></h2> <h4 id=feat_5>Feat<a class=headerlink href=#feat_5 title="Permanent link">¤</a></h4> <ul> <li>Add support for HTML fragments. HTML fragments can be rendered by passing <code>type="fragment"</code> to <code>Component.render()</code> or <code>Component.render_to_response()</code>. Read more on how to <a href=https://django-components.github.io/django-components/latest/concepts/advanced/html_tragments>use HTML fragments with HTMX, AlpineJS, or vanillaJS</a>.</li> </ul> <h2 id=v0121>v0.121<a class=headerlink href=#v0121 title="Permanent link">¤</a></h2> <h4 id=fix_3>Fix<a class=headerlink href=#fix_3 title="Permanent link">¤</a></h4> <ul> <li>Fix the use of Django template filters (<code>|lower:"etc"</code>) with component inputs <a href=https://github.com/django-components/django-components/pull/855>#855</a>.</li> </ul> <h2 id=v0120>v0.120<a class=headerlink href=#v0120 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.121 to fix bugs introduced in v0.119.</p> <h4 id=fix_4>Fix<a class=headerlink href=#fix_4 title="Permanent link">¤</a></h4> <ul> <li>Fix the use of translation strings <code>_("bla")</code> as inputs to components <a href=https://github.com/django-components/django-components/pull/849>#849</a>.</li> </ul> <h2 id=v0119>v0.119<a class=headerlink href=#v0119 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - This release introduced bugs <a href=https://github.com/django-components/django-components/pull/849>#849</a>, <a href=https://github.com/django-components/django-components/pull/855>#855</a>. Please update to v0.121.</p> <h4 id=fix_5>Fix<a class=headerlink href=#fix_5 title="Permanent link">¤</a></h4> <ul> <li>Fix compatibility with custom subclasses of Django's <code>Template</code> that need to access <code>origin</code> or other initialization arguments. (<a href=https://github.com/django-components/django-components/pull/828>https://github.com/django-components/django-components/pull/828</a>)</li> </ul> <h4 id=refactor_5>Refactor<a class=headerlink href=#refactor_5 title="Permanent link">¤</a></h4> <ul> <li>Compatibility with <code>django-debug-toolbar-template-profiler</code>:</li> <li> <p>Monkeypatching of Django's <code>Template</code> now happens at <code>AppConfig.ready()</code> (<a href=https://github.com/django-components/django-components/pull/825>https://github.com/django-components/django-components/pull/825</a>)</p> </li> <li> <p>Internal parsing of template tags tag was updated. No API change. (<a href=https://github.com/django-components/django-components/pull/827>https://github.com/django-components/django-components/pull/827</a>)</p> </li> </ul> <h2 id=v0118>v0.118<a class=headerlink href=#v0118 title="Permanent link">¤</a></h2> <h4 id=feat_6>Feat<a class=headerlink href=#feat_6 title="Permanent link">¤</a></h4> <ul> <li>Add support for <code>context_processors</code> and <code>RenderContext</code> inside component templates</li> </ul> <p><code>Component.render()</code> and <code>Component.render_to_response()</code> now accept an extra kwarg <code>request</code>.</p> <div class=codehilite><pre><span></span><code>```py
+<!doctype html><html lang=en class=no-js> <head><meta charset=utf-8><meta name=viewport content="width=device-width,initial-scale=1"><meta name=description content="A way to create simple reusable template components in Django."><link href=https://django-components.github.io/django-components/latest/release_notes/ rel=canonical><link href=../reference/testing_api/ rel=prev><link rel=icon href=../assets/images/favicon.png><meta name=generator content="mkdocs-1.6.1, mkdocs-material-9.6.9"><title>Release Notes - Django-Components</title><link rel=stylesheet href=../assets/stylesheets/main.4af4bdda.min.css><link rel=stylesheet href=../assets/stylesheets/palette.06af60db.min.css><link rel=preconnect href=https://fonts.gstatic.com crossorigin><link rel=stylesheet href="https://fonts.googleapis.com/css?family=Roboto:300,300i,400,400i,700,700i%7CRoboto+Mono:400,400i,700,700i&display=fallback"><style>:root{--md-text-font:"Roboto";--md-code-font:"Roboto Mono"}</style><link rel=stylesheet href=../assets/_markdown_exec_pyodide.css><link rel=stylesheet href=../assets/_mkdocstrings.css><link rel=stylesheet href=../css/timeago.css><link rel=stylesheet href=../css/style.css><script>__md_scope=new URL("..",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script><meta property=og:type content=website><meta property=og:title content="Release Notes - Django-Components"><meta property=og:description content="A way to create simple reusable template components in Django."><meta property=og:image content=https://django-components.github.io/django-components/latest/assets/images/social/release_notes.png><meta property=og:image:type content=image/png><meta property=og:image:width content=1200><meta property=og:image:height content=630><meta content=https://django-components.github.io/django-components/latest/release_notes/ property=og:url><meta name=twitter:card content=summary_large_image><meta name=twitter:title content="Release Notes - Django-Components"><meta name=twitter:description content="A way to create simple reusable template components in Django."><meta name=twitter:image content=https://django-components.github.io/django-components/latest/assets/images/social/release_notes.png></head> <body dir=ltr data-md-color-scheme=default data-md-color-primary=indigo data-md-color-accent=indigo> <input class=md-toggle data-md-toggle=drawer type=checkbox id=__drawer autocomplete=off> <input class=md-toggle data-md-toggle=search type=checkbox id=__search autocomplete=off> <label class=md-overlay for=__drawer></label> <div data-md-component=skip> <a href=#release-notes class=md-skip> Skip to content </a> </div> <div data-md-component=announce> </div> <div data-md-color-scheme=default data-md-component=outdated hidden> </div> <header class=md-header data-md-component=header> <nav class="md-header__inner md-grid" aria-label=Header> <a href=.. title=Django-Components class="md-header__button md-logo" aria-label=Django-Components data-md-component=logo> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 8a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3 3 3 0 0 0 3 3m0 3.54C9.64 9.35 6.5 8 3 8v11c3.5 0 6.64 1.35 9 3.54 2.36-2.19 5.5-3.54 9-3.54V8c-3.5 0-6.64 1.35-9 3.54"/></svg> </a> <label class="md-header__button md-icon" for=__drawer> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M3 6h18v2H3zm0 5h18v2H3zm0 5h18v2H3z"/></svg> </label> <div class=md-header__title data-md-component=header-title> <div class=md-header__ellipsis> <div class=md-header__topic> <span class=md-ellipsis> Django-Components </span> </div> <div class=md-header__topic data-md-component=header-topic> <span class=md-ellipsis> Release Notes </span> </div> </div> </div> <form class=md-header__option data-md-component=palette> <input class=md-option data-md-color-media=(prefers-color-scheme) data-md-color-scheme=default data-md-color-primary=indigo data-md-color-accent=indigo aria-label="Switch to light mode" type=radio name=__palette id=__palette_0> <label class="md-header__button md-icon" title="Switch to light mode" for=__palette_1 hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="m14.3 16-.7-2h-3.2l-.7 2H7.8L11 7h2l3.2 9zM20 8.69V4h-4.69L12 .69 8.69 4H4v4.69L.69 12 4 15.31V20h4.69L12 23.31 15.31 20H20v-4.69L23.31 12zm-9.15 3.96h2.3L12 9z"/></svg> </label> <input class=md-option data-md-color-media="(prefers-color-scheme: light)" data-md-color-scheme=default data-md-color-primary=teal data-md-color-accent=indigo aria-label="Switch to dark mode" type=radio name=__palette id=__palette_1> <label class="md-header__button md-icon" title="Switch to dark mode" for=__palette_2 hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="m17.75 4.09-2.53 1.94.91 3.06-2.63-1.81-2.63 1.81.91-3.06-2.53-1.94L12.44 4l1.06-3 1.06 3zm3.5 6.91-1.64 1.25.59 1.98-1.7-1.17-1.7 1.17.59-1.98L15.75 11l2.06-.05L18.5 9l.69 1.95zm-2.28 4.95c.83-.08 1.72 1.1 1.19 1.85-.32.45-.66.87-1.08 1.27C15.17 23 8.84 23 4.94 19.07c-3.91-3.9-3.91-10.24 0-14.14.4-.4.82-.76 1.27-1.08.75-.53 1.93.36 1.85 1.19-.27 2.86.69 5.83 2.89 8.02a9.96 9.96 0 0 0 8.02 2.89m-1.64 2.02a12.08 12.08 0 0 1-7.8-3.47c-2.17-2.19-3.33-5-3.49-7.82-2.81 3.14-2.7 7.96.31 10.98 3.02 3.01 7.84 3.12 10.98.31"/></svg> </label> <input class=md-option data-md-color-media="(prefers-color-scheme: dark)" data-md-color-scheme=slate data-md-color-primary=teal data-md-color-accent=indigo aria-label="Switch to light mode" type=radio name=__palette id=__palette_2> <label class="md-header__button md-icon" title="Switch to light mode" for=__palette_0 hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 7a5 5 0 0 1 5 5 5 5 0 0 1-5 5 5 5 0 0 1-5-5 5 5 0 0 1 5-5m0 2a3 3 0 0 0-3 3 3 3 0 0 0 3 3 3 3 0 0 0 3-3 3 3 0 0 0-3-3m0-7 2.39 3.42C13.65 5.15 12.84 5 12 5s-1.65.15-2.39.42zM3.34 7l4.16-.35A7.2 7.2 0 0 0 5.94 8.5c-.44.74-.69 1.5-.83 2.29zm.02 10 1.76-3.77a7.131 7.131 0 0 0 2.38 4.14zM20.65 7l-1.77 3.79a7.02 7.02 0 0 0-2.38-4.15zm-.01 10-4.14.36c.59-.51 1.12-1.14 1.54-1.86.42-.73.69-1.5.83-2.29zM12 22l-2.41-3.44c.74.27 1.55.44 2.41.44.82 0 1.63-.17 2.37-.44z"/></svg> </label> </form> <script>var palette=__md_get("__palette");if(palette&&palette.color){if("(prefers-color-scheme)"===palette.color.media){var media=matchMedia("(prefers-color-scheme: light)"),input=document.querySelector(media.matches?"[data-md-color-media='(prefers-color-scheme: light)']":"[data-md-color-media='(prefers-color-scheme: dark)']");palette.color.media=input.getAttribute("data-md-color-media"),palette.color.scheme=input.getAttribute("data-md-color-scheme"),palette.color.primary=input.getAttribute("data-md-color-primary"),palette.color.accent=input.getAttribute("data-md-color-accent")}for(var[key,value]of Object.entries(palette.color))document.body.setAttribute("data-md-color-"+key,value)}</script> <label class="md-header__button md-icon" for=__search> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg> </label> <div class=md-search data-md-component=search role=dialog> <label class=md-search__overlay for=__search></label> <div class=md-search__inner role=search> <form class=md-search__form name=search> <input type=text class=md-search__input name=query aria-label=Search placeholder=Search autocapitalize=off autocorrect=off autocomplete=off spellcheck=false data-md-component=search-query required> <label class="md-search__icon md-icon" for=__search> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg> </label> <nav class=md-search__options aria-label=Search> <a href=javascript:void(0) class="md-search__icon md-icon" title=Share aria-label=Share data-clipboard data-clipboard-text data-md-component=search-share tabindex=-1> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M18 16.08c-.76 0-1.44.3-1.96.77L8.91 12.7c.05-.23.09-.46.09-.7s-.04-.47-.09-.7l7.05-4.11c.54.5 1.25.81 2.04.81a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3c0 .24.04.47.09.7L8.04 9.81C7.5 9.31 6.79 9 6 9a3 3 0 0 0-3 3 3 3 0 0 0 3 3c.79 0 1.5-.31 2.04-.81l7.12 4.15c-.05.21-.08.43-.08.66 0 1.61 1.31 2.91 2.92 2.91s2.92-1.3 2.92-2.91A2.92 2.92 0 0 0 18 16.08"/></svg> </a> <button type=reset class="md-search__icon md-icon" title=Clear aria-label=Clear tabindex=-1> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M19 6.41 17.59 5 12 10.59 6.41 5 5 6.41 10.59 12 5 17.59 6.41 19 12 13.41 17.59 19 19 17.59 13.41 12z"/></svg> </button> </nav> <div class=md-search__suggest data-md-component=search-suggest></div> </form> <div class=md-search__output> <div class=md-search__scrollwrap tabindex=0 data-md-scrollfix> <div class=md-search-result data-md-component=search-result> <div class=md-search-result__meta> Initializing search </div> <ol class=md-search-result__list role=presentation></ol> </div> </div> </div> </div> </div> <div class=md-header__source> <a href=https://github.com/django-components/django-components title="Go to repository" class=md-source data-md-component=source> <div class="md-source__icon md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </div> <div class=md-source__repository> django-components/django-components </div> </a> </div> </nav> </header> <div class=md-container data-md-component=container> <nav class=md-tabs aria-label=Tabs data-md-component=tabs> <div class=md-grid> <ul class=md-tabs__list> <li class=md-tabs__item> <a href=../overview/welcome/ class=md-tabs__link> Overview </a> </li> <li class=md-tabs__item> <a href=../getting_started/your_first_component/ class=md-tabs__link> Getting Started </a> </li> <li class=md-tabs__item> <a href=../concepts/fundamentals/single_file_components/ class=md-tabs__link> Concepts </a> </li> <li class=md-tabs__item> <a href=../guides/setup/syntax_highlight/ class=md-tabs__link> Guides </a> </li> <li class=md-tabs__item> <a href=../reference/api/ class=md-tabs__link> API Documentation </a> </li> <li class="md-tabs__item md-tabs__item--active"> <a href=./ class=md-tabs__link> Release Notes </a> </li> </ul> </div> </nav> <main class=md-main data-md-component=main> <div class="md-main__inner md-grid"> <div class="md-sidebar md-sidebar--primary" data-md-component=sidebar data-md-type=navigation> <div class=md-sidebar__scrollwrap> <div class=md-sidebar__inner> <nav class="md-nav md-nav--primary md-nav--lifted" aria-label=Navigation data-md-level=0> <label class=md-nav__title for=__drawer> <a href=.. title=Django-Components class="md-nav__button md-logo" aria-label=Django-Components data-md-component=logo> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 8a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3 3 3 0 0 0 3 3m0 3.54C9.64 9.35 6.5 8 3 8v11c3.5 0 6.64 1.35 9 3.54 2.36-2.19 5.5-3.54 9-3.54V8c-3.5 0-6.64 1.35-9 3.54"/></svg> </a> Django-Components </label> <div class=md-nav__source> <a href=https://github.com/django-components/django-components title="Go to repository" class=md-source data-md-component=source> <div class="md-source__icon md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </div> <div class=md-source__repository> django-components/django-components </div> </a> </div> <ul class=md-nav__list data-md-scrollfix> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_1> <label class=md-nav__link for=__nav_1 id=__nav_1_label tabindex=0> <span class=md-ellipsis> Overview </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_1_label aria-expanded=false> <label class=md-nav__title for=__nav_1> <span class="md-nav__icon md-icon"></span> Overview </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../overview/welcome/ class=md-nav__link> <span class=md-ellipsis> Welcome to Django Components </span> </a> </li> <li class=md-nav__item> <a href=../overview/compatibility/ class=md-nav__link> <span class=md-ellipsis> Compatibility </span> </a> </li> <li class=md-nav__item> <a href=../overview/installation/ class=md-nav__link> <span class=md-ellipsis> Installation </span> </a> </li> <li class=md-nav__item> <a href=../overview/security_notes/ class=md-nav__link> <span class=md-ellipsis> Security notes 🚨 </span> </a> </li> <li class=md-nav__item> <a href=../overview/community/ class=md-nav__link> <span class=md-ellipsis> Community </span> </a> </li> <li class=md-nav__item> <a href=../overview/contributing/ class=md-nav__link> <span class=md-ellipsis> Contributing </span> </a> </li> <li class=md-nav__item> <a href=../overview/development/ class=md-nav__link> <span class=md-ellipsis> Development </span> </a> </li> <li class=md-nav__item> <a href=../overview/performance/ class=md-nav__link> <span class=md-ellipsis> Performance </span> </a> </li> <li class=md-nav__item> <a href=../overview/code_of_conduct/ class=md-nav__link> <span class=md-ellipsis> Code of Conduct </span> </a> </li> <li class=md-nav__item> <a href=../overview/license/ class=md-nav__link> <span class=md-ellipsis> License </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_2> <label class=md-nav__link for=__nav_2 id=__nav_2_label tabindex=0> <span class=md-ellipsis> Getting Started </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_2_label aria-expanded=false> <label class=md-nav__title for=__nav_2> <span class="md-nav__icon md-icon"></span> Getting Started </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../getting_started/your_first_component/ class=md-nav__link> <span class=md-ellipsis> Create your first component </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/adding_js_and_css/ class=md-nav__link> <span class=md-ellipsis> Adding JS and CSS </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/components_in_templates/ class=md-nav__link> <span class=md-ellipsis> Components in templates </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/parametrising_components/ class=md-nav__link> <span class=md-ellipsis> Parametrising components </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/adding_slots/ class=md-nav__link> <span class=md-ellipsis> Adding slots </span> </a> </li> <li class=md-nav__item> <a href=../getting_started/rendering_components/ class=md-nav__link> <span class=md-ellipsis> Rendering components </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_3> <label class=md-nav__link for=__nav_3 id=__nav_3_label tabindex=0> <span class=md-ellipsis> Concepts </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_3_label aria-expanded=false> <label class=md-nav__title for=__nav_3> <span class="md-nav__icon md-icon"></span> Concepts </label> <ul class=md-nav__list data-md-scrollfix> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_3_1> <label class=md-nav__link for=__nav_3_1 id=__nav_3_1_label tabindex=0> <span class=md-ellipsis> Fundamentals </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_3_1_label aria-expanded=false> <label class=md-nav__title for=__nav_3_1> <span class="md-nav__icon md-icon"></span> Fundamentals </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../concepts/fundamentals/single_file_components/ class=md-nav__link> <span class=md-ellipsis> Single-file components </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/components_in_python/ class=md-nav__link> <span class=md-ellipsis> Components in Python </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/access_component_input/ class=md-nav__link> <span class=md-ellipsis> Accessing component inputs </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/component_context_scope/ class=md-nav__link> <span class=md-ellipsis> Component context and scope </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/template_tag_syntax/ class=md-nav__link> <span class=md-ellipsis> Template tag syntax </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/slots/ class=md-nav__link> <span class=md-ellipsis> Slots </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/html_attributes/ class=md-nav__link> <span class=md-ellipsis> HTML attributes </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/defining_js_css_html_files/ class=md-nav__link> <span class=md-ellipsis> Defining HTML / JS / CSS files </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/autodiscovery/ class=md-nav__link> <span class=md-ellipsis> Autodiscovery </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/components_as_views/ class=md-nav__link> <span class=md-ellipsis> Components as views </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/http_request/ class=md-nav__link> <span class=md-ellipsis> HTTP Request </span> </a> </li> <li class=md-nav__item> <a href=../concepts/fundamentals/subclassing_components/ class=md-nav__link> <span class=md-ellipsis> Subclassing components </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_3_2> <label class=md-nav__link for=__nav_3_2 id=__nav_3_2_label tabindex=0> <span class=md-ellipsis> Advanced </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_3_2_label aria-expanded=false> <label class=md-nav__title for=__nav_3_2> <span class="md-nav__icon md-icon"></span> Advanced </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../concepts/advanced/rendering_js_css/ class=md-nav__link> <span class=md-ellipsis> Rendering JS / CSS </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/html_fragments/ class=md-nav__link> <span class=md-ellipsis> HTML fragments </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/provide_inject/ class=md-nav__link> <span class=md-ellipsis> Prop drilling and provide / inject </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/hooks/ class=md-nav__link> <span class=md-ellipsis> Lifecycle hooks </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/component_registry/ class=md-nav__link> <span class=md-ellipsis> Registering components </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/typing_and_validation/ class=md-nav__link> <span class=md-ellipsis> Typing and validation </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/template_tags/ class=md-nav__link> <span class=md-ellipsis> Custom template tags </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/tag_formatter/ class=md-nav__link> <span class=md-ellipsis> Tag formatters </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/extensions/ class=md-nav__link> <span class=md-ellipsis> Extensions </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/testing/ class=md-nav__link> <span class=md-ellipsis> Testing </span> </a> </li> <li class=md-nav__item> <a href=../concepts/advanced/authoring_component_libraries/ class=md-nav__link> <span class=md-ellipsis> Authoring component libraries </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_4> <label class=md-nav__link for=__nav_4 id=__nav_4_label tabindex=0> <span class=md-ellipsis> Guides </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_4_label aria-expanded=false> <label class=md-nav__title for=__nav_4> <span class="md-nav__icon md-icon"></span> Guides </label> <ul class=md-nav__list data-md-scrollfix> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_4_1> <label class=md-nav__link for=__nav_4_1 id=__nav_4_1_label tabindex=0> <span class=md-ellipsis> Setup </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_4_1_label aria-expanded=false> <label class=md-nav__title for=__nav_4_1> <span class="md-nav__icon md-icon"></span> Setup </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../guides/setup/syntax_highlight/ class=md-nav__link> <span class=md-ellipsis> Syntax highlighting </span> </a> </li> <li class=md-nav__item> <a href=../guides/setup/caching/ class=md-nav__link> <span class=md-ellipsis> Caching </span> </a> </li> <li class=md-nav__item> <a href=../guides/setup/development_server/ class=md-nav__link> <span class=md-ellipsis> Development server </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_4_2> <label class=md-nav__link for=__nav_4_2 id=__nav_4_2_label tabindex=0> <span class=md-ellipsis> Other </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_4_2_label aria-expanded=false> <label class=md-nav__title for=__nav_4_2> <span class="md-nav__icon md-icon"></span> Other </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../guides/other/troubleshooting/ class=md-nav__link> <span class=md-ellipsis> Troubleshooting </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_4_3> <label class=md-nav__link for=__nav_4_3 id=__nav_4_3_label tabindex=0> <span class=md-ellipsis> Dev Guides </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=2 aria-labelledby=__nav_4_3_label aria-expanded=false> <label class=md-nav__title for=__nav_4_3> <span class="md-nav__icon md-icon"></span> Dev Guides </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../guides/devguides/dependency_mgmt/ class=md-nav__link> <span class=md-ellipsis> JS and CSS rendering </span> </a> </li> <li class=md-nav__item> <a href=../guides/devguides/slot_rendering/ class=md-nav__link> <span class=md-ellipsis> Slot rendering </span> </a> </li> <li class=md-nav__item> <a href=../guides/devguides/slots_and_blocks/ class=md-nav__link> <span class=md-ellipsis> Using slot and block tags </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle md-toggle--indeterminate" type=checkbox id=__nav_5> <label class=md-nav__link for=__nav_5 id=__nav_5_label tabindex=0> <span class=md-ellipsis> API Documentation </span> <span class="md-nav__icon md-icon"></span> </label> <nav class=md-nav data-md-level=1 aria-labelledby=__nav_5_label aria-expanded=false> <label class=md-nav__title for=__nav_5> <span class="md-nav__icon md-icon"></span> API Documentation </label> <ul class=md-nav__list data-md-scrollfix> <li class=md-nav__item> <a href=../reference/api/ class=md-nav__link> <span class=md-ellipsis> API </span> </a> </li> <li class=md-nav__item> <a href=../reference/commands/ class=md-nav__link> <span class=md-ellipsis> Commands </span> </a> </li> <li class=md-nav__item> <a href=../reference/components/ class=md-nav__link> <span class=md-ellipsis> Components </span> </a> </li> <li class=md-nav__item> <a href=../reference/exceptions/ class=md-nav__link> <span class=md-ellipsis> Exceptions </span> </a> </li> <li class=md-nav__item> <a href=../reference/extension_hooks/ class=md-nav__link> <span class=md-ellipsis> Extension hooks </span> </a> </li> <li class=md-nav__item> <a href=../reference/middlewares/ class=md-nav__link> <span class=md-ellipsis> Middlewares </span> </a> </li> <li class=md-nav__item> <a href=../reference/settings/ class=md-nav__link> <span class=md-ellipsis> Settings </span> </a> </li> <li class=md-nav__item> <a href=../reference/signals/ class=md-nav__link> <span class=md-ellipsis> Signals </span> </a> </li> <li class=md-nav__item> <a href=../reference/tag_formatters/ class=md-nav__link> <span class=md-ellipsis> Tag formatters </span> </a> </li> <li class=md-nav__item> <a href=../reference/template_tags/ class=md-nav__link> <span class=md-ellipsis> Template tags </span> </a> </li> <li class=md-nav__item> <a href=../reference/template_vars/ class=md-nav__link> <span class=md-ellipsis> Template vars </span> </a> </li> <li class=md-nav__item> <a href=../reference/urls/ class=md-nav__link> <span class=md-ellipsis> URLs </span> </a> </li> <li class=md-nav__item> <a href=../reference/testing_api/ class=md-nav__link> <span class=md-ellipsis> Testing API </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--active"> <input class="md-nav__toggle md-toggle" type=checkbox id=__toc> <label class="md-nav__link md-nav__link--active" for=__toc> <span class=md-ellipsis> Release Notes </span> <span class="md-nav__icon md-icon"></span> </label> <a href=./ class="md-nav__link md-nav__link--active"> <span class=md-ellipsis> Release Notes </span> </a> <nav class="md-nav md-nav--secondary" aria-label="Table of contents"> <label class=md-nav__title for=__toc> <span class="md-nav__icon md-icon"></span> Table of contents </label> <ul class=md-nav__list data-md-component=toc data-md-scrollfix> <li class=md-nav__item> <a href=#v0132 class=md-nav__link> <span class=md-ellipsis> v0.132 </span> </a> <nav class=md-nav aria-label=v0.132> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0131 class=md-nav__link> <span class=md-ellipsis> v0.131 </span> </a> <nav class=md-nav aria-label=v0.131> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_1 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> <li class=md-nav__item> <a href=#internal class=md-nav__link> <span class=md-ellipsis> Internal </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0130 class=md-nav__link> <span class=md-ellipsis> v0.130 </span> </a> <nav class=md-nav aria-label=v0.130> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_2 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0129 class=md-nav__link> <span class=md-ellipsis> v0.129 </span> </a> <nav class=md-nav aria-label=v0.129> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0128 class=md-nav__link> <span class=md-ellipsis> v0.128 </span> </a> <nav class=md-nav aria-label=v0.128> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_3 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_1 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> <li class=md-nav__item> <a href=#perf class=md-nav__link> <span class=md-ellipsis> Perf </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0127 class=md-nav__link> <span class=md-ellipsis> v0.127 </span> </a> <nav class=md-nav aria-label=v0.127> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_1 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0126 class=md-nav__link> <span class=md-ellipsis> v0.126 </span> </a> <nav class=md-nav aria-label=v0.126> <ul class=md-nav__list> <li class=md-nav__item> <a href=#refactor_2 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0125 class=md-nav__link> <span class=md-ellipsis> v0.125 </span> </a> <nav class=md-nav aria-label=v0.125> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_4 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_3 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0124 class=md-nav__link> <span class=md-ellipsis> v0.124 </span> </a> <nav class=md-nav aria-label=v0.124> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_5 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_4 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0123 class=md-nav__link> <span class=md-ellipsis> v0.123 </span> </a> <nav class=md-nav aria-label=v0.123> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_2 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0122 class=md-nav__link> <span class=md-ellipsis> v0.122 </span> </a> <nav class=md-nav aria-label=v0.122> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_6 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0121 class=md-nav__link> <span class=md-ellipsis> v0.121 </span> </a> <nav class=md-nav aria-label=v0.121> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_3 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0120 class=md-nav__link> <span class=md-ellipsis> v0.120 </span> </a> <nav class=md-nav aria-label=v0.120> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_4 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0119 class=md-nav__link> <span class=md-ellipsis> v0.119 </span> </a> <nav class=md-nav aria-label=v0.119> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_5 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_5 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0118 class=md-nav__link> <span class=md-ellipsis> v0.118 </span> </a> <nav class=md-nav aria-label=v0.118> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_7 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0117 class=md-nav__link> <span class=md-ellipsis> v0.117 </span> </a> <nav class=md-nav aria-label=v0.117> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_6 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_6 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0116 class=md-nav__link> <span class=md-ellipsis> v0.116 </span> </a> <nav class=md-nav aria-label=v0.116> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_7 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0115 class=md-nav__link> <span class=md-ellipsis> v0.115 </span> </a> <nav class=md-nav aria-label=v0.115> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_8 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0114 class=md-nav__link> <span class=md-ellipsis> v0.114 </span> </a> <nav class=md-nav aria-label=v0.114> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_9 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0113 class=md-nav__link> <span class=md-ellipsis> v0.113 </span> </a> <nav class=md-nav aria-label=v0.113> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_10 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0112 class=md-nav__link> <span class=md-ellipsis> v0.112 </span> </a> <nav class=md-nav aria-label=v0.112> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_11 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0111 class=md-nav__link> <span class=md-ellipsis> v0.111 </span> </a> <nav class=md-nav aria-label=v0.111> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_12 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0110 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.110 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.110"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#general class=md-nav__link> <span class=md-ellipsis> General </span> </a> <nav class=md-nav aria-label=General> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes class=md-nav__link> <span class=md-ellipsis> 🚨📢 BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_8 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_7 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#tags class=md-nav__link> <span class=md-ellipsis> Tags </span> </a> <nav class=md-nav aria-label=Tags> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_1 class=md-nav__link> <span class=md-ellipsis> 🚨📢 BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#fix_13 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_8 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#slots class=md-nav__link> <span class=md-ellipsis> Slots </span> </a> <nav class=md-nav aria-label=Slots> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_9 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#fix_14 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_9 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0100 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.100 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.100"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_2 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_10 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_10 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v097 class=md-nav__link> <span class=md-ellipsis> v0.97 </span> </a> <nav class=md-nav aria-label=v0.97> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_15 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_11 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v096 class=md-nav__link> <span class=md-ellipsis> v0.96 </span> </a> <nav class=md-nav aria-label=v0.96> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_11 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#095 class=md-nav__link> <span class=md-ellipsis> 0.95 </span> </a> <nav class=md-nav aria-label=0.95> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_12 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_12 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v094 class=md-nav__link> <span class=md-ellipsis> v0.94 </span> </a> <nav class=md-nav aria-label=v0.94> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_13 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v093 class=md-nav__link> <span class=md-ellipsis> v0.93 </span> </a> <nav class=md-nav aria-label=v0.93> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_14 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v092 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.92 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.92"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_3 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_15 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v090 class=md-nav__link> <span class=md-ellipsis> v0.90 </span> </a> <nav class=md-nav aria-label=v0.90> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_16 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v085 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.85 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.85"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_4 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v081 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.81 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.81"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_5 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_17 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v080 class=md-nav__link> <span class=md-ellipsis> v0.80 </span> </a> <nav class=md-nav aria-label=v0.80> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_18 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v079 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.79 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.79"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_6 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v077 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.77 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.77"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking class=md-nav__link> <span class=md-ellipsis> BREAKING </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v074 class=md-nav__link> <span class=md-ellipsis> v0.74 </span> </a> <nav class=md-nav aria-label=v0.74> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_19 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v070 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.70 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.70"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_7 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v067 class=md-nav__link> <span class=md-ellipsis> v0.67 </span> </a> <nav class=md-nav aria-label=v0.67> <ul class=md-nav__list> <li class=md-nav__item> <a href=#refactor_13 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v050 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.50 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.50"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_8 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v034 class=md-nav__link> <span class=md-ellipsis> v0.34 </span> </a> <nav class=md-nav aria-label=v0.34> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_20 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v028 class=md-nav__link> <span class=md-ellipsis> v0.28 </span> </a> <nav class=md-nav aria-label=v0.28> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_21 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v027 class=md-nav__link> <span class=md-ellipsis> v0.27 </span> </a> <nav class=md-nav aria-label=v0.27> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_22 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v026 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.26 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.26"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_9 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v022 class=md-nav__link> <span class=md-ellipsis> v0.22 </span> </a> <nav class=md-nav aria-label=v0.22> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_23 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v017 class=md-nav__link> <span class=md-ellipsis> v0.17 </span> </a> <nav class=md-nav aria-label=v0.17> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_10 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> </ul> </nav> </div> </div> </div> <div class="md-sidebar md-sidebar--secondary" data-md-component=sidebar data-md-type=toc> <div class=md-sidebar__scrollwrap> <div class=md-sidebar__inner> <nav class="md-nav md-nav--secondary" aria-label="Table of contents"> <label class=md-nav__title for=__toc> <span class="md-nav__icon md-icon"></span> Table of contents </label> <ul class=md-nav__list data-md-component=toc data-md-scrollfix> <li class=md-nav__item> <a href=#v0132 class=md-nav__link> <span class=md-ellipsis> v0.132 </span> </a> <nav class=md-nav aria-label=v0.132> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0131 class=md-nav__link> <span class=md-ellipsis> v0.131 </span> </a> <nav class=md-nav aria-label=v0.131> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_1 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> <li class=md-nav__item> <a href=#internal class=md-nav__link> <span class=md-ellipsis> Internal </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0130 class=md-nav__link> <span class=md-ellipsis> v0.130 </span> </a> <nav class=md-nav aria-label=v0.130> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_2 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0129 class=md-nav__link> <span class=md-ellipsis> v0.129 </span> </a> <nav class=md-nav aria-label=v0.129> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0128 class=md-nav__link> <span class=md-ellipsis> v0.128 </span> </a> <nav class=md-nav aria-label=v0.128> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_3 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_1 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> <li class=md-nav__item> <a href=#perf class=md-nav__link> <span class=md-ellipsis> Perf </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0127 class=md-nav__link> <span class=md-ellipsis> v0.127 </span> </a> <nav class=md-nav aria-label=v0.127> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_1 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0126 class=md-nav__link> <span class=md-ellipsis> v0.126 </span> </a> <nav class=md-nav aria-label=v0.126> <ul class=md-nav__list> <li class=md-nav__item> <a href=#refactor_2 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0125 class=md-nav__link> <span class=md-ellipsis> v0.125 </span> </a> <nav class=md-nav aria-label=v0.125> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_4 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_3 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0124 class=md-nav__link> <span class=md-ellipsis> v0.124 </span> </a> <nav class=md-nav aria-label=v0.124> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_5 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_4 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0123 class=md-nav__link> <span class=md-ellipsis> v0.123 </span> </a> <nav class=md-nav aria-label=v0.123> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_2 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0122 class=md-nav__link> <span class=md-ellipsis> v0.122 </span> </a> <nav class=md-nav aria-label=v0.122> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_6 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0121 class=md-nav__link> <span class=md-ellipsis> v0.121 </span> </a> <nav class=md-nav aria-label=v0.121> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_3 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0120 class=md-nav__link> <span class=md-ellipsis> v0.120 </span> </a> <nav class=md-nav aria-label=v0.120> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_4 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0119 class=md-nav__link> <span class=md-ellipsis> v0.119 </span> </a> <nav class=md-nav aria-label=v0.119> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_5 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_5 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0118 class=md-nav__link> <span class=md-ellipsis> v0.118 </span> </a> <nav class=md-nav aria-label=v0.118> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_7 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0117 class=md-nav__link> <span class=md-ellipsis> v0.117 </span> </a> <nav class=md-nav aria-label=v0.117> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_6 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_6 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0116 class=md-nav__link> <span class=md-ellipsis> v0.116 </span> </a> <nav class=md-nav aria-label=v0.116> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_7 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0115 class=md-nav__link> <span class=md-ellipsis> v0.115 </span> </a> <nav class=md-nav aria-label=v0.115> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_8 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0114 class=md-nav__link> <span class=md-ellipsis> v0.114 </span> </a> <nav class=md-nav aria-label=v0.114> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_9 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0113 class=md-nav__link> <span class=md-ellipsis> v0.113 </span> </a> <nav class=md-nav aria-label=v0.113> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_10 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0112 class=md-nav__link> <span class=md-ellipsis> v0.112 </span> </a> <nav class=md-nav aria-label=v0.112> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_11 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0111 class=md-nav__link> <span class=md-ellipsis> v0.111 </span> </a> <nav class=md-nav aria-label=v0.111> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_12 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0110 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.110 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.110"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#general class=md-nav__link> <span class=md-ellipsis> General </span> </a> <nav class=md-nav aria-label=General> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes class=md-nav__link> <span class=md-ellipsis> 🚨📢 BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_8 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_7 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#tags class=md-nav__link> <span class=md-ellipsis> Tags </span> </a> <nav class=md-nav aria-label=Tags> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_1 class=md-nav__link> <span class=md-ellipsis> 🚨📢 BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#fix_13 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_8 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#slots class=md-nav__link> <span class=md-ellipsis> Slots </span> </a> <nav class=md-nav aria-label=Slots> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_9 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#fix_14 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_9 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v0100 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.100 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.100"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_2 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_10 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_10 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v097 class=md-nav__link> <span class=md-ellipsis> v0.97 </span> </a> <nav class=md-nav aria-label=v0.97> <ul class=md-nav__list> <li class=md-nav__item> <a href=#fix_15 class=md-nav__link> <span class=md-ellipsis> Fix </span> </a> </li> <li class=md-nav__item> <a href=#refactor_11 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v096 class=md-nav__link> <span class=md-ellipsis> v0.96 </span> </a> <nav class=md-nav aria-label=v0.96> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_11 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#095 class=md-nav__link> <span class=md-ellipsis> 0.95 </span> </a> <nav class=md-nav aria-label=0.95> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_12 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> <li class=md-nav__item> <a href=#refactor_12 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v094 class=md-nav__link> <span class=md-ellipsis> v0.94 </span> </a> <nav class=md-nav aria-label=v0.94> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_13 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v093 class=md-nav__link> <span class=md-ellipsis> v0.93 </span> </a> <nav class=md-nav aria-label=v0.93> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_14 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v092 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.92 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.92"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_3 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_15 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v090 class=md-nav__link> <span class=md-ellipsis> v0.90 </span> </a> <nav class=md-nav aria-label=v0.90> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_16 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v085 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.85 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.85"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_4 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v081 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.81 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.81"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_5 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> <li class=md-nav__item> <a href=#feat_17 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v080 class=md-nav__link> <span class=md-ellipsis> v0.80 </span> </a> <nav class=md-nav aria-label=v0.80> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_18 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v079 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.79 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.79"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_6 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v077 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.77 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.77"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking class=md-nav__link> <span class=md-ellipsis> BREAKING </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v074 class=md-nav__link> <span class=md-ellipsis> v0.74 </span> </a> <nav class=md-nav aria-label=v0.74> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_19 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v070 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.70 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.70"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_7 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v067 class=md-nav__link> <span class=md-ellipsis> v0.67 </span> </a> <nav class=md-nav aria-label=v0.67> <ul class=md-nav__list> <li class=md-nav__item> <a href=#refactor_13 class=md-nav__link> <span class=md-ellipsis> Refactor </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v050 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.50 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.50"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_8 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v034 class=md-nav__link> <span class=md-ellipsis> v0.34 </span> </a> <nav class=md-nav aria-label=v0.34> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_20 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v028 class=md-nav__link> <span class=md-ellipsis> v0.28 </span> </a> <nav class=md-nav aria-label=v0.28> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_21 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v027 class=md-nav__link> <span class=md-ellipsis> v0.27 </span> </a> <nav class=md-nav aria-label=v0.27> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_22 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v026 class=md-nav__link> <span class=md-ellipsis> 🚨📢 v0.26 </span> </a> <nav class=md-nav aria-label="🚨📢 v0.26"> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_9 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v022 class=md-nav__link> <span class=md-ellipsis> v0.22 </span> </a> <nav class=md-nav aria-label=v0.22> <ul class=md-nav__list> <li class=md-nav__item> <a href=#feat_23 class=md-nav__link> <span class=md-ellipsis> Feat </span> </a> </li> </ul> </nav> </li> <li class=md-nav__item> <a href=#v017 class=md-nav__link> <span class=md-ellipsis> v0.17 </span> </a> <nav class=md-nav aria-label=v0.17> <ul class=md-nav__list> <li class=md-nav__item> <a href=#breaking-changes_10 class=md-nav__link> <span class=md-ellipsis> BREAKING CHANGES </span> </a> </li> </ul> </nav> </li> </ul> </nav> </div> </div> </div> <div class=md-content data-md-component=content> <article class="md-content__inner md-typeset"> <a href=https://github.com/django-components/django-components/edit/master/docs/release_notes.md title="Edit this page" class="md-content__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4zm10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1z"/></svg> </a> <a href=https://github.com/django-components/django-components/raw/master/docs/release_notes.md title="View source of this page" class="md-content__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M17 18c.56 0 1 .44 1 1s-.44 1-1 1-1-.44-1-1 .44-1 1-1m0-3c-2.73 0-5.06 1.66-6 4 .94 2.34 3.27 4 6 4s5.06-1.66 6-4c-.94-2.34-3.27-4-6-4m0 6.5a2.5 2.5 0 0 1-2.5-2.5 2.5 2.5 0 0 1 2.5-2.5 2.5 2.5 0 0 1 2.5 2.5 2.5 2.5 0 0 1-2.5 2.5M9.27 20H6V4h7v5h5v4.07c.7.08 1.36.25 2 .49V8l-6-6H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h4.5a8.2 8.2 0 0 1-1.23-2"/></svg> </a> <h1 id=release-notes>Release notes<a class=headerlink href=#release-notes title="Permanent link">¤</a></h1> <h2 id=v0132>v0.132<a class=headerlink href=#v0132 title="Permanent link">¤</a></h2> <h4 id=feat>Feat<a class=headerlink href=#feat title="Permanent link">¤</a></h4> <ul> <li> <p>Allow to use glob patterns as paths for additional JS / CSS in <code>Component.Media.js</code> and <code>Component.Media.css</code></p> <div class=highlight><pre><span></span><code><a id=__codelineno-0-1 name=__codelineno-0-1 href=#__codelineno-0-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyComponent</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
+<a id=__codelineno-0-2 name=__codelineno-0-2 href=#__codelineno-0-2></a>    <span class=k>class</span><span class=w> </span><span class=nc>Media</span><span class=p>:</span>
+<a id=__codelineno-0-3 name=__codelineno-0-3 href=#__codelineno-0-3></a>        <span class=n>js</span> <span class=o>=</span> <span class=p>[</span><span class=s2>&quot;*.js&quot;</span><span class=p>]</span>
+<a id=__codelineno-0-4 name=__codelineno-0-4 href=#__codelineno-0-4></a>        <span class=n>css</span> <span class=o>=</span> <span class=p>[</span><span class=s2>&quot;*.css&quot;</span><span class=p>]</span>
+</code></pre></div> </li> </ul> <h2 id=v0131>v0.131<a class=headerlink href=#v0131 title="Permanent link">¤</a></h2> <h4 id=feat_1>Feat<a class=headerlink href=#feat_1 title="Permanent link">¤</a></h4> <ul> <li> <p>Support for extensions (plugins) for django-components!</p> <ul> <li>Hook into lifecycle events of django-components</li> <li>Pre-/post-process component inputs, outputs, and templates</li> <li>Add extra methods or attributes to Components</li> <li>Add custom extension-specific CLI commands</li> <li>Add custom extension-specific URL routes</li> </ul> <p>Read more on <a href=https://django-components.github.io/django-components/0.131/concepts/advanced/extensions/ >Extensions</a>.</p> </li> <li> <p>New CLI commands:</p> <ul> <li><code>components list</code> - List all components</li> <li><code>components create &lt;name&gt;</code> - Create a new component (supersedes <code>startcomponent</code>)</li> <li><code>components upgrade</code> - Upgrade a component (supersedes <code>upgradecomponent</code>)</li> <li><code>components ext list</code> - List all extensions</li> <li><code>components ext run &lt;extension&gt; &lt;command&gt;</code> - Run a command added by an extension</li> </ul> </li> <li> <p><code>@djc_test</code> decorator for writing tests that involve Components.</p> <ul> <li>The decorator manages global state, ensuring that tests don't leak.</li> <li>If using <code>pytest</code>, the decorator allows you to parametrize Django or Components settings.</li> <li>The decorator also serves as a stand-in for Django's <code>@override_settings</code>.</li> </ul> <p>See the API reference for <a href=https://django-components.github.io/django-components/0.131/reference/testing_api/#djc_test><code>@djc_test</code></a> for more details.</p> </li> <li> <p><code>ComponentRegistry</code> now has a <code>has()</code> method to check if a component is registered without raising an error.</p> </li> <li> <p>Get all created <code>Component</code> classes with <code>all_components()</code>.</p> </li> <li> <p>Get all created <code>ComponentRegistry</code> instances with <code>all_registries()</code>.</p> </li> </ul> <h4 id=refactor>Refactor<a class=headerlink href=#refactor title="Permanent link">¤</a></h4> <ul> <li> <p>The <code>startcomponent</code> and <code>upgradecomponent</code> commands are deprecated, and will be removed in v1.</p> <p>Instead, use <code>components create &lt;name&gt;</code> and <code>components upgrade</code>.</p> </li> </ul> <h4 id=internal>Internal<a class=headerlink href=#internal title="Permanent link">¤</a></h4> <ul> <li>Settings are now loaded only once, and thus are considered immutable once loaded. Previously, django-components would load settings from <code>settings.COMPONENTS</code> on each access. The new behavior aligns with Django's settings.</li> </ul> <h2 id=v0130>v0.130<a class=headerlink href=#v0130 title="Permanent link">¤</a></h2> <h4 id=feat_2>Feat<a class=headerlink href=#feat_2 title="Permanent link">¤</a></h4> <ul> <li> <p>Access the HttpRequest object under <code>Component.request</code>.</p> <p>To pass the request object to a component, either: - Render a template or component with <code>RequestContext</code>, - Or set the <code>request</code> kwarg to <code>Component.render()</code> or <code>Component.render_to_response()</code>.</p> <p>Read more on <a href=https://django-components.github.io/django-components/0.130/concepts/fundamentals/http_request/ >HttpRequest</a>.</p> </li> <li> <p>Access the context processors data under <code>Component.context_processors_data</code>.</p> <p>Context processors data is available only when the component has access to the <code>request</code> object, either by: - Passing the request to <code>Component.render()</code> or <code>Component.render_to_response()</code>, - Or by rendering a template or component with <code>RequestContext</code>, - Or being nested in another component that has access to the request object.</p> <p>The data from context processors is automatically available within the component's template.</p> <p>Read more on <a href=https://django-components.github.io/django-components/0.130/concepts/fundamentals/http_request/ >HttpRequest</a>.</p> </li> </ul> <h2 id=v0129>v0.129<a class=headerlink href=#v0129 title="Permanent link">¤</a></h2> <h4 id=fix>Fix<a class=headerlink href=#fix title="Permanent link">¤</a></h4> <ul> <li>Fix thread unsafe media resolve validation by moving it to ComponentMedia <code>__post_init</code> (<a href=https://github.com/django-components/django-components/pull/977>#977</a></li> <li>Fix bug: Relative path in extends and include does not work when using template_file (<a href=https://github.com/django-components/django-components/pull/976>#976</a></li> <li>Fix error when template cache setting (<code>template_cache_size</code>) is set to 0 (<a href=https://github.com/django-components/django-components/pull/974>#974</a></li> </ul> <h2 id=v0128>v0.128<a class=headerlink href=#v0128 title="Permanent link">¤</a></h2> <h4 id=feat_3>Feat<a class=headerlink href=#feat_3 title="Permanent link">¤</a></h4> <ul> <li> <p>Configurable cache - Set <a href=https://django-components.github.io/django-components/0.128/reference/settings/#django_components.app_settings.ComponentsSettings.cache><code>COMPONENTS.cache</code></a> to change where and how django-components caches JS and CSS files. (<a href=https://github.com/django-components/django-components/pull/946>#946</a>)</p> <p>Read more on <a href=https://django-components.github.io/django-components/0.128/guides/setup/caching>Caching</a>.</p> </li> <li> <p>Highlight coponents and slots in the UI - We've added two boolean settings <a href=https://django-components.github.io/django-components/0.128/reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_components><code>COMPONENTS.debug_highlight_components</code></a> and <a href=https://django-components.github.io/django-components/0.128/reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_slots><code>COMPONENTS.debug_highlight_slots</code></a>, which can be independently set to <code>True</code>. First will wrap components in a blue border, the second will wrap slots in a red border. (<a href=https://github.com/django-components/django-components/pull/942>#942</a>)</p> <p>Read more on <a href=https://django-components.github.io/django-components/0.128/guides/other/troubleshooting/#component-and-slot-highlighting>Troubleshooting</a>.</p> </li> </ul> <h4 id=refactor_1>Refactor<a class=headerlink href=#refactor_1 title="Permanent link">¤</a></h4> <ul> <li>Removed use of eval for node validation (<a href=https://github.com/django-components/django-components/pull/944>#944</a>)</li> </ul> <h4 id=perf>Perf<a class=headerlink href=#perf title="Permanent link">¤</a></h4> <ul> <li> <p>Components can now be infinitely nested. (<a href=https://github.com/django-components/django-components/pull/936>#936</a>)</p> </li> <li> <p>Component input validation is now 6-7x faster on CPython and PyPy. This previously made up 10-30% of the total render time. (<a href=https://github.com/django-components/django-components/pull/945>#945</a>)</p> </li> </ul> <h2 id=v0127>v0.127<a class=headerlink href=#v0127 title="Permanent link">¤</a></h2> <h4 id=fix_1>Fix<a class=headerlink href=#fix_1 title="Permanent link">¤</a></h4> <ul> <li>Fix component rendering when using <code>{% cache %}</code> with remote cache and multiple web servers (<a href=https://github.com/django-components/django-components/issues/930>#930</a>)</li> </ul> <h2 id=v0126>v0.126<a class=headerlink href=#v0126 title="Permanent link">¤</a></h2> <h4 id=refactor_2>Refactor<a class=headerlink href=#refactor_2 title="Permanent link">¤</a></h4> <ul> <li>Replaced <a href=https://www.crummy.com/software/BeautifulSoup/bs4/doc/ >BeautifulSoup4</a> with a custom HTML parser.</li> <li>The heuristic for inserting JS and CSS dependenies into the default place has changed.<ul> <li>JS is still inserted at the end of the <code>&lt;body&gt;</code>, and CSS at the end of <code>&lt;head&gt;</code>.</li> <li>However, we find end of <code>&lt;body&gt;</code> by searching for <strong>last</strong> occurrence of <code>&lt;/body&gt;</code></li> <li>And for the end of <code>&lt;head&gt;</code> we search for the <strong>first</strong> occurrence of <code>&lt;/head&gt;</code></li> </ul> </li> </ul> <h2 id=v0125>v0.125<a class=headerlink href=#v0125 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - We migrated from <code>EmilStenstrom/django-components</code> to <code>django-components/django-components</code>.</p> <p><strong>Repo name and documentation URL changed. Package name remains the same.</strong></p> <p>If you see any broken links or other issues, please report them in <a href=https://github.com/django-components/django-components/issues/922>#922</a>.</p> <h4 id=feat_4>Feat<a class=headerlink href=#feat_4 title="Permanent link">¤</a></h4> <ul> <li><code>@template_tag</code> and <code>BaseNode</code> - A decorator and a class that allow you to define custom template tags that will behave similarly to django-components' own template tags.</li> </ul> <p>Read more on <a href=https://django-components.github.io/django-components/0.125/concepts/advanced/template_tags/ >Template tags</a>.</p> <p>Template tags defined with <code>@template_tag</code> and <code>BaseNode</code> will have the following features:</p> <ul> <li> <p>Accepting args, kwargs, and flags.</p> </li> <li> <p>Allowing literal lists and dicts as inputs as:</p> <p><code>key=[1, 2, 3]</code> or <code>key={"a": 1, "b": 2}</code> - Using template tags tag inputs as:</p> <p><code>{% my_tag key="{% lorem 3 w %}" / %}</code> - Supporting the flat dictionary definition:</p> <p><code>attr:key=value</code> - Spreading args and kwargs with <code>...</code>:</p> <p><code>{% my_tag ...args ...kwargs / %}</code> - Being able to call the template tag as:</p> <p><code>{% my_tag %} ... {% endmy_tag %}</code> or <code>{% my_tag / %}</code></p> </li> </ul> <h4 id=refactor_3>Refactor<a class=headerlink href=#refactor_3 title="Permanent link">¤</a></h4> <ul> <li> <p>Refactored template tag input validation. When you now call template tags like <code>{% slot %}</code>, <code>{% fill %}</code>, <code>{% html_attrs %}</code>, and others, their inputs are now validated the same way as Python function inputs are.</p> <p>So, for example</p> <div class=highlight><pre><span></span><code><a id=__codelineno-1-1 name=__codelineno-1-1 href=#__codelineno-1-1></a><span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;my_slot&quot;</span> <span class=nv>name</span><span class=o>=</span><span class=s2>&quot;content&quot;</span> <span class=o>/</span> <span class=cp>%}</span>
+</code></pre></div> <p>will raise an error, because the positional argument <code>name</code> is given twice.</p> <p>NOTE: Special kwargs whose keys are not valid Python variable names are not affected by this change. So when you define:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-2-1 name=__codelineno-2-1 href=#__codelineno-2-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=nv>data-id</span><span class=o>=</span><span class=m>123</span> <span class=o>/</span> <span class=cp>%}</span>
+</code></pre></div> <p>The <code>data-id</code> will still be accepted as a valid kwarg, assuming that your <code>get_context_data()</code> accepts <code>**kwargs</code>:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-3-1 name=__codelineno-3-1 href=#__codelineno-3-1></a><span class=k>def</span><span class=w> </span><span class=nf>get_context_data</span><span class=p>(</span><span class=bp>self</span><span class=p>,</span> <span class=o>**</span><span class=n>kwargs</span><span class=p>):</span>
+<a id=__codelineno-3-2 name=__codelineno-3-2 href=#__codelineno-3-2></a>    <span class=k>return</span> <span class=p>{</span>
+<a id=__codelineno-3-3 name=__codelineno-3-3 href=#__codelineno-3-3></a>        <span class=s2>&quot;data_id&quot;</span><span class=p>:</span> <span class=n>kwargs</span><span class=p>[</span><span class=s2>&quot;data-id&quot;</span><span class=p>],</span>
+<a id=__codelineno-3-4 name=__codelineno-3-4 href=#__codelineno-3-4></a>    <span class=p>}</span>
+</code></pre></div> </li> </ul> <h2 id=v0124>v0.124<a class=headerlink href=#v0124 title="Permanent link">¤</a></h2> <h4 id=feat_5>Feat<a class=headerlink href=#feat_5 title="Permanent link">¤</a></h4> <ul> <li> <p>Instead of inlining the JS and CSS under <code>Component.js</code> and <code>Component.css</code>, you can move them to their own files, and link the JS/CSS files with <code>Component.js_file</code> and <code>Component.css_file</code>.</p> <p>Even when you specify the JS/CSS with <code>Component.js_file</code> or <code>Component.css_file</code>, then you can still access the content under <code>Component.js</code> or <code>Component.css</code> - behind the scenes, the content of the JS/CSS files will be set to <code>Component.js</code> / <code>Component.css</code> upon first access.</p> <p>The same applies to <code>Component.template_file</code>, which will populate <code>Component.template</code> upon first access.</p> <p>With this change, the role of <code>Component.js/css</code> and the JS/CSS in <code>Component.Media</code> has changed:</p> <ul> <li>The JS/CSS defined in <code>Component.js/css</code> or <code>Component.js/css_file</code> is the "main" JS/CSS</li> <li>The JS/CSS defined in <code>Component.Media.js/css</code> are secondary or additional</li> </ul> <p>See the updated <a href=https://django-components.github.io/django-components/0.124/getting_started/adding_js_and_css/ >"Getting Started" tutorial</a></p> </li> </ul> <h4 id=refactor_4>Refactor<a class=headerlink href=#refactor_4 title="Permanent link">¤</a></h4> <ul> <li> <p>The canonical way to define a template file was changed from <code>template_name</code> to <code>template_file</code>, to align with the rest of the API.</p> <p><code>template_name</code> remains for backwards compatibility. When you get / set <code>template_name</code>, internally this is proxied to <code>template_file</code>.</p> </li> <li> <p>The undocumented <code>Component.component_id</code> was removed. Instead, use <code>Component.id</code>. Changes:</p> <ul> <li>While <code>component_id</code> was unique every time you instantiated <code>Component</code>, the new <code>id</code> is unique every time you render the component (e.g. with <code>Component.render()</code>)</li> <li>The new <code>id</code> is available only during render, so e.g. from within <code>get_context_data()</code></li> </ul> </li> <li> <p>Component's HTML / CSS / JS are now resolved and loaded lazily. That is, if you specify <code>template_name</code>/<code>template_file</code>, <code>js_file</code>, <code>css_file</code>, or <code>Media.js/css</code>, the file paths will be resolved only once you:</p> <ol> <li>Try to access component's HTML / CSS / JS, or</li> <li>Render the component.</li> </ol> <p>Read more on <a href=https://django-components.github.io/django-components/0.124/concepts/fundamentals/defining_js_css_html_files/#customize-how-paths-are-rendered-into-html-tags>Accessing component's HTML / JS / CSS</a>.</p> </li> <li> <p>Component inheritance:</p> <ul> <li>When you subclass a component, the JS and CSS defined on parent's <code>Media</code> class is now inherited by the child component.</li> <li>You can disable or customize Media inheritance by setting <code>extend</code> attribute on the <code>Component.Media</code> nested class. This work similarly to Django's <a href=https://docs.djangoproject.com/en/5.1/topics/forms/media/#extend><code>Media.extend</code></a>.</li> <li>When child component defines either <code>template</code> or <code>template_file</code>, both of parent's <code>template</code> and <code>template_file</code> are ignored. The same applies to <code>js_file</code> and <code>css_file</code>.</li> </ul> </li> <li> <p>Autodiscovery now ignores files and directories that start with an underscore (<code>_</code>), except <code>__init__.py</code></p> </li> <li> <p>The <a href=https://docs.djangoproject.com/en/5.1/topics/signals/ >Signals</a> emitted by or during the use of django-components are now documented, together the <code>template_rendered</code> signal.</p> </li> </ul> <h2 id=v0123>v0.123<a class=headerlink href=#v0123 title="Permanent link">¤</a></h2> <h4 id=fix_2>Fix<a class=headerlink href=#fix_2 title="Permanent link">¤</a></h4> <ul> <li>Fix edge cases around rendering components whose templates used the <code>{% extends %}</code> template tag (<a href=https://github.com/django-components/django-components/pull/859>#859</a>)</li> </ul> <h2 id=v0122>v0.122<a class=headerlink href=#v0122 title="Permanent link">¤</a></h2> <h4 id=feat_6>Feat<a class=headerlink href=#feat_6 title="Permanent link">¤</a></h4> <ul> <li>Add support for HTML fragments. HTML fragments can be rendered by passing <code>type="fragment"</code> to <code>Component.render()</code> or <code>Component.render_to_response()</code>. Read more on how to <a href=https://django-components.github.io/django-components/latest/concepts/advanced/html_tragments>use HTML fragments with HTMX, AlpineJS, or vanillaJS</a>.</li> </ul> <h2 id=v0121>v0.121<a class=headerlink href=#v0121 title="Permanent link">¤</a></h2> <h4 id=fix_3>Fix<a class=headerlink href=#fix_3 title="Permanent link">¤</a></h4> <ul> <li>Fix the use of Django template filters (<code>|lower:"etc"</code>) with component inputs <a href=https://github.com/django-components/django-components/pull/855>#855</a>.</li> </ul> <h2 id=v0120>v0.120<a class=headerlink href=#v0120 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.121 to fix bugs introduced in v0.119.</p> <h4 id=fix_4>Fix<a class=headerlink href=#fix_4 title="Permanent link">¤</a></h4> <ul> <li>Fix the use of translation strings <code>_("bla")</code> as inputs to components <a href=https://github.com/django-components/django-components/pull/849>#849</a>.</li> </ul> <h2 id=v0119>v0.119<a class=headerlink href=#v0119 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - This release introduced bugs <a href=https://github.com/django-components/django-components/pull/849>#849</a>, <a href=https://github.com/django-components/django-components/pull/855>#855</a>. Please update to v0.121.</p> <h4 id=fix_5>Fix<a class=headerlink href=#fix_5 title="Permanent link">¤</a></h4> <ul> <li>Fix compatibility with custom subclasses of Django's <code>Template</code> that need to access <code>origin</code> or other initialization arguments. (<a href=https://github.com/django-components/django-components/pull/828>https://github.com/django-components/django-components/pull/828</a>)</li> </ul> <h4 id=refactor_5>Refactor<a class=headerlink href=#refactor_5 title="Permanent link">¤</a></h4> <ul> <li>Compatibility with <code>django-debug-toolbar-template-profiler</code>:</li> <li> <p>Monkeypatching of Django's <code>Template</code> now happens at <code>AppConfig.ready()</code> (<a href=https://github.com/django-components/django-components/pull/825>https://github.com/django-components/django-components/pull/825</a>)</p> </li> <li> <p>Internal parsing of template tags tag was updated. No API change. (<a href=https://github.com/django-components/django-components/pull/827>https://github.com/django-components/django-components/pull/827</a>)</p> </li> </ul> <h2 id=v0118>v0.118<a class=headerlink href=#v0118 title="Permanent link">¤</a></h2> <h4 id=feat_7>Feat<a class=headerlink href=#feat_7 title="Permanent link">¤</a></h4> <ul> <li>Add support for <code>context_processors</code> and <code>RenderContext</code> inside component templates</li> </ul> <p><code>Component.render()</code> and <code>Component.render_to_response()</code> now accept an extra kwarg <code>request</code>.</p> <div class=codehilite><pre><span></span><code>```py
 def my_view(request)
     return MyTable.render_to_response(
         request=request
     )
 ```
-</code></pre></div> <ul> <li> <p>When you pass in <code>request</code>, the component will use <code>RenderContext</code> instead of <code>Context</code>. Thus the context processors will be applied to the context.</p> </li> <li> <p>NOTE: When you pass in both <code>request</code> and <code>context</code> to <code>Component.render()</code>, and <code>context</code> is already an instance of <code>Context</code>, the <code>request</code> kwarg will be ignored.</p> </li> </ul> <h2 id=v0117>v0.117<a class=headerlink href=#v0117 title="Permanent link">¤</a></h2> <h4 id=fix_6>Fix<a class=headerlink href=#fix_6 title="Permanent link">¤</a></h4> <ul> <li>The HTML parser no longer erronously inserts <code>&lt;html&gt;&lt;head&gt;&lt;body&gt;</code> on some occasions, and no longer tries to close unclosed HTML tags.</li> </ul> <h4 id=refactor_6>Refactor<a class=headerlink href=#refactor_6 title="Permanent link">¤</a></h4> <ul> <li>Replaced <a href=https://github.com/rushter/selectolax>Selectolax</a> with <a href=https://www.crummy.com/software/BeautifulSoup/bs4/doc/ >BeautifulSoup4</a> as project dependencies.</li> </ul> <h2 id=v0116>v0.116<a class=headerlink href=#v0116 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_7>Fix<a class=headerlink href=#fix_7 title="Permanent link">¤</a></h4> <ul> <li>Fix the order of execution of JS scripts:</li> <li>Scripts in <code>Component.Media.js</code> are executed in the order they are defined</li> <li> <p>Scripts in <code>Component.js</code> are executed AFTER <code>Media.js</code> scripts</p> </li> <li> <p>Fix compatibility with AlpineJS</p> </li> <li>Scripts in <code>Component.Media.js</code> are now again inserted as <code>&lt;script&gt;</code> tags</li> <li>By default, <code>Component.Media.js</code> are inserted as synchronous <code>&lt;script&gt;</code> tags, so the AlpineJS components registered in the <code>Media.js</code> scripts will now again run BEFORE the core AlpineJS script.</li> </ul> <p>AlpineJS can be configured like so:</p> <p>Option 1 - AlpineJS loaded in <code>&lt;head&gt;</code> with <code>defer</code> attribute: <div class=highlight><pre><span></span><code><a id=__codelineno-4-1 name=__codelineno-4-1 href=#__codelineno-4-1></a><span class=p>&lt;</span><span class=nt>html</span><span class=p>&gt;</span>
-<a id=__codelineno-4-2 name=__codelineno-4-2 href=#__codelineno-4-2></a>  <span class=p>&lt;</span><span class=nt>head</span><span class=p>&gt;</span>
-<a id=__codelineno-4-3 name=__codelineno-4-3 href=#__codelineno-4-3></a>    {% component_css_dependencies %}
-<a id=__codelineno-4-4 name=__codelineno-4-4 href=#__codelineno-4-4></a>    <span class=p>&lt;</span><span class=nt>script</span> <span class=na>defer</span> <span class=na>src</span><span class=o>=</span><span class=s>&quot;https://unpkg.com/alpinejs&quot;</span><span class=p>&gt;&lt;/</span><span class=nt>script</span><span class=p>&gt;</span>
-<a id=__codelineno-4-5 name=__codelineno-4-5 href=#__codelineno-4-5></a>  <span class=p>&lt;/</span><span class=nt>head</span><span class=p>&gt;</span>
-<a id=__codelineno-4-6 name=__codelineno-4-6 href=#__codelineno-4-6></a>  <span class=p>&lt;</span><span class=nt>body</span><span class=p>&gt;</span>
-<a id=__codelineno-4-7 name=__codelineno-4-7 href=#__codelineno-4-7></a>    {% component &#39;my_alpine_component&#39; / %}
-<a id=__codelineno-4-8 name=__codelineno-4-8 href=#__codelineno-4-8></a>    {% component_js_dependencies %}
-<a id=__codelineno-4-9 name=__codelineno-4-9 href=#__codelineno-4-9></a>  <span class=p>&lt;/</span><span class=nt>body</span><span class=p>&gt;</span>
-<a id=__codelineno-4-10 name=__codelineno-4-10 href=#__codelineno-4-10></a><span class=p>&lt;/</span><span class=nt>html</span><span class=p>&gt;</span>
-</code></pre></div></p> <p>Option 2 - AlpineJS loaded in <code>&lt;body&gt;</code> AFTER <code>{% component_js_depenencies %}</code>: <div class=highlight><pre><span></span><code><a id=__codelineno-5-1 name=__codelineno-5-1 href=#__codelineno-5-1></a><span class=p>&lt;</span><span class=nt>html</span><span class=p>&gt;</span>
-<a id=__codelineno-5-2 name=__codelineno-5-2 href=#__codelineno-5-2></a>    <span class=p>&lt;</span><span class=nt>head</span><span class=p>&gt;</span>
-<a id=__codelineno-5-3 name=__codelineno-5-3 href=#__codelineno-5-3></a>        {% component_css_dependencies %}
-<a id=__codelineno-5-4 name=__codelineno-5-4 href=#__codelineno-5-4></a>    <span class=p>&lt;/</span><span class=nt>head</span><span class=p>&gt;</span>
-<a id=__codelineno-5-5 name=__codelineno-5-5 href=#__codelineno-5-5></a>    <span class=p>&lt;</span><span class=nt>body</span><span class=p>&gt;</span>
-<a id=__codelineno-5-6 name=__codelineno-5-6 href=#__codelineno-5-6></a>        {% component &#39;my_alpine_component&#39; / %}
-<a id=__codelineno-5-7 name=__codelineno-5-7 href=#__codelineno-5-7></a>        {% component_js_dependencies %}
-<a id=__codelineno-5-8 name=__codelineno-5-8 href=#__codelineno-5-8></a>
-<a id=__codelineno-5-9 name=__codelineno-5-9 href=#__codelineno-5-9></a>        <span class=p>&lt;</span><span class=nt>script</span> <span class=na>src</span><span class=o>=</span><span class=s>&quot;https://unpkg.com/alpinejs&quot;</span><span class=p>&gt;&lt;/</span><span class=nt>script</span><span class=p>&gt;</span>
-<a id=__codelineno-5-10 name=__codelineno-5-10 href=#__codelineno-5-10></a>    <span class=p>&lt;/</span><span class=nt>body</span><span class=p>&gt;</span>
-<a id=__codelineno-5-11 name=__codelineno-5-11 href=#__codelineno-5-11></a><span class=p>&lt;/</span><span class=nt>html</span><span class=p>&gt;</span>
-</code></pre></div></p> <h2 id=v0115>v0.115<a class=headerlink href=#v0115 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_8>Fix<a class=headerlink href=#fix_8 title="Permanent link">¤</a></h4> <ul> <li>Fix integration with ManifestStaticFilesStorage on Windows by resolving component filepaths (like <code>Component.template_name</code>) to POSIX paths.</li> </ul> <h2 id=v0114>v0.114<a class=headerlink href=#v0114 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_9>Fix<a class=headerlink href=#fix_9 title="Permanent link">¤</a></h4> <ul> <li>Prevent rendering Slot tags during fill discovery stage to fix a case when a component inside a slot fill tried to access provided data too early.</li> </ul> <h2 id=v0113>v0.113<a class=headerlink href=#v0113 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_10>Fix<a class=headerlink href=#fix_10 title="Permanent link">¤</a></h4> <ul> <li>Ensure consistent order of scripts in <code>Component.Media.js</code></li> </ul> <h2 id=v0112>v0.112<a class=headerlink href=#v0112 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_11>Fix<a class=headerlink href=#fix_11 title="Permanent link">¤</a></h4> <ul> <li>Allow components to accept default fill even if no default slot was encountered during rendering</li> </ul> <h2 id=v0111>v0.111<a class=headerlink href=#v0111 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_12>Fix<a class=headerlink href=#fix_12 title="Permanent link">¤</a></h4> <ul> <li>Prevent rendering Component tags during fill discovery stage to fix a case when a component inside the default slot tried to access provided data too early.</li> </ul> <h2 id=v0110>🚨📢 v0.110<a class=headerlink href=#v0110 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h3 id=general>General<a class=headerlink href=#general title="Permanent link">¤</a></h3> <h4 id=breaking-changes>🚨📢 BREAKING CHANGES<a class=headerlink href=#breaking-changes title="Permanent link">¤</a></h4> <ul> <li> <p>Installation changes:</p> <ul> <li>If your components include JS or CSS, you now must use the middleware and add django-components' URLs to your <code>urlpatterns</code> (See "<a href=https://github.com/django-components/django-components#adding-support-for-js-and-css>Adding support for JS and CSS</a>")</li> </ul> </li> <li> <p>Component typing signature changed from</p> <div class=highlight><pre><span></span><code><a id=__codelineno-6-1 name=__codelineno-6-1 href=#__codelineno-6-1></a><span class=n>Component</span><span class=p>[</span><span class=n>Args</span><span class=p>,</span> <span class=n>Kwargs</span><span class=p>,</span> <span class=n>Data</span><span class=p>,</span> <span class=n>Slots</span><span class=p>]</span>
-</code></pre></div> <p>to</p> <div class=highlight><pre><span></span><code><a id=__codelineno-7-1 name=__codelineno-7-1 href=#__codelineno-7-1></a><span class=n>Component</span><span class=p>[</span><span class=n>Args</span><span class=p>,</span> <span class=n>Kwargs</span><span class=p>,</span> <span class=n>Slots</span><span class=p>,</span> <span class=n>Data</span><span class=p>,</span> <span class=n>JsData</span><span class=p>,</span> <span class=n>CssData</span><span class=p>]</span>
-</code></pre></div> </li> <li> <p>If you rendered a component A with <code>Component.render()</code> and then inserted that into another component B, now you must pass <code>render_dependencies=False</code> to component A:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-8-1 name=__codelineno-8-1 href=#__codelineno-8-1></a><span class=n>prerendered_a</span> <span class=o>=</span> <span class=n>CompA</span><span class=o>.</span><span class=n>render</span><span class=p>(</span>
-<a id=__codelineno-8-2 name=__codelineno-8-2 href=#__codelineno-8-2></a>    <span class=n>args</span><span class=o>=</span><span class=p>[</span><span class=o>...</span><span class=p>],</span>
-<a id=__codelineno-8-3 name=__codelineno-8-3 href=#__codelineno-8-3></a>    <span class=n>kwargs</span><span class=o>=</span><span class=p>{</span><span class=o>...</span><span class=p>},</span>
-<a id=__codelineno-8-4 name=__codelineno-8-4 href=#__codelineno-8-4></a>    <span class=n>render_dependencies</span><span class=o>=</span><span class=kc>False</span><span class=p>,</span>
-<a id=__codelineno-8-5 name=__codelineno-8-5 href=#__codelineno-8-5></a><span class=p>)</span>
-<a id=__codelineno-8-6 name=__codelineno-8-6 href=#__codelineno-8-6></a>
-<a id=__codelineno-8-7 name=__codelineno-8-7 href=#__codelineno-8-7></a><span class=n>html</span> <span class=o>=</span> <span class=n>CompB</span><span class=o>.</span><span class=n>render</span><span class=p>(</span>
-<a id=__codelineno-8-8 name=__codelineno-8-8 href=#__codelineno-8-8></a>    <span class=n>kwargs</span><span class=o>=</span><span class=p>{</span>
-<a id=__codelineno-8-9 name=__codelineno-8-9 href=#__codelineno-8-9></a>        <span class=n>content</span><span class=o>=</span><span class=n>prerendered_a</span><span class=p>,</span>
-<a id=__codelineno-8-10 name=__codelineno-8-10 href=#__codelineno-8-10></a>    <span class=p>},</span>
-<a id=__codelineno-8-11 name=__codelineno-8-11 href=#__codelineno-8-11></a><span class=p>)</span>
-</code></pre></div> </li> </ul> <h4 id=feat_7>Feat<a class=headerlink href=#feat_7 title="Permanent link">¤</a></h4> <ul> <li>Intellisense and mypy validation for settings:</li> </ul> <p>Instead of defining the <code>COMPONENTS</code> settings as a plain dict, you can use <code>ComponentsSettings</code>:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-9-1 name=__codelineno-9-1 href=#__codelineno-9-1></a><span class=c1># settings.py</span>
-<a id=__codelineno-9-2 name=__codelineno-9-2 href=#__codelineno-9-2></a><span class=kn>from</span><span class=w> </span><span class=nn>django_components</span><span class=w> </span><span class=kn>import</span> <span class=n>ComponentsSettings</span>
-<a id=__codelineno-9-3 name=__codelineno-9-3 href=#__codelineno-9-3></a>
-<a id=__codelineno-9-4 name=__codelineno-9-4 href=#__codelineno-9-4></a><span class=n>COMPONENTS</span> <span class=o>=</span> <span class=n>ComponentsSettings</span><span class=p>(</span>
-<a id=__codelineno-9-5 name=__codelineno-9-5 href=#__codelineno-9-5></a>    <span class=n>autodiscover</span><span class=o>=</span><span class=kc>True</span><span class=p>,</span>
-<a id=__codelineno-9-6 name=__codelineno-9-6 href=#__codelineno-9-6></a>    <span class=o>...</span>
-<a id=__codelineno-9-7 name=__codelineno-9-7 href=#__codelineno-9-7></a><span class=p>)</span>
-</code></pre></div> <ul> <li>Use <code>get_component_dirs()</code> and <code>get_component_files()</code> to get the same list of dirs / files that would be imported by <code>autodiscover()</code>, but without actually importing them.</li> </ul> <h4 id=refactor_7>Refactor<a class=headerlink href=#refactor_7 title="Permanent link">¤</a></h4> <ul> <li> <p>For advanced use cases, use can omit the middleware and instead manage component JS and CSS dependencies yourself with <a href=https://github.com/django-components/django-components#render_dependencies-and-deep-dive-into-rendering-js--css-without-the-middleware><code>render_dependencies</code></a></p> </li> <li> <p>The <a href=../api#django_components.ComponentRegistry><code>ComponentRegistry</code></a> settings <a href=../api#django_components.RegistrySettings><code>RegistrySettings</code></a> were lowercased to align with the global settings:</p> </li> <li><code>RegistrySettings.CONTEXT_BEHAVIOR</code> -&gt; <code>RegistrySettings.context_behavior</code></li> <li><code>RegistrySettings.TAG_FORMATTER</code> -&gt; <code>RegistrySettings.tag_formatter</code></li> </ul> <p>The old uppercase settings <code>CONTEXT_BEHAVIOR</code> and <code>TAG_FORMATTER</code> are deprecated and will be removed in v1.</p> <ul> <li> <p>The setting <code>reload_on_template_change</code> was renamed to <a href=../settings#django_components.app_settings.ComponentsSettings#reload_on_file_change><code>reload_on_file_change</code></a>. And now it properly triggers server reload when any file in the component dirs change. The old name <code>reload_on_template_change</code> is deprecated and will be removed in v1.</p> </li> <li> <p>The setting <code>forbidden_static_files</code> was renamed to <a href=../settings#django_components.app_settings.ComponentsSettings#static_files_forbidden><code>static_files_forbidden</code></a> to align with <a href=../settings#django_components.app_settings.ComponentsSettings#static_files_allowed><code>static_files_allowed</code></a> The old name <code>forbidden_static_files</code> is deprecated and will be removed in v1.</p> </li> </ul> <h3 id=tags>Tags<a class=headerlink href=#tags title="Permanent link">¤</a></h3> <h4 id=breaking-changes_1>🚨📢 BREAKING CHANGES<a class=headerlink href=#breaking-changes_1 title="Permanent link">¤</a></h4> <ul> <li> <p><code>{% component_dependencies %}</code> tag was removed. Instead, use <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code></p> <ul> <li> <p>The combined tag was removed to encourage the best practice of putting JS scripts at the end of <code>&lt;body&gt;</code>, and CSS styles inside <code>&lt;head&gt;</code>.</p> <p>On the other hand, co-locating JS script and CSS styles can lead to a <a href=https://en.wikipedia.org/wiki/Flash_of_unstyled_content>flash of unstyled content</a>, as either JS scripts will block the rendering, or CSS will load too late.</p> </li> </ul> </li> <li> <p>The undocumented keyword arg <code>preload</code> of <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code> tags was removed. This will be replaced with HTML fragment support.</p> </li> </ul> <h4 id=fix_13>Fix<a class=headerlink href=#fix_13 title="Permanent link">¤</a></h4> <ul> <li>Allow using forward slash (<code>/</code>) when defining custom TagFormatter, e.g. <code>{% MyComp %}..{% /MyComp %}</code>.</li> </ul> <h4 id=refactor_8>Refactor<a class=headerlink href=#refactor_8 title="Permanent link">¤</a></h4> <ul> <li><code>{% component_dependencies %}</code> tags are now OPTIONAL - If your components use JS and CSS, but you don't use <code>{% component_dependencies %}</code> tags, the JS and CSS will now be, by default, inserted at the end of <code>&lt;body&gt;</code> and at the end of <code>&lt;head&gt;</code> respectively.</li> </ul> <h3 id=slots>Slots<a class=headerlink href=#slots title="Permanent link">¤</a></h3> <h4 id=feat_8>Feat<a class=headerlink href=#feat_8 title="Permanent link">¤</a></h4> <ul> <li>Fills can now be defined within loops (<code>{% for %}</code>) or other tags (like <code>{% with %}</code>), or even other templates using <code>{% include %}</code>.</li> </ul> <p>Following is now possible</p> <div class=highlight><pre><span></span><code><a id=__codelineno-10-1 name=__codelineno-10-1 href=#__codelineno-10-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;table&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-10-2 name=__codelineno-10-2 href=#__codelineno-10-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>for</span> <span class=nv>slot_name</span> <span class=k>in</span> <span class=nv>slots</span> <span class=cp>%}</span>
-<a id=__codelineno-10-3 name=__codelineno-10-3 href=#__codelineno-10-3></a><span class=x>    </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>name</span><span class=o>=</span><span class=nv>slot_name</span> <span class=cp>%}</span>
-<a id=__codelineno-10-4 name=__codelineno-10-4 href=#__codelineno-10-4></a><span class=x>    </span><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
-<a id=__codelineno-10-5 name=__codelineno-10-5 href=#__codelineno-10-5></a><span class=x>  </span><span class=cp>{%</span> <span class=k>endfor</span> <span class=cp>%}</span>
-<a id=__codelineno-10-6 name=__codelineno-10-6 href=#__codelineno-10-6></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
-</code></pre></div> <ul> <li>If you need to access the data or the default content of a default fill, you can set the <code>name</code> kwarg to <code>"default"</code>.</li> </ul> <p>Previously, a default fill would be defined simply by omitting the <code>{% fill %}</code> tags:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-11-1 name=__codelineno-11-1 href=#__codelineno-11-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;child&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-11-2 name=__codelineno-11-2 href=#__codelineno-11-2></a><span class=x>  Hello world</span>
-<a id=__codelineno-11-3 name=__codelineno-11-3 href=#__codelineno-11-3></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
-</code></pre></div> <p>But in that case you could not access the slot data or the default content, like it's possible for named fills:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-12-1 name=__codelineno-12-1 href=#__codelineno-12-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;child&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-12-2 name=__codelineno-12-2 href=#__codelineno-12-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>name</span><span class=o>=</span><span class=s2>&quot;header&quot;</span> <span class=nv>data</span><span class=o>=</span><span class=s2>&quot;data&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-12-3 name=__codelineno-12-3 href=#__codelineno-12-3></a><span class=x>    Hello </span><span class=cp>{{</span> <span class=nv>data.user.name</span> <span class=cp>}}</span>
-<a id=__codelineno-12-4 name=__codelineno-12-4 href=#__codelineno-12-4></a><span class=x>  </span><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
-<a id=__codelineno-12-5 name=__codelineno-12-5 href=#__codelineno-12-5></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
-</code></pre></div> <p>Now, you can specify default tag by using <code>name="default"</code>:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-13-1 name=__codelineno-13-1 href=#__codelineno-13-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;child&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-13-2 name=__codelineno-13-2 href=#__codelineno-13-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>name</span><span class=o>=</span><span class=s2>&quot;default&quot;</span> <span class=nv>data</span><span class=o>=</span><span class=s2>&quot;data&quot;</span> <span class=cp>%}</span>
+</code></pre></div> <ul> <li> <p>When you pass in <code>request</code>, the component will use <code>RenderContext</code> instead of <code>Context</code>. Thus the context processors will be applied to the context.</p> </li> <li> <p>NOTE: When you pass in both <code>request</code> and <code>context</code> to <code>Component.render()</code>, and <code>context</code> is already an instance of <code>Context</code>, the <code>request</code> kwarg will be ignored.</p> </li> </ul> <h2 id=v0117>v0.117<a class=headerlink href=#v0117 title="Permanent link">¤</a></h2> <h4 id=fix_6>Fix<a class=headerlink href=#fix_6 title="Permanent link">¤</a></h4> <ul> <li>The HTML parser no longer erronously inserts <code>&lt;html&gt;&lt;head&gt;&lt;body&gt;</code> on some occasions, and no longer tries to close unclosed HTML tags.</li> </ul> <h4 id=refactor_6>Refactor<a class=headerlink href=#refactor_6 title="Permanent link">¤</a></h4> <ul> <li>Replaced <a href=https://github.com/rushter/selectolax>Selectolax</a> with <a href=https://www.crummy.com/software/BeautifulSoup/bs4/doc/ >BeautifulSoup4</a> as project dependencies.</li> </ul> <h2 id=v0116>v0.116<a class=headerlink href=#v0116 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_7>Fix<a class=headerlink href=#fix_7 title="Permanent link">¤</a></h4> <ul> <li>Fix the order of execution of JS scripts:</li> <li>Scripts in <code>Component.Media.js</code> are executed in the order they are defined</li> <li> <p>Scripts in <code>Component.js</code> are executed AFTER <code>Media.js</code> scripts</p> </li> <li> <p>Fix compatibility with AlpineJS</p> </li> <li>Scripts in <code>Component.Media.js</code> are now again inserted as <code>&lt;script&gt;</code> tags</li> <li>By default, <code>Component.Media.js</code> are inserted as synchronous <code>&lt;script&gt;</code> tags, so the AlpineJS components registered in the <code>Media.js</code> scripts will now again run BEFORE the core AlpineJS script.</li> </ul> <p>AlpineJS can be configured like so:</p> <p>Option 1 - AlpineJS loaded in <code>&lt;head&gt;</code> with <code>defer</code> attribute: <div class=highlight><pre><span></span><code><a id=__codelineno-5-1 name=__codelineno-5-1 href=#__codelineno-5-1></a><span class=p>&lt;</span><span class=nt>html</span><span class=p>&gt;</span>
+<a id=__codelineno-5-2 name=__codelineno-5-2 href=#__codelineno-5-2></a>  <span class=p>&lt;</span><span class=nt>head</span><span class=p>&gt;</span>
+<a id=__codelineno-5-3 name=__codelineno-5-3 href=#__codelineno-5-3></a>    {% component_css_dependencies %}
+<a id=__codelineno-5-4 name=__codelineno-5-4 href=#__codelineno-5-4></a>    <span class=p>&lt;</span><span class=nt>script</span> <span class=na>defer</span> <span class=na>src</span><span class=o>=</span><span class=s>&quot;https://unpkg.com/alpinejs&quot;</span><span class=p>&gt;&lt;/</span><span class=nt>script</span><span class=p>&gt;</span>
+<a id=__codelineno-5-5 name=__codelineno-5-5 href=#__codelineno-5-5></a>  <span class=p>&lt;/</span><span class=nt>head</span><span class=p>&gt;</span>
+<a id=__codelineno-5-6 name=__codelineno-5-6 href=#__codelineno-5-6></a>  <span class=p>&lt;</span><span class=nt>body</span><span class=p>&gt;</span>
+<a id=__codelineno-5-7 name=__codelineno-5-7 href=#__codelineno-5-7></a>    {% component &#39;my_alpine_component&#39; / %}
+<a id=__codelineno-5-8 name=__codelineno-5-8 href=#__codelineno-5-8></a>    {% component_js_dependencies %}
+<a id=__codelineno-5-9 name=__codelineno-5-9 href=#__codelineno-5-9></a>  <span class=p>&lt;/</span><span class=nt>body</span><span class=p>&gt;</span>
+<a id=__codelineno-5-10 name=__codelineno-5-10 href=#__codelineno-5-10></a><span class=p>&lt;/</span><span class=nt>html</span><span class=p>&gt;</span>
+</code></pre></div></p> <p>Option 2 - AlpineJS loaded in <code>&lt;body&gt;</code> AFTER <code>{% component_js_depenencies %}</code>: <div class=highlight><pre><span></span><code><a id=__codelineno-6-1 name=__codelineno-6-1 href=#__codelineno-6-1></a><span class=p>&lt;</span><span class=nt>html</span><span class=p>&gt;</span>
+<a id=__codelineno-6-2 name=__codelineno-6-2 href=#__codelineno-6-2></a>    <span class=p>&lt;</span><span class=nt>head</span><span class=p>&gt;</span>
+<a id=__codelineno-6-3 name=__codelineno-6-3 href=#__codelineno-6-3></a>        {% component_css_dependencies %}
+<a id=__codelineno-6-4 name=__codelineno-6-4 href=#__codelineno-6-4></a>    <span class=p>&lt;/</span><span class=nt>head</span><span class=p>&gt;</span>
+<a id=__codelineno-6-5 name=__codelineno-6-5 href=#__codelineno-6-5></a>    <span class=p>&lt;</span><span class=nt>body</span><span class=p>&gt;</span>
+<a id=__codelineno-6-6 name=__codelineno-6-6 href=#__codelineno-6-6></a>        {% component &#39;my_alpine_component&#39; / %}
+<a id=__codelineno-6-7 name=__codelineno-6-7 href=#__codelineno-6-7></a>        {% component_js_dependencies %}
+<a id=__codelineno-6-8 name=__codelineno-6-8 href=#__codelineno-6-8></a>
+<a id=__codelineno-6-9 name=__codelineno-6-9 href=#__codelineno-6-9></a>        <span class=p>&lt;</span><span class=nt>script</span> <span class=na>src</span><span class=o>=</span><span class=s>&quot;https://unpkg.com/alpinejs&quot;</span><span class=p>&gt;&lt;/</span><span class=nt>script</span><span class=p>&gt;</span>
+<a id=__codelineno-6-10 name=__codelineno-6-10 href=#__codelineno-6-10></a>    <span class=p>&lt;/</span><span class=nt>body</span><span class=p>&gt;</span>
+<a id=__codelineno-6-11 name=__codelineno-6-11 href=#__codelineno-6-11></a><span class=p>&lt;/</span><span class=nt>html</span><span class=p>&gt;</span>
+</code></pre></div></p> <h2 id=v0115>v0.115<a class=headerlink href=#v0115 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_8>Fix<a class=headerlink href=#fix_8 title="Permanent link">¤</a></h4> <ul> <li>Fix integration with ManifestStaticFilesStorage on Windows by resolving component filepaths (like <code>Component.template_name</code>) to POSIX paths.</li> </ul> <h2 id=v0114>v0.114<a class=headerlink href=#v0114 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_9>Fix<a class=headerlink href=#fix_9 title="Permanent link">¤</a></h4> <ul> <li>Prevent rendering Slot tags during fill discovery stage to fix a case when a component inside a slot fill tried to access provided data too early.</li> </ul> <h2 id=v0113>v0.113<a class=headerlink href=#v0113 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_10>Fix<a class=headerlink href=#fix_10 title="Permanent link">¤</a></h4> <ul> <li>Ensure consistent order of scripts in <code>Component.Media.js</code></li> </ul> <h2 id=v0112>v0.112<a class=headerlink href=#v0112 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_11>Fix<a class=headerlink href=#fix_11 title="Permanent link">¤</a></h4> <ul> <li>Allow components to accept default fill even if no default slot was encountered during rendering</li> </ul> <h2 id=v0111>v0.111<a class=headerlink href=#v0111 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h4 id=fix_12>Fix<a class=headerlink href=#fix_12 title="Permanent link">¤</a></h4> <ul> <li>Prevent rendering Component tags during fill discovery stage to fix a case when a component inside the default slot tried to access provided data too early.</li> </ul> <h2 id=v0110>🚨📢 v0.110<a class=headerlink href=#v0110 title="Permanent link">¤</a></h2> <p>⚠️ Attention ⚠️ - Please update to v0.117 to fix known bugs. See <a href=https://github.com/django-components/django-components/issues/791>#791</a> and <a href=https://github.com/django-components/django-components/issues/789>#789</a> and <a href=https://github.com/django-components/django-components/issues/818>#818</a>.</p> <h3 id=general>General<a class=headerlink href=#general title="Permanent link">¤</a></h3> <h4 id=breaking-changes>🚨📢 BREAKING CHANGES<a class=headerlink href=#breaking-changes title="Permanent link">¤</a></h4> <ul> <li> <p>Installation changes:</p> <ul> <li>If your components include JS or CSS, you now must use the middleware and add django-components' URLs to your <code>urlpatterns</code> (See "<a href=https://github.com/django-components/django-components#adding-support-for-js-and-css>Adding support for JS and CSS</a>")</li> </ul> </li> <li> <p>Component typing signature changed from</p> <div class=highlight><pre><span></span><code><a id=__codelineno-7-1 name=__codelineno-7-1 href=#__codelineno-7-1></a><span class=n>Component</span><span class=p>[</span><span class=n>Args</span><span class=p>,</span> <span class=n>Kwargs</span><span class=p>,</span> <span class=n>Data</span><span class=p>,</span> <span class=n>Slots</span><span class=p>]</span>
+</code></pre></div> <p>to</p> <div class=highlight><pre><span></span><code><a id=__codelineno-8-1 name=__codelineno-8-1 href=#__codelineno-8-1></a><span class=n>Component</span><span class=p>[</span><span class=n>Args</span><span class=p>,</span> <span class=n>Kwargs</span><span class=p>,</span> <span class=n>Slots</span><span class=p>,</span> <span class=n>Data</span><span class=p>,</span> <span class=n>JsData</span><span class=p>,</span> <span class=n>CssData</span><span class=p>]</span>
+</code></pre></div> </li> <li> <p>If you rendered a component A with <code>Component.render()</code> and then inserted that into another component B, now you must pass <code>render_dependencies=False</code> to component A:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-9-1 name=__codelineno-9-1 href=#__codelineno-9-1></a><span class=n>prerendered_a</span> <span class=o>=</span> <span class=n>CompA</span><span class=o>.</span><span class=n>render</span><span class=p>(</span>
+<a id=__codelineno-9-2 name=__codelineno-9-2 href=#__codelineno-9-2></a>    <span class=n>args</span><span class=o>=</span><span class=p>[</span><span class=o>...</span><span class=p>],</span>
+<a id=__codelineno-9-3 name=__codelineno-9-3 href=#__codelineno-9-3></a>    <span class=n>kwargs</span><span class=o>=</span><span class=p>{</span><span class=o>...</span><span class=p>},</span>
+<a id=__codelineno-9-4 name=__codelineno-9-4 href=#__codelineno-9-4></a>    <span class=n>render_dependencies</span><span class=o>=</span><span class=kc>False</span><span class=p>,</span>
+<a id=__codelineno-9-5 name=__codelineno-9-5 href=#__codelineno-9-5></a><span class=p>)</span>
+<a id=__codelineno-9-6 name=__codelineno-9-6 href=#__codelineno-9-6></a>
+<a id=__codelineno-9-7 name=__codelineno-9-7 href=#__codelineno-9-7></a><span class=n>html</span> <span class=o>=</span> <span class=n>CompB</span><span class=o>.</span><span class=n>render</span><span class=p>(</span>
+<a id=__codelineno-9-8 name=__codelineno-9-8 href=#__codelineno-9-8></a>    <span class=n>kwargs</span><span class=o>=</span><span class=p>{</span>
+<a id=__codelineno-9-9 name=__codelineno-9-9 href=#__codelineno-9-9></a>        <span class=n>content</span><span class=o>=</span><span class=n>prerendered_a</span><span class=p>,</span>
+<a id=__codelineno-9-10 name=__codelineno-9-10 href=#__codelineno-9-10></a>    <span class=p>},</span>
+<a id=__codelineno-9-11 name=__codelineno-9-11 href=#__codelineno-9-11></a><span class=p>)</span>
+</code></pre></div> </li> </ul> <h4 id=feat_8>Feat<a class=headerlink href=#feat_8 title="Permanent link">¤</a></h4> <ul> <li>Intellisense and mypy validation for settings:</li> </ul> <p>Instead of defining the <code>COMPONENTS</code> settings as a plain dict, you can use <code>ComponentsSettings</code>:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-10-1 name=__codelineno-10-1 href=#__codelineno-10-1></a><span class=c1># settings.py</span>
+<a id=__codelineno-10-2 name=__codelineno-10-2 href=#__codelineno-10-2></a><span class=kn>from</span><span class=w> </span><span class=nn>django_components</span><span class=w> </span><span class=kn>import</span> <span class=n>ComponentsSettings</span>
+<a id=__codelineno-10-3 name=__codelineno-10-3 href=#__codelineno-10-3></a>
+<a id=__codelineno-10-4 name=__codelineno-10-4 href=#__codelineno-10-4></a><span class=n>COMPONENTS</span> <span class=o>=</span> <span class=n>ComponentsSettings</span><span class=p>(</span>
+<a id=__codelineno-10-5 name=__codelineno-10-5 href=#__codelineno-10-5></a>    <span class=n>autodiscover</span><span class=o>=</span><span class=kc>True</span><span class=p>,</span>
+<a id=__codelineno-10-6 name=__codelineno-10-6 href=#__codelineno-10-6></a>    <span class=o>...</span>
+<a id=__codelineno-10-7 name=__codelineno-10-7 href=#__codelineno-10-7></a><span class=p>)</span>
+</code></pre></div> <ul> <li>Use <code>get_component_dirs()</code> and <code>get_component_files()</code> to get the same list of dirs / files that would be imported by <code>autodiscover()</code>, but without actually importing them.</li> </ul> <h4 id=refactor_7>Refactor<a class=headerlink href=#refactor_7 title="Permanent link">¤</a></h4> <ul> <li> <p>For advanced use cases, use can omit the middleware and instead manage component JS and CSS dependencies yourself with <a href=https://github.com/django-components/django-components#render_dependencies-and-deep-dive-into-rendering-js--css-without-the-middleware><code>render_dependencies</code></a></p> </li> <li> <p>The <a href=../api#django_components.ComponentRegistry><code>ComponentRegistry</code></a> settings <a href=../api#django_components.RegistrySettings><code>RegistrySettings</code></a> were lowercased to align with the global settings:</p> </li> <li><code>RegistrySettings.CONTEXT_BEHAVIOR</code> -&gt; <code>RegistrySettings.context_behavior</code></li> <li><code>RegistrySettings.TAG_FORMATTER</code> -&gt; <code>RegistrySettings.tag_formatter</code></li> </ul> <p>The old uppercase settings <code>CONTEXT_BEHAVIOR</code> and <code>TAG_FORMATTER</code> are deprecated and will be removed in v1.</p> <ul> <li> <p>The setting <code>reload_on_template_change</code> was renamed to <a href=../settings#django_components.app_settings.ComponentsSettings#reload_on_file_change><code>reload_on_file_change</code></a>. And now it properly triggers server reload when any file in the component dirs change. The old name <code>reload_on_template_change</code> is deprecated and will be removed in v1.</p> </li> <li> <p>The setting <code>forbidden_static_files</code> was renamed to <a href=../settings#django_components.app_settings.ComponentsSettings#static_files_forbidden><code>static_files_forbidden</code></a> to align with <a href=../settings#django_components.app_settings.ComponentsSettings#static_files_allowed><code>static_files_allowed</code></a> The old name <code>forbidden_static_files</code> is deprecated and will be removed in v1.</p> </li> </ul> <h3 id=tags>Tags<a class=headerlink href=#tags title="Permanent link">¤</a></h3> <h4 id=breaking-changes_1>🚨📢 BREAKING CHANGES<a class=headerlink href=#breaking-changes_1 title="Permanent link">¤</a></h4> <ul> <li> <p><code>{% component_dependencies %}</code> tag was removed. Instead, use <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code></p> <ul> <li> <p>The combined tag was removed to encourage the best practice of putting JS scripts at the end of <code>&lt;body&gt;</code>, and CSS styles inside <code>&lt;head&gt;</code>.</p> <p>On the other hand, co-locating JS script and CSS styles can lead to a <a href=https://en.wikipedia.org/wiki/Flash_of_unstyled_content>flash of unstyled content</a>, as either JS scripts will block the rendering, or CSS will load too late.</p> </li> </ul> </li> <li> <p>The undocumented keyword arg <code>preload</code> of <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code> tags was removed. This will be replaced with HTML fragment support.</p> </li> </ul> <h4 id=fix_13>Fix<a class=headerlink href=#fix_13 title="Permanent link">¤</a></h4> <ul> <li>Allow using forward slash (<code>/</code>) when defining custom TagFormatter, e.g. <code>{% MyComp %}..{% /MyComp %}</code>.</li> </ul> <h4 id=refactor_8>Refactor<a class=headerlink href=#refactor_8 title="Permanent link">¤</a></h4> <ul> <li><code>{% component_dependencies %}</code> tags are now OPTIONAL - If your components use JS and CSS, but you don't use <code>{% component_dependencies %}</code> tags, the JS and CSS will now be, by default, inserted at the end of <code>&lt;body&gt;</code> and at the end of <code>&lt;head&gt;</code> respectively.</li> </ul> <h3 id=slots>Slots<a class=headerlink href=#slots title="Permanent link">¤</a></h3> <h4 id=feat_9>Feat<a class=headerlink href=#feat_9 title="Permanent link">¤</a></h4> <ul> <li>Fills can now be defined within loops (<code>{% for %}</code>) or other tags (like <code>{% with %}</code>), or even other templates using <code>{% include %}</code>.</li> </ul> <p>Following is now possible</p> <div class=highlight><pre><span></span><code><a id=__codelineno-11-1 name=__codelineno-11-1 href=#__codelineno-11-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;table&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-11-2 name=__codelineno-11-2 href=#__codelineno-11-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>for</span> <span class=nv>slot_name</span> <span class=k>in</span> <span class=nv>slots</span> <span class=cp>%}</span>
+<a id=__codelineno-11-3 name=__codelineno-11-3 href=#__codelineno-11-3></a><span class=x>    </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>name</span><span class=o>=</span><span class=nv>slot_name</span> <span class=cp>%}</span>
+<a id=__codelineno-11-4 name=__codelineno-11-4 href=#__codelineno-11-4></a><span class=x>    </span><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
+<a id=__codelineno-11-5 name=__codelineno-11-5 href=#__codelineno-11-5></a><span class=x>  </span><span class=cp>{%</span> <span class=k>endfor</span> <span class=cp>%}</span>
+<a id=__codelineno-11-6 name=__codelineno-11-6 href=#__codelineno-11-6></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
+</code></pre></div> <ul> <li>If you need to access the data or the default content of a default fill, you can set the <code>name</code> kwarg to <code>"default"</code>.</li> </ul> <p>Previously, a default fill would be defined simply by omitting the <code>{% fill %}</code> tags:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-12-1 name=__codelineno-12-1 href=#__codelineno-12-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;child&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-12-2 name=__codelineno-12-2 href=#__codelineno-12-2></a><span class=x>  Hello world</span>
+<a id=__codelineno-12-3 name=__codelineno-12-3 href=#__codelineno-12-3></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
+</code></pre></div> <p>But in that case you could not access the slot data or the default content, like it's possible for named fills:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-13-1 name=__codelineno-13-1 href=#__codelineno-13-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;child&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-13-2 name=__codelineno-13-2 href=#__codelineno-13-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>name</span><span class=o>=</span><span class=s2>&quot;header&quot;</span> <span class=nv>data</span><span class=o>=</span><span class=s2>&quot;data&quot;</span> <span class=cp>%}</span>
 <a id=__codelineno-13-3 name=__codelineno-13-3 href=#__codelineno-13-3></a><span class=x>    Hello </span><span class=cp>{{</span> <span class=nv>data.user.name</span> <span class=cp>}}</span>
 <a id=__codelineno-13-4 name=__codelineno-13-4 href=#__codelineno-13-4></a><span class=x>  </span><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
 <a id=__codelineno-13-5 name=__codelineno-13-5 href=#__codelineno-13-5></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
-</code></pre></div> <ul> <li>When inside <code>get_context_data()</code> or other component methods, the default fill can now be accessed as <code>Component.input.slots["default"]</code>, e.g.:</li> </ul> <div class=highlight><pre><span></span><code><a id=__codelineno-14-1 name=__codelineno-14-1 href=#__codelineno-14-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
-<a id=__codelineno-14-2 name=__codelineno-14-2 href=#__codelineno-14-2></a>    <span class=k>def</span><span class=w> </span><span class=nf>get_context_data</span><span class=p>(</span><span class=bp>self</span><span class=p>,</span> <span class=o>*</span><span class=n>args</span><span class=p>,</span> <span class=o>**</span><span class=n>kwargs</span><span class=p>):</span>
-<a id=__codelineno-14-3 name=__codelineno-14-3 href=#__codelineno-14-3></a>        <span class=n>default_slot</span> <span class=o>=</span> <span class=bp>self</span><span class=o>.</span><span class=n>input</span><span class=o>.</span><span class=n>slots</span><span class=p>[</span><span class=s2>&quot;default&quot;</span><span class=p>]</span>
-<a id=__codelineno-14-4 name=__codelineno-14-4 href=#__codelineno-14-4></a>        <span class=o>...</span>
-</code></pre></div> <ul> <li>You can now dynamically pass all slots to a child component. This is similar to <a href=https://vue-land.github.io/faq/forwarding-slots#passing-all-slots>passing all slots in Vue</a>:</li> </ul> <div class=highlight><pre><span></span><code><a id=__codelineno-15-1 name=__codelineno-15-1 href=#__codelineno-15-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
+</code></pre></div> <p>Now, you can specify default tag by using <code>name="default"</code>:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-14-1 name=__codelineno-14-1 href=#__codelineno-14-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;child&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-14-2 name=__codelineno-14-2 href=#__codelineno-14-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>name</span><span class=o>=</span><span class=s2>&quot;default&quot;</span> <span class=nv>data</span><span class=o>=</span><span class=s2>&quot;data&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-14-3 name=__codelineno-14-3 href=#__codelineno-14-3></a><span class=x>    Hello </span><span class=cp>{{</span> <span class=nv>data.user.name</span> <span class=cp>}}</span>
+<a id=__codelineno-14-4 name=__codelineno-14-4 href=#__codelineno-14-4></a><span class=x>  </span><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
+<a id=__codelineno-14-5 name=__codelineno-14-5 href=#__codelineno-14-5></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
+</code></pre></div> <ul> <li>When inside <code>get_context_data()</code> or other component methods, the default fill can now be accessed as <code>Component.input.slots["default"]</code>, e.g.:</li> </ul> <div class=highlight><pre><span></span><code><a id=__codelineno-15-1 name=__codelineno-15-1 href=#__codelineno-15-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
 <a id=__codelineno-15-2 name=__codelineno-15-2 href=#__codelineno-15-2></a>    <span class=k>def</span><span class=w> </span><span class=nf>get_context_data</span><span class=p>(</span><span class=bp>self</span><span class=p>,</span> <span class=o>*</span><span class=n>args</span><span class=p>,</span> <span class=o>**</span><span class=n>kwargs</span><span class=p>):</span>
-<a id=__codelineno-15-3 name=__codelineno-15-3 href=#__codelineno-15-3></a>        <span class=k>return</span> <span class=p>{</span>
-<a id=__codelineno-15-4 name=__codelineno-15-4 href=#__codelineno-15-4></a>            <span class=s2>&quot;slots&quot;</span><span class=p>:</span> <span class=bp>self</span><span class=o>.</span><span class=n>input</span><span class=o>.</span><span class=n>slots</span><span class=p>,</span>
-<a id=__codelineno-15-5 name=__codelineno-15-5 href=#__codelineno-15-5></a>        <span class=p>}</span>
-<a id=__codelineno-15-6 name=__codelineno-15-6 href=#__codelineno-15-6></a>
-<a id=__codelineno-15-7 name=__codelineno-15-7 href=#__codelineno-15-7></a>    <span class=n>template</span><span class=p>:</span> <span class=s2>&quot;&quot;&quot;</span>
-<a id=__codelineno-15-8 name=__codelineno-15-8 href=#__codelineno-15-8></a><span class=s2>      &lt;div&gt;</span>
-<a id=__codelineno-15-9 name=__codelineno-15-9 href=#__codelineno-15-9></a><span class=s2>        {</span><span class=si>% c</span><span class=s2>omponent &quot;child&quot; %}</span>
-<a id=__codelineno-15-10 name=__codelineno-15-10 href=#__codelineno-15-10></a><span class=s2>          {</span><span class=si>% f</span><span class=s2>or slot_name in slots %}</span>
-<a id=__codelineno-15-11 name=__codelineno-15-11 href=#__codelineno-15-11></a><span class=s2>            {</span><span class=si>% f</span><span class=s2>ill name=slot_name data=&quot;data&quot; %}</span>
-<a id=__codelineno-15-12 name=__codelineno-15-12 href=#__codelineno-15-12></a><span class=s2>              {</span><span class=si>% s</span><span class=s2>lot name=slot_name ...data / %}</span>
-<a id=__codelineno-15-13 name=__codelineno-15-13 href=#__codelineno-15-13></a><span class=s2>            {</span><span class=si>% e</span><span class=s2>ndfill %}</span>
-<a id=__codelineno-15-14 name=__codelineno-15-14 href=#__codelineno-15-14></a><span class=s2>          {</span><span class=si>% e</span><span class=s2>ndfor %}</span>
-<a id=__codelineno-15-15 name=__codelineno-15-15 href=#__codelineno-15-15></a><span class=s2>        {</span><span class=si>% e</span><span class=s2>ndcomponent %}</span>
-<a id=__codelineno-15-16 name=__codelineno-15-16 href=#__codelineno-15-16></a><span class=s2>      &lt;/div&gt;</span>
-<a id=__codelineno-15-17 name=__codelineno-15-17 href=#__codelineno-15-17></a><span class=s2>    &quot;&quot;&quot;</span>
-</code></pre></div> <h4 id=fix_14>Fix<a class=headerlink href=#fix_14 title="Permanent link">¤</a></h4> <ul> <li> <p>Slots defined with <code>{% fill %}</code> tags are now properly accessible via <code>self.input.slots</code> in <code>get_context_data()</code></p> </li> <li> <p>Do not raise error if multiple slots with same name are flagged as default</p> </li> <li> <p>Slots can now be defined within loops (<code>{% for %}</code>) or other tags (like <code>{% with %}</code>), or even other templates using <code>{% include %}</code>.</p> </li> </ul> <p>Previously, following would cause the kwarg <code>name</code> to be an empty string:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-16-1 name=__codelineno-16-1 href=#__codelineno-16-1></a><span class=cp>{%</span> <span class=k>for</span> <span class=nv>slot_name</span> <span class=k>in</span> <span class=nv>slots</span> <span class=cp>%}</span>
-<a id=__codelineno-16-2 name=__codelineno-16-2 href=#__codelineno-16-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>slot</span> <span class=nv>name</span><span class=o>=</span><span class=nv>slot_name</span> <span class=cp>%}</span>
-<a id=__codelineno-16-3 name=__codelineno-16-3 href=#__codelineno-16-3></a><span class=cp>{%</span> <span class=k>endfor</span> <span class=cp>%}</span>
-</code></pre></div> <h4 id=refactor_9>Refactor<a class=headerlink href=#refactor_9 title="Permanent link">¤</a></h4> <ul> <li>When you define multiple slots with the same name inside a template, you now have to set the <code>default</code> and <code>required</code> flags individually.</li> </ul> <div class=highlight><pre><span></span><code><a id=__codelineno-17-1 name=__codelineno-17-1 href=#__codelineno-17-1></a><span class=p>&lt;</span><span class=nt>div</span> <span class=na>class</span><span class=o>=</span><span class=s>&quot;calendar-component&quot;</span><span class=p>&gt;</span>
-<a id=__codelineno-17-2 name=__codelineno-17-2 href=#__codelineno-17-2></a>    <span class=p>&lt;</span><span class=nt>div</span> <span class=na>class</span><span class=o>=</span><span class=s>&quot;header&quot;</span><span class=p>&gt;</span>
-<a id=__codelineno-17-3 name=__codelineno-17-3 href=#__codelineno-17-3></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=nv>required</span> <span class=cp>%}</span>Image here<span class=cp>{%</span> <span class=k>endslot</span> <span class=cp>%}</span>
-<a id=__codelineno-17-4 name=__codelineno-17-4 href=#__codelineno-17-4></a>    <span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
-<a id=__codelineno-17-5 name=__codelineno-17-5 href=#__codelineno-17-5></a>    <span class=p>&lt;</span><span class=nt>div</span> <span class=na>class</span><span class=o>=</span><span class=s>&quot;body&quot;</span><span class=p>&gt;</span>
-<a id=__codelineno-17-6 name=__codelineno-17-6 href=#__codelineno-17-6></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=nv>required</span> <span class=cp>%}</span>Image here<span class=cp>{%</span> <span class=k>endslot</span> <span class=cp>%}</span>
-<a id=__codelineno-17-7 name=__codelineno-17-7 href=#__codelineno-17-7></a>    <span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
-<a id=__codelineno-17-8 name=__codelineno-17-8 href=#__codelineno-17-8></a><span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
-</code></pre></div> <p>This means you can also have multiple slots with the same name but different conditions.</p> <p>E.g. in this example, we have a component that renders a user avatar - a small circular image with a profile picture of name initials.</p> <p>If the component is given <code>image_src</code> or <code>name_initials</code> variables, the <code>image</code> slot is optional. But if neither of those are provided, you MUST fill the <code>image</code> slot.</p> <div class=highlight><pre><span></span><code><a id=__codelineno-18-1 name=__codelineno-18-1 href=#__codelineno-18-1></a><span class=p>&lt;</span><span class=nt>div</span> <span class=na>class</span><span class=o>=</span><span class=s>&quot;avatar&quot;</span><span class=p>&gt;</span>
-<a id=__codelineno-18-2 name=__codelineno-18-2 href=#__codelineno-18-2></a>    <span class=cp>{%</span> <span class=k>if</span> <span class=nv>image_src</span> <span class=cp>%}</span>
-<a id=__codelineno-18-3 name=__codelineno-18-3 href=#__codelineno-18-3></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=cp>%}</span>
-<a id=__codelineno-18-4 name=__codelineno-18-4 href=#__codelineno-18-4></a>            <span class=p>&lt;</span><span class=nt>img</span> <span class=na>src</span><span class=o>=</span><span class=s>&quot;</span><span class=cp>{{</span> <span class=nv>image_src</span> <span class=cp>}}</span><span class=s>&quot;</span> <span class=p>/&gt;</span>
-<a id=__codelineno-18-5 name=__codelineno-18-5 href=#__codelineno-18-5></a>        <span class=cp>{%</span> <span class=k>endslot</span> <span class=cp>%}</span>
-<a id=__codelineno-18-6 name=__codelineno-18-6 href=#__codelineno-18-6></a>    <span class=cp>{%</span> <span class=k>elif</span> <span class=nv>name_initials</span> <span class=cp>%}</span>
-<a id=__codelineno-18-7 name=__codelineno-18-7 href=#__codelineno-18-7></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=nv>required</span> <span class=cp>%}</span>
-<a id=__codelineno-18-8 name=__codelineno-18-8 href=#__codelineno-18-8></a>            <span class=p>&lt;</span><span class=nt>div</span> <span class=na>style</span><span class=o>=</span><span class=s>&quot;</span>
-<a id=__codelineno-18-9 name=__codelineno-18-9 href=#__codelineno-18-9></a><span class=s>                border-radius: 25px;</span>
-<a id=__codelineno-18-10 name=__codelineno-18-10 href=#__codelineno-18-10></a><span class=s>                width: 50px;</span>
-<a id=__codelineno-18-11 name=__codelineno-18-11 href=#__codelineno-18-11></a><span class=s>                height: 50px;</span>
-<a id=__codelineno-18-12 name=__codelineno-18-12 href=#__codelineno-18-12></a><span class=s>                background: blue;</span>
-<a id=__codelineno-18-13 name=__codelineno-18-13 href=#__codelineno-18-13></a><span class=s>            &quot;</span><span class=p>&gt;</span>
-<a id=__codelineno-18-14 name=__codelineno-18-14 href=#__codelineno-18-14></a>                <span class=cp>{{</span> <span class=nv>name_initials</span> <span class=cp>}}</span>
-<a id=__codelineno-18-15 name=__codelineno-18-15 href=#__codelineno-18-15></a>            <span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
-<a id=__codelineno-18-16 name=__codelineno-18-16 href=#__codelineno-18-16></a>        <span class=cp>{%</span> <span class=k>endslot</span> <span class=cp>%}</span>
-<a id=__codelineno-18-17 name=__codelineno-18-17 href=#__codelineno-18-17></a>    <span class=cp>{%</span> <span class=k>else</span> <span class=cp>%}</span>
-<a id=__codelineno-18-18 name=__codelineno-18-18 href=#__codelineno-18-18></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=nv>required</span> <span class=o>/</span> <span class=cp>%}</span>
-<a id=__codelineno-18-19 name=__codelineno-18-19 href=#__codelineno-18-19></a>    <span class=cp>{%</span> <span class=k>endif</span> <span class=cp>%}</span>
-<a id=__codelineno-18-20 name=__codelineno-18-20 href=#__codelineno-18-20></a><span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
-</code></pre></div> <ul> <li>The slot fills that were passed to a component and which can be accessed as <code>Component.input.slots</code> can now be passed through the Django template, e.g. as inputs to other tags.</li> </ul> <p>Internally, django-components handles slot fills as functions.</p> <p>Previously, if you tried to pass a slot fill within a template, Django would try to call it as a function.</p> <p>Now, something like this is possible:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-19-1 name=__codelineno-19-1 href=#__codelineno-19-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
-<a id=__codelineno-19-2 name=__codelineno-19-2 href=#__codelineno-19-2></a>    <span class=k>def</span><span class=w> </span><span class=nf>get_context_data</span><span class=p>(</span><span class=bp>self</span><span class=p>,</span> <span class=o>*</span><span class=n>args</span><span class=p>,</span> <span class=o>**</span><span class=n>kwargs</span><span class=p>):</span>
-<a id=__codelineno-19-3 name=__codelineno-19-3 href=#__codelineno-19-3></a>        <span class=k>return</span> <span class=p>{</span>
-<a id=__codelineno-19-4 name=__codelineno-19-4 href=#__codelineno-19-4></a>            <span class=s2>&quot;child_slot&quot;</span><span class=p>:</span> <span class=bp>self</span><span class=o>.</span><span class=n>input</span><span class=o>.</span><span class=n>slots</span><span class=p>[</span><span class=s2>&quot;child_slot&quot;</span><span class=p>],</span>
-<a id=__codelineno-19-5 name=__codelineno-19-5 href=#__codelineno-19-5></a>        <span class=p>}</span>
-<a id=__codelineno-19-6 name=__codelineno-19-6 href=#__codelineno-19-6></a>
-<a id=__codelineno-19-7 name=__codelineno-19-7 href=#__codelineno-19-7></a>    <span class=n>template</span><span class=p>:</span> <span class=s2>&quot;&quot;&quot;</span>
-<a id=__codelineno-19-8 name=__codelineno-19-8 href=#__codelineno-19-8></a><span class=s2>      &lt;div&gt;</span>
-<a id=__codelineno-19-9 name=__codelineno-19-9 href=#__codelineno-19-9></a><span class=s2>        {</span><span class=si>% c</span><span class=s2>omponent &quot;child&quot; content=child_slot / %}</span>
-<a id=__codelineno-19-10 name=__codelineno-19-10 href=#__codelineno-19-10></a><span class=s2>      &lt;/div&gt;</span>
-<a id=__codelineno-19-11 name=__codelineno-19-11 href=#__codelineno-19-11></a><span class=s2>    &quot;&quot;&quot;</span>
-</code></pre></div> <p>NOTE: Using <code>{% slot %}</code> and <code>{% fill %}</code> tags is still the preferred method, but the approach above may be necessary in some complex or edge cases.</p> <ul> <li>The <code>is_filled</code> variable (and the <code>{{ component_vars.is_filled }}</code> context variable) now returns <code>False</code> when you try to access a slot name which has not been defined:</li> </ul> <p>Before:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-20-1 name=__codelineno-20-1 href=#__codelineno-20-1></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.header</span> <span class=cp>}}</span><span class=x> -&gt; True</span>
-<a id=__codelineno-20-2 name=__codelineno-20-2 href=#__codelineno-20-2></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.footer</span> <span class=cp>}}</span><span class=x> -&gt; False</span>
-<a id=__codelineno-20-3 name=__codelineno-20-3 href=#__codelineno-20-3></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.nonexist</span> <span class=cp>}}</span><span class=x> -&gt; &quot;&quot; (empty string)</span>
-</code></pre></div> <p>After: <div class=highlight><pre><span></span><code><a id=__codelineno-21-1 name=__codelineno-21-1 href=#__codelineno-21-1></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.header</span> <span class=cp>}}</span><span class=x> -&gt; True</span>
+<a id=__codelineno-15-3 name=__codelineno-15-3 href=#__codelineno-15-3></a>        <span class=n>default_slot</span> <span class=o>=</span> <span class=bp>self</span><span class=o>.</span><span class=n>input</span><span class=o>.</span><span class=n>slots</span><span class=p>[</span><span class=s2>&quot;default&quot;</span><span class=p>]</span>
+<a id=__codelineno-15-4 name=__codelineno-15-4 href=#__codelineno-15-4></a>        <span class=o>...</span>
+</code></pre></div> <ul> <li>You can now dynamically pass all slots to a child component. This is similar to <a href=https://vue-land.github.io/faq/forwarding-slots#passing-all-slots>passing all slots in Vue</a>:</li> </ul> <div class=highlight><pre><span></span><code><a id=__codelineno-16-1 name=__codelineno-16-1 href=#__codelineno-16-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
+<a id=__codelineno-16-2 name=__codelineno-16-2 href=#__codelineno-16-2></a>    <span class=k>def</span><span class=w> </span><span class=nf>get_context_data</span><span class=p>(</span><span class=bp>self</span><span class=p>,</span> <span class=o>*</span><span class=n>args</span><span class=p>,</span> <span class=o>**</span><span class=n>kwargs</span><span class=p>):</span>
+<a id=__codelineno-16-3 name=__codelineno-16-3 href=#__codelineno-16-3></a>        <span class=k>return</span> <span class=p>{</span>
+<a id=__codelineno-16-4 name=__codelineno-16-4 href=#__codelineno-16-4></a>            <span class=s2>&quot;slots&quot;</span><span class=p>:</span> <span class=bp>self</span><span class=o>.</span><span class=n>input</span><span class=o>.</span><span class=n>slots</span><span class=p>,</span>
+<a id=__codelineno-16-5 name=__codelineno-16-5 href=#__codelineno-16-5></a>        <span class=p>}</span>
+<a id=__codelineno-16-6 name=__codelineno-16-6 href=#__codelineno-16-6></a>
+<a id=__codelineno-16-7 name=__codelineno-16-7 href=#__codelineno-16-7></a>    <span class=n>template</span><span class=p>:</span> <span class=s2>&quot;&quot;&quot;</span>
+<a id=__codelineno-16-8 name=__codelineno-16-8 href=#__codelineno-16-8></a><span class=s2>      &lt;div&gt;</span>
+<a id=__codelineno-16-9 name=__codelineno-16-9 href=#__codelineno-16-9></a><span class=s2>        {</span><span class=si>% c</span><span class=s2>omponent &quot;child&quot; %}</span>
+<a id=__codelineno-16-10 name=__codelineno-16-10 href=#__codelineno-16-10></a><span class=s2>          {</span><span class=si>% f</span><span class=s2>or slot_name in slots %}</span>
+<a id=__codelineno-16-11 name=__codelineno-16-11 href=#__codelineno-16-11></a><span class=s2>            {</span><span class=si>% f</span><span class=s2>ill name=slot_name data=&quot;data&quot; %}</span>
+<a id=__codelineno-16-12 name=__codelineno-16-12 href=#__codelineno-16-12></a><span class=s2>              {</span><span class=si>% s</span><span class=s2>lot name=slot_name ...data / %}</span>
+<a id=__codelineno-16-13 name=__codelineno-16-13 href=#__codelineno-16-13></a><span class=s2>            {</span><span class=si>% e</span><span class=s2>ndfill %}</span>
+<a id=__codelineno-16-14 name=__codelineno-16-14 href=#__codelineno-16-14></a><span class=s2>          {</span><span class=si>% e</span><span class=s2>ndfor %}</span>
+<a id=__codelineno-16-15 name=__codelineno-16-15 href=#__codelineno-16-15></a><span class=s2>        {</span><span class=si>% e</span><span class=s2>ndcomponent %}</span>
+<a id=__codelineno-16-16 name=__codelineno-16-16 href=#__codelineno-16-16></a><span class=s2>      &lt;/div&gt;</span>
+<a id=__codelineno-16-17 name=__codelineno-16-17 href=#__codelineno-16-17></a><span class=s2>    &quot;&quot;&quot;</span>
+</code></pre></div> <h4 id=fix_14>Fix<a class=headerlink href=#fix_14 title="Permanent link">¤</a></h4> <ul> <li> <p>Slots defined with <code>{% fill %}</code> tags are now properly accessible via <code>self.input.slots</code> in <code>get_context_data()</code></p> </li> <li> <p>Do not raise error if multiple slots with same name are flagged as default</p> </li> <li> <p>Slots can now be defined within loops (<code>{% for %}</code>) or other tags (like <code>{% with %}</code>), or even other templates using <code>{% include %}</code>.</p> </li> </ul> <p>Previously, following would cause the kwarg <code>name</code> to be an empty string:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-17-1 name=__codelineno-17-1 href=#__codelineno-17-1></a><span class=cp>{%</span> <span class=k>for</span> <span class=nv>slot_name</span> <span class=k>in</span> <span class=nv>slots</span> <span class=cp>%}</span>
+<a id=__codelineno-17-2 name=__codelineno-17-2 href=#__codelineno-17-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>slot</span> <span class=nv>name</span><span class=o>=</span><span class=nv>slot_name</span> <span class=cp>%}</span>
+<a id=__codelineno-17-3 name=__codelineno-17-3 href=#__codelineno-17-3></a><span class=cp>{%</span> <span class=k>endfor</span> <span class=cp>%}</span>
+</code></pre></div> <h4 id=refactor_9>Refactor<a class=headerlink href=#refactor_9 title="Permanent link">¤</a></h4> <ul> <li>When you define multiple slots with the same name inside a template, you now have to set the <code>default</code> and <code>required</code> flags individually.</li> </ul> <div class=highlight><pre><span></span><code><a id=__codelineno-18-1 name=__codelineno-18-1 href=#__codelineno-18-1></a><span class=p>&lt;</span><span class=nt>div</span> <span class=na>class</span><span class=o>=</span><span class=s>&quot;calendar-component&quot;</span><span class=p>&gt;</span>
+<a id=__codelineno-18-2 name=__codelineno-18-2 href=#__codelineno-18-2></a>    <span class=p>&lt;</span><span class=nt>div</span> <span class=na>class</span><span class=o>=</span><span class=s>&quot;header&quot;</span><span class=p>&gt;</span>
+<a id=__codelineno-18-3 name=__codelineno-18-3 href=#__codelineno-18-3></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=nv>required</span> <span class=cp>%}</span>Image here<span class=cp>{%</span> <span class=k>endslot</span> <span class=cp>%}</span>
+<a id=__codelineno-18-4 name=__codelineno-18-4 href=#__codelineno-18-4></a>    <span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
+<a id=__codelineno-18-5 name=__codelineno-18-5 href=#__codelineno-18-5></a>    <span class=p>&lt;</span><span class=nt>div</span> <span class=na>class</span><span class=o>=</span><span class=s>&quot;body&quot;</span><span class=p>&gt;</span>
+<a id=__codelineno-18-6 name=__codelineno-18-6 href=#__codelineno-18-6></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=nv>required</span> <span class=cp>%}</span>Image here<span class=cp>{%</span> <span class=k>endslot</span> <span class=cp>%}</span>
+<a id=__codelineno-18-7 name=__codelineno-18-7 href=#__codelineno-18-7></a>    <span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
+<a id=__codelineno-18-8 name=__codelineno-18-8 href=#__codelineno-18-8></a><span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
+</code></pre></div> <p>This means you can also have multiple slots with the same name but different conditions.</p> <p>E.g. in this example, we have a component that renders a user avatar - a small circular image with a profile picture of name initials.</p> <p>If the component is given <code>image_src</code> or <code>name_initials</code> variables, the <code>image</code> slot is optional. But if neither of those are provided, you MUST fill the <code>image</code> slot.</p> <div class=highlight><pre><span></span><code><a id=__codelineno-19-1 name=__codelineno-19-1 href=#__codelineno-19-1></a><span class=p>&lt;</span><span class=nt>div</span> <span class=na>class</span><span class=o>=</span><span class=s>&quot;avatar&quot;</span><span class=p>&gt;</span>
+<a id=__codelineno-19-2 name=__codelineno-19-2 href=#__codelineno-19-2></a>    <span class=cp>{%</span> <span class=k>if</span> <span class=nv>image_src</span> <span class=cp>%}</span>
+<a id=__codelineno-19-3 name=__codelineno-19-3 href=#__codelineno-19-3></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=cp>%}</span>
+<a id=__codelineno-19-4 name=__codelineno-19-4 href=#__codelineno-19-4></a>            <span class=p>&lt;</span><span class=nt>img</span> <span class=na>src</span><span class=o>=</span><span class=s>&quot;</span><span class=cp>{{</span> <span class=nv>image_src</span> <span class=cp>}}</span><span class=s>&quot;</span> <span class=p>/&gt;</span>
+<a id=__codelineno-19-5 name=__codelineno-19-5 href=#__codelineno-19-5></a>        <span class=cp>{%</span> <span class=k>endslot</span> <span class=cp>%}</span>
+<a id=__codelineno-19-6 name=__codelineno-19-6 href=#__codelineno-19-6></a>    <span class=cp>{%</span> <span class=k>elif</span> <span class=nv>name_initials</span> <span class=cp>%}</span>
+<a id=__codelineno-19-7 name=__codelineno-19-7 href=#__codelineno-19-7></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=nv>required</span> <span class=cp>%}</span>
+<a id=__codelineno-19-8 name=__codelineno-19-8 href=#__codelineno-19-8></a>            <span class=p>&lt;</span><span class=nt>div</span> <span class=na>style</span><span class=o>=</span><span class=s>&quot;</span>
+<a id=__codelineno-19-9 name=__codelineno-19-9 href=#__codelineno-19-9></a><span class=s>                border-radius: 25px;</span>
+<a id=__codelineno-19-10 name=__codelineno-19-10 href=#__codelineno-19-10></a><span class=s>                width: 50px;</span>
+<a id=__codelineno-19-11 name=__codelineno-19-11 href=#__codelineno-19-11></a><span class=s>                height: 50px;</span>
+<a id=__codelineno-19-12 name=__codelineno-19-12 href=#__codelineno-19-12></a><span class=s>                background: blue;</span>
+<a id=__codelineno-19-13 name=__codelineno-19-13 href=#__codelineno-19-13></a><span class=s>            &quot;</span><span class=p>&gt;</span>
+<a id=__codelineno-19-14 name=__codelineno-19-14 href=#__codelineno-19-14></a>                <span class=cp>{{</span> <span class=nv>name_initials</span> <span class=cp>}}</span>
+<a id=__codelineno-19-15 name=__codelineno-19-15 href=#__codelineno-19-15></a>            <span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
+<a id=__codelineno-19-16 name=__codelineno-19-16 href=#__codelineno-19-16></a>        <span class=cp>{%</span> <span class=k>endslot</span> <span class=cp>%}</span>
+<a id=__codelineno-19-17 name=__codelineno-19-17 href=#__codelineno-19-17></a>    <span class=cp>{%</span> <span class=k>else</span> <span class=cp>%}</span>
+<a id=__codelineno-19-18 name=__codelineno-19-18 href=#__codelineno-19-18></a>        <span class=cp>{%</span> <span class=k>slot</span> <span class=s2>&quot;image&quot;</span> <span class=nv>default</span> <span class=nv>required</span> <span class=o>/</span> <span class=cp>%}</span>
+<a id=__codelineno-19-19 name=__codelineno-19-19 href=#__codelineno-19-19></a>    <span class=cp>{%</span> <span class=k>endif</span> <span class=cp>%}</span>
+<a id=__codelineno-19-20 name=__codelineno-19-20 href=#__codelineno-19-20></a><span class=p>&lt;/</span><span class=nt>div</span><span class=p>&gt;</span>
+</code></pre></div> <ul> <li>The slot fills that were passed to a component and which can be accessed as <code>Component.input.slots</code> can now be passed through the Django template, e.g. as inputs to other tags.</li> </ul> <p>Internally, django-components handles slot fills as functions.</p> <p>Previously, if you tried to pass a slot fill within a template, Django would try to call it as a function.</p> <p>Now, something like this is possible:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-20-1 name=__codelineno-20-1 href=#__codelineno-20-1></a><span class=k>class</span><span class=w> </span><span class=nc>MyTable</span><span class=p>(</span><span class=n>Component</span><span class=p>):</span>
+<a id=__codelineno-20-2 name=__codelineno-20-2 href=#__codelineno-20-2></a>    <span class=k>def</span><span class=w> </span><span class=nf>get_context_data</span><span class=p>(</span><span class=bp>self</span><span class=p>,</span> <span class=o>*</span><span class=n>args</span><span class=p>,</span> <span class=o>**</span><span class=n>kwargs</span><span class=p>):</span>
+<a id=__codelineno-20-3 name=__codelineno-20-3 href=#__codelineno-20-3></a>        <span class=k>return</span> <span class=p>{</span>
+<a id=__codelineno-20-4 name=__codelineno-20-4 href=#__codelineno-20-4></a>            <span class=s2>&quot;child_slot&quot;</span><span class=p>:</span> <span class=bp>self</span><span class=o>.</span><span class=n>input</span><span class=o>.</span><span class=n>slots</span><span class=p>[</span><span class=s2>&quot;child_slot&quot;</span><span class=p>],</span>
+<a id=__codelineno-20-5 name=__codelineno-20-5 href=#__codelineno-20-5></a>        <span class=p>}</span>
+<a id=__codelineno-20-6 name=__codelineno-20-6 href=#__codelineno-20-6></a>
+<a id=__codelineno-20-7 name=__codelineno-20-7 href=#__codelineno-20-7></a>    <span class=n>template</span><span class=p>:</span> <span class=s2>&quot;&quot;&quot;</span>
+<a id=__codelineno-20-8 name=__codelineno-20-8 href=#__codelineno-20-8></a><span class=s2>      &lt;div&gt;</span>
+<a id=__codelineno-20-9 name=__codelineno-20-9 href=#__codelineno-20-9></a><span class=s2>        {</span><span class=si>% c</span><span class=s2>omponent &quot;child&quot; content=child_slot / %}</span>
+<a id=__codelineno-20-10 name=__codelineno-20-10 href=#__codelineno-20-10></a><span class=s2>      &lt;/div&gt;</span>
+<a id=__codelineno-20-11 name=__codelineno-20-11 href=#__codelineno-20-11></a><span class=s2>    &quot;&quot;&quot;</span>
+</code></pre></div> <p>NOTE: Using <code>{% slot %}</code> and <code>{% fill %}</code> tags is still the preferred method, but the approach above may be necessary in some complex or edge cases.</p> <ul> <li>The <code>is_filled</code> variable (and the <code>{{ component_vars.is_filled }}</code> context variable) now returns <code>False</code> when you try to access a slot name which has not been defined:</li> </ul> <p>Before:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-21-1 name=__codelineno-21-1 href=#__codelineno-21-1></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.header</span> <span class=cp>}}</span><span class=x> -&gt; True</span>
 <a id=__codelineno-21-2 name=__codelineno-21-2 href=#__codelineno-21-2></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.footer</span> <span class=cp>}}</span><span class=x> -&gt; False</span>
-<a id=__codelineno-21-3 name=__codelineno-21-3 href=#__codelineno-21-3></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.nonexist</span> <span class=cp>}}</span><span class=x> -&gt; False</span>
-</code></pre></div></p> <ul> <li> <p>Components no longer raise an error if there are extra slot fills</p> </li> <li> <p>Components will raise error when a slot is doubly-filled. </p> </li> </ul> <p>E.g. if we have a component with a default slot:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-22-1 name=__codelineno-22-1 href=#__codelineno-22-1></a><span class=cp>{%</span> <span class=k>slot</span> <span class=nv>name</span><span class=o>=</span><span class=s2>&quot;content&quot;</span> <span class=nv>default</span> <span class=o>/</span> <span class=cp>%}</span>
-</code></pre></div> <p>Now there is two ways how we can target this slot: Either using <code>name="default"</code> or <code>name="content"</code>.</p> <p>In case you specify BOTH, the component will raise an error:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-23-1 name=__codelineno-23-1 href=#__codelineno-23-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;child&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-23-2 name=__codelineno-23-2 href=#__codelineno-23-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>slot</span><span class=o>=</span><span class=s2>&quot;default&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-23-3 name=__codelineno-23-3 href=#__codelineno-23-3></a><span class=x>    Hello from default slot</span>
-<a id=__codelineno-23-4 name=__codelineno-23-4 href=#__codelineno-23-4></a><span class=x>  </span><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
-<a id=__codelineno-23-5 name=__codelineno-23-5 href=#__codelineno-23-5></a><span class=x>  </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>slot</span><span class=o>=</span><span class=s2>&quot;content&quot;</span> <span class=nv>data</span><span class=o>=</span><span class=s2>&quot;data&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-23-6 name=__codelineno-23-6 href=#__codelineno-23-6></a><span class=x>    Hello from content slot</span>
-<a id=__codelineno-23-7 name=__codelineno-23-7 href=#__codelineno-23-7></a><span class=x>  </span><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
-<a id=__codelineno-23-8 name=__codelineno-23-8 href=#__codelineno-23-8></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
-</code></pre></div> <h2 id=v0100>🚨📢 v0.100<a class=headerlink href=#v0100 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_2>BREAKING CHANGES<a class=headerlink href=#breaking-changes_2 title="Permanent link">¤</a></h4> <ul> <li> <p><code>django_components.safer_staticfiles</code> app was removed. It is no longer needed.</p> </li> <li> <p>Installation changes:</p> <ul> <li>Instead of defining component directories in <code>STATICFILES_DIRS</code>, set them to <a href=https://github.com/django-components/django-components#dirs><code>COMPONENTS.dirs</code></a>.</li> <li> <p>You now must define <code>STATICFILES_FINDERS</code></p> </li> <li> <p><a href=https://github.com/django-components/django-components/blob/master/docs/migrating_from_safer_staticfiles.md>See here how to migrate your settings.py</a></p> </li> </ul> </li> </ul> <h4 id=feat_9>Feat<a class=headerlink href=#feat_9 title="Permanent link">¤</a></h4> <ul> <li>Beside the top-level <code>/components</code> directory, you can now define also app-level components dirs, e.g. <code>[app]/components</code> (See <a href=https://github.com/django-components/django-components#app_dirs><code>COMPONENTS.app_dirs</code></a>).</li> </ul> <h4 id=refactor_10>Refactor<a class=headerlink href=#refactor_10 title="Permanent link">¤</a></h4> <ul> <li>When you call <code>as_view()</code> on a component instance, that instance will be passed to <code>View.as_view()</code></li> </ul> <h2 id=v097>v0.97<a class=headerlink href=#v097 title="Permanent link">¤</a></h2> <h4 id=fix_15>Fix<a class=headerlink href=#fix_15 title="Permanent link">¤</a></h4> <ul> <li>Fixed template caching. You can now also manually create cached templates with <a href=https://github.com/django-components/django-components#template_cache_size---tune-the-template-cache><code>cached_template()</code></a></li> </ul> <h4 id=refactor_11>Refactor<a class=headerlink href=#refactor_11 title="Permanent link">¤</a></h4> <ul> <li> <p>The previously undocumented <code>get_template</code> was made private.</p> </li> <li> <p>In it's place, there's a new <code>get_template</code>, which supersedes <code>get_template_string</code> (will be removed in v1). The new <code>get_template</code> is the same as <code>get_template_string</code>, except it allows to return either a string or a Template instance.</p> </li> <li> <p>You now must use only one of <code>template</code>, <code>get_template</code>, <code>template_name</code>, or <code>get_template_name</code>.</p> </li> </ul> <h2 id=v096>v0.96<a class=headerlink href=#v096 title="Permanent link">¤</a></h2> <h4 id=feat_10>Feat<a class=headerlink href=#feat_10 title="Permanent link">¤</a></h4> <ul> <li> <p>Run-time type validation for Python 3.11+ - If the <code>Component</code> class is typed, e.g. <code>Component[Args, Kwargs, ...]</code>, the args, kwargs, slots, and data are validated against the given types. (See <a href=https://github.com/django-components/django-components#runtime-input-validation-with-types>Runtime input validation with types</a>)</p> </li> <li> <p>Render hooks - Set <code>on_render_before</code> and <code>on_render_after</code> methods on <code>Component</code> to intercept or modify the template or context before rendering, or the rendered result afterwards. (See <a href=https://github.com/django-components/django-components#component-hooks>Component hooks</a>)</p> </li> <li> <p><code>component_vars.is_filled</code> context variable can be accessed from within <code>on_render_before</code> and <code>on_render_after</code> hooks as <code>self.is_filled.my_slot</code></p> </li> </ul> <h2 id=095>0.95<a class=headerlink href=#095 title="Permanent link">¤</a></h2> <h4 id=feat_11>Feat<a class=headerlink href=#feat_11 title="Permanent link">¤</a></h4> <ul> <li>Added support for dynamic components, where the component name is passed as a variable. (See <a href=https://github.com/django-components/django-components#dynamic-components>Dynamic components</a>)</li> </ul> <h4 id=refactor_12>Refactor<a class=headerlink href=#refactor_12 title="Permanent link">¤</a></h4> <ul> <li>Changed <code>Component.input</code> to raise <code>RuntimeError</code> if accessed outside of render context. Previously it returned <code>None</code> if unset.</li> </ul> <h2 id=v094>v0.94<a class=headerlink href=#v094 title="Permanent link">¤</a></h2> <h4 id=feat_12>Feat<a class=headerlink href=#feat_12 title="Permanent link">¤</a></h4> <ul> <li> <p>django_components now automatically configures Django to support multi-line tags. (See <a href=https://github.com/django-components/django-components#multi-line-tags>Multi-line tags</a>)</p> </li> <li> <p>New setting <code>reload_on_template_change</code>. Set this to <code>True</code> to reload the dev server on changes to component template files. (See <a href=https://github.com/django-components/django-components#reload-dev-server-on-component-file-changes>Reload dev server on component file changes</a>)</p> </li> </ul> <h2 id=v093>v0.93<a class=headerlink href=#v093 title="Permanent link">¤</a></h2> <h4 id=feat_13>Feat<a class=headerlink href=#feat_13 title="Permanent link">¤</a></h4> <ul> <li> <p>Spread operator <code>...dict</code> inside template tags. (See <a href=https://github.com/django-components/django-components#spread-operator>Spread operator</a>)</p> </li> <li> <p>Use template tags inside string literals in component inputs. (See <a href=https://github.com/django-components/django-components#use-template-tags-inside-component-inputs>Use template tags inside component inputs</a>)</p> </li> <li> <p>Dynamic slots, fills and provides - The <code>name</code> argument for these can now be a variable, a template expression, or via spread operator</p> </li> <li> <p>Component library authors can now configure <code>CONTEXT_BEHAVIOR</code> and <code>TAG_FORMATTER</code> settings independently from user settings.</p> </li> </ul> <h2 id=v092>🚨📢 v0.92<a class=headerlink href=#v092 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_3>BREAKING CHANGES<a class=headerlink href=#breaking-changes_3 title="Permanent link">¤</a></h4> <ul> <li><code>Component</code> class is no longer a subclass of <code>View</code>. To configure the <code>View</code> class, set the <code>Component.View</code> nested class. HTTP methods like <code>get</code> or <code>post</code> can still be defined directly on <code>Component</code> class, and <code>Component.as_view()</code> internally calls <code>Component.View.as_view()</code>. (See <a href=https://github.com/django-components/django-components#modifying-the-view-class>Modifying the View class</a>)</li> </ul> <h4 id=feat_14>Feat<a class=headerlink href=#feat_14 title="Permanent link">¤</a></h4> <ul> <li> <p>The inputs (args, kwargs, slots, context, ...) that you pass to <code>Component.render()</code> can be accessed from within <code>get_context_data</code>, <code>get_template</code> and <code>get_template_name</code> via <code>self.input</code>. (See <a href=https://github.com/django-components/django-components#accessing-data-passed-to-the-component>Accessing data passed to the component</a>)</p> </li> <li> <p>Typing: <code>Component</code> class supports generics that specify types for <code>Component.render</code> (See <a href=https://github.com/django-components/django-components#adding-type-hints-with-generics>Adding type hints with Generics</a>)</p> </li> </ul> <h2 id=v090>v0.90<a class=headerlink href=#v090 title="Permanent link">¤</a></h2> <h4 id=feat_15>Feat<a class=headerlink href=#feat_15 title="Permanent link">¤</a></h4> <ul> <li> <p>All tags (<code>component</code>, <code>slot</code>, <code>fill</code>, ...) now support "self-closing" or "inline" form, where you can omit the closing tag:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-24-1 name=__codelineno-24-1 href=#__codelineno-24-1></a><span class=c>{# Before #}</span>
-<a id=__codelineno-24-2 name=__codelineno-24-2 href=#__codelineno-24-2></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;button&quot;</span> <span class=cp>%}{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
-<a id=__codelineno-24-3 name=__codelineno-24-3 href=#__codelineno-24-3></a><span class=c>{# After #}</span>
-<a id=__codelineno-24-4 name=__codelineno-24-4 href=#__codelineno-24-4></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;button&quot;</span> <span class=o>/</span> <span class=cp>%}</span>
-</code></pre></div> </li> <li> <p>All tags now support the "dictionary key" or "aggregate" syntax (<code>kwarg:key=val</code>):</p> <div class=highlight><pre><span></span><code><a id=__codelineno-25-1 name=__codelineno-25-1 href=#__codelineno-25-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;button&quot;</span> <span class=nv>attrs</span><span class=o>:</span><span class=nv>class</span><span class=o>=</span><span class=s2>&quot;hidden&quot;</span> <span class=cp>%}</span>
-</code></pre></div> </li> <li> <p>You can change how the components are written in the template with <a href=https://github.com/django-components/django-components#customizing-component-tags-with-tagformatter>TagFormatter</a>.</p> <p>The default is <code>django_components.component_formatter</code>:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-26-1 name=__codelineno-26-1 href=#__codelineno-26-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;button&quot;</span> <span class=nv>href</span><span class=o>=</span><span class=s2>&quot;...&quot;</span> <span class=nv>disabled</span> <span class=cp>%}</span>
-<a id=__codelineno-26-2 name=__codelineno-26-2 href=#__codelineno-26-2></a><span class=x>    Click me!</span>
-<a id=__codelineno-26-3 name=__codelineno-26-3 href=#__codelineno-26-3></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
-</code></pre></div> <p>While <code>django_components.shorthand_component_formatter</code> allows you to write components like so:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-27-1 name=__codelineno-27-1 href=#__codelineno-27-1></a><span class=cp>{%</span> <span class=k>button</span> <span class=nv>href</span><span class=o>=</span><span class=s2>&quot;...&quot;</span> <span class=nv>disabled</span> <span class=cp>%}</span>
+<a id=__codelineno-21-3 name=__codelineno-21-3 href=#__codelineno-21-3></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.nonexist</span> <span class=cp>}}</span><span class=x> -&gt; &quot;&quot; (empty string)</span>
+</code></pre></div> <p>After: <div class=highlight><pre><span></span><code><a id=__codelineno-22-1 name=__codelineno-22-1 href=#__codelineno-22-1></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.header</span> <span class=cp>}}</span><span class=x> -&gt; True</span>
+<a id=__codelineno-22-2 name=__codelineno-22-2 href=#__codelineno-22-2></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.footer</span> <span class=cp>}}</span><span class=x> -&gt; False</span>
+<a id=__codelineno-22-3 name=__codelineno-22-3 href=#__codelineno-22-3></a><span class=cp>{{</span> <span class=nv>component_vars.is_filled.nonexist</span> <span class=cp>}}</span><span class=x> -&gt; False</span>
+</code></pre></div></p> <ul> <li> <p>Components no longer raise an error if there are extra slot fills</p> </li> <li> <p>Components will raise error when a slot is doubly-filled. </p> </li> </ul> <p>E.g. if we have a component with a default slot:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-23-1 name=__codelineno-23-1 href=#__codelineno-23-1></a><span class=cp>{%</span> <span class=k>slot</span> <span class=nv>name</span><span class=o>=</span><span class=s2>&quot;content&quot;</span> <span class=nv>default</span> <span class=o>/</span> <span class=cp>%}</span>
+</code></pre></div> <p>Now there is two ways how we can target this slot: Either using <code>name="default"</code> or <code>name="content"</code>.</p> <p>In case you specify BOTH, the component will raise an error:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-24-1 name=__codelineno-24-1 href=#__codelineno-24-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;child&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-24-2 name=__codelineno-24-2 href=#__codelineno-24-2></a><span class=x>  </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>slot</span><span class=o>=</span><span class=s2>&quot;default&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-24-3 name=__codelineno-24-3 href=#__codelineno-24-3></a><span class=x>    Hello from default slot</span>
+<a id=__codelineno-24-4 name=__codelineno-24-4 href=#__codelineno-24-4></a><span class=x>  </span><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
+<a id=__codelineno-24-5 name=__codelineno-24-5 href=#__codelineno-24-5></a><span class=x>  </span><span class=cp>{%</span> <span class=k>fill</span> <span class=nv>slot</span><span class=o>=</span><span class=s2>&quot;content&quot;</span> <span class=nv>data</span><span class=o>=</span><span class=s2>&quot;data&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-24-6 name=__codelineno-24-6 href=#__codelineno-24-6></a><span class=x>    Hello from content slot</span>
+<a id=__codelineno-24-7 name=__codelineno-24-7 href=#__codelineno-24-7></a><span class=x>  </span><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
+<a id=__codelineno-24-8 name=__codelineno-24-8 href=#__codelineno-24-8></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
+</code></pre></div> <h2 id=v0100>🚨📢 v0.100<a class=headerlink href=#v0100 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_2>BREAKING CHANGES<a class=headerlink href=#breaking-changes_2 title="Permanent link">¤</a></h4> <ul> <li> <p><code>django_components.safer_staticfiles</code> app was removed. It is no longer needed.</p> </li> <li> <p>Installation changes:</p> <ul> <li>Instead of defining component directories in <code>STATICFILES_DIRS</code>, set them to <a href=https://github.com/django-components/django-components#dirs><code>COMPONENTS.dirs</code></a>.</li> <li> <p>You now must define <code>STATICFILES_FINDERS</code></p> </li> <li> <p><a href=https://github.com/django-components/django-components/blob/master/docs/migrating_from_safer_staticfiles.md>See here how to migrate your settings.py</a></p> </li> </ul> </li> </ul> <h4 id=feat_10>Feat<a class=headerlink href=#feat_10 title="Permanent link">¤</a></h4> <ul> <li>Beside the top-level <code>/components</code> directory, you can now define also app-level components dirs, e.g. <code>[app]/components</code> (See <a href=https://github.com/django-components/django-components#app_dirs><code>COMPONENTS.app_dirs</code></a>).</li> </ul> <h4 id=refactor_10>Refactor<a class=headerlink href=#refactor_10 title="Permanent link">¤</a></h4> <ul> <li>When you call <code>as_view()</code> on a component instance, that instance will be passed to <code>View.as_view()</code></li> </ul> <h2 id=v097>v0.97<a class=headerlink href=#v097 title="Permanent link">¤</a></h2> <h4 id=fix_15>Fix<a class=headerlink href=#fix_15 title="Permanent link">¤</a></h4> <ul> <li>Fixed template caching. You can now also manually create cached templates with <a href=https://github.com/django-components/django-components#template_cache_size---tune-the-template-cache><code>cached_template()</code></a></li> </ul> <h4 id=refactor_11>Refactor<a class=headerlink href=#refactor_11 title="Permanent link">¤</a></h4> <ul> <li> <p>The previously undocumented <code>get_template</code> was made private.</p> </li> <li> <p>In it's place, there's a new <code>get_template</code>, which supersedes <code>get_template_string</code> (will be removed in v1). The new <code>get_template</code> is the same as <code>get_template_string</code>, except it allows to return either a string or a Template instance.</p> </li> <li> <p>You now must use only one of <code>template</code>, <code>get_template</code>, <code>template_name</code>, or <code>get_template_name</code>.</p> </li> </ul> <h2 id=v096>v0.96<a class=headerlink href=#v096 title="Permanent link">¤</a></h2> <h4 id=feat_11>Feat<a class=headerlink href=#feat_11 title="Permanent link">¤</a></h4> <ul> <li> <p>Run-time type validation for Python 3.11+ - If the <code>Component</code> class is typed, e.g. <code>Component[Args, Kwargs, ...]</code>, the args, kwargs, slots, and data are validated against the given types. (See <a href=https://github.com/django-components/django-components#runtime-input-validation-with-types>Runtime input validation with types</a>)</p> </li> <li> <p>Render hooks - Set <code>on_render_before</code> and <code>on_render_after</code> methods on <code>Component</code> to intercept or modify the template or context before rendering, or the rendered result afterwards. (See <a href=https://github.com/django-components/django-components#component-hooks>Component hooks</a>)</p> </li> <li> <p><code>component_vars.is_filled</code> context variable can be accessed from within <code>on_render_before</code> and <code>on_render_after</code> hooks as <code>self.is_filled.my_slot</code></p> </li> </ul> <h2 id=095>0.95<a class=headerlink href=#095 title="Permanent link">¤</a></h2> <h4 id=feat_12>Feat<a class=headerlink href=#feat_12 title="Permanent link">¤</a></h4> <ul> <li>Added support for dynamic components, where the component name is passed as a variable. (See <a href=https://github.com/django-components/django-components#dynamic-components>Dynamic components</a>)</li> </ul> <h4 id=refactor_12>Refactor<a class=headerlink href=#refactor_12 title="Permanent link">¤</a></h4> <ul> <li>Changed <code>Component.input</code> to raise <code>RuntimeError</code> if accessed outside of render context. Previously it returned <code>None</code> if unset.</li> </ul> <h2 id=v094>v0.94<a class=headerlink href=#v094 title="Permanent link">¤</a></h2> <h4 id=feat_13>Feat<a class=headerlink href=#feat_13 title="Permanent link">¤</a></h4> <ul> <li> <p>django_components now automatically configures Django to support multi-line tags. (See <a href=https://github.com/django-components/django-components#multi-line-tags>Multi-line tags</a>)</p> </li> <li> <p>New setting <code>reload_on_template_change</code>. Set this to <code>True</code> to reload the dev server on changes to component template files. (See <a href=https://github.com/django-components/django-components#reload-dev-server-on-component-file-changes>Reload dev server on component file changes</a>)</p> </li> </ul> <h2 id=v093>v0.93<a class=headerlink href=#v093 title="Permanent link">¤</a></h2> <h4 id=feat_14>Feat<a class=headerlink href=#feat_14 title="Permanent link">¤</a></h4> <ul> <li> <p>Spread operator <code>...dict</code> inside template tags. (See <a href=https://github.com/django-components/django-components#spread-operator>Spread operator</a>)</p> </li> <li> <p>Use template tags inside string literals in component inputs. (See <a href=https://github.com/django-components/django-components#use-template-tags-inside-component-inputs>Use template tags inside component inputs</a>)</p> </li> <li> <p>Dynamic slots, fills and provides - The <code>name</code> argument for these can now be a variable, a template expression, or via spread operator</p> </li> <li> <p>Component library authors can now configure <code>CONTEXT_BEHAVIOR</code> and <code>TAG_FORMATTER</code> settings independently from user settings.</p> </li> </ul> <h2 id=v092>🚨📢 v0.92<a class=headerlink href=#v092 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_3>BREAKING CHANGES<a class=headerlink href=#breaking-changes_3 title="Permanent link">¤</a></h4> <ul> <li><code>Component</code> class is no longer a subclass of <code>View</code>. To configure the <code>View</code> class, set the <code>Component.View</code> nested class. HTTP methods like <code>get</code> or <code>post</code> can still be defined directly on <code>Component</code> class, and <code>Component.as_view()</code> internally calls <code>Component.View.as_view()</code>. (See <a href=https://github.com/django-components/django-components#modifying-the-view-class>Modifying the View class</a>)</li> </ul> <h4 id=feat_15>Feat<a class=headerlink href=#feat_15 title="Permanent link">¤</a></h4> <ul> <li> <p>The inputs (args, kwargs, slots, context, ...) that you pass to <code>Component.render()</code> can be accessed from within <code>get_context_data</code>, <code>get_template</code> and <code>get_template_name</code> via <code>self.input</code>. (See <a href=https://github.com/django-components/django-components#accessing-data-passed-to-the-component>Accessing data passed to the component</a>)</p> </li> <li> <p>Typing: <code>Component</code> class supports generics that specify types for <code>Component.render</code> (See <a href=https://github.com/django-components/django-components#adding-type-hints-with-generics>Adding type hints with Generics</a>)</p> </li> </ul> <h2 id=v090>v0.90<a class=headerlink href=#v090 title="Permanent link">¤</a></h2> <h4 id=feat_16>Feat<a class=headerlink href=#feat_16 title="Permanent link">¤</a></h4> <ul> <li> <p>All tags (<code>component</code>, <code>slot</code>, <code>fill</code>, ...) now support "self-closing" or "inline" form, where you can omit the closing tag:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-25-1 name=__codelineno-25-1 href=#__codelineno-25-1></a><span class=c>{# Before #}</span>
+<a id=__codelineno-25-2 name=__codelineno-25-2 href=#__codelineno-25-2></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;button&quot;</span> <span class=cp>%}{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
+<a id=__codelineno-25-3 name=__codelineno-25-3 href=#__codelineno-25-3></a><span class=c>{# After #}</span>
+<a id=__codelineno-25-4 name=__codelineno-25-4 href=#__codelineno-25-4></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;button&quot;</span> <span class=o>/</span> <span class=cp>%}</span>
+</code></pre></div> </li> <li> <p>All tags now support the "dictionary key" or "aggregate" syntax (<code>kwarg:key=val</code>):</p> <div class=highlight><pre><span></span><code><a id=__codelineno-26-1 name=__codelineno-26-1 href=#__codelineno-26-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;button&quot;</span> <span class=nv>attrs</span><span class=o>:</span><span class=nv>class</span><span class=o>=</span><span class=s2>&quot;hidden&quot;</span> <span class=cp>%}</span>
+</code></pre></div> </li> <li> <p>You can change how the components are written in the template with <a href=https://github.com/django-components/django-components#customizing-component-tags-with-tagformatter>TagFormatter</a>.</p> <p>The default is <code>django_components.component_formatter</code>:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-27-1 name=__codelineno-27-1 href=#__codelineno-27-1></a><span class=cp>{%</span> <span class=k>component</span> <span class=s2>&quot;button&quot;</span> <span class=nv>href</span><span class=o>=</span><span class=s2>&quot;...&quot;</span> <span class=nv>disabled</span> <span class=cp>%}</span>
 <a id=__codelineno-27-2 name=__codelineno-27-2 href=#__codelineno-27-2></a><span class=x>    Click me!</span>
-<a id=__codelineno-27-3 name=__codelineno-27-3 href=#__codelineno-27-3></a><span class=cp>{%</span> <span class=k>endbutton</span> <span class=cp>%}</span>
-</code></pre></div> </li> </ul> <h2 id=v085>🚨📢 v0.85<a class=headerlink href=#v085 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_4>BREAKING CHANGES<a class=headerlink href=#breaking-changes_4 title="Permanent link">¤</a></h4> <ul> <li> <p>Autodiscovery module resolution changed. Following undocumented behavior was removed:</p> <ul> <li> <p>Previously, autodiscovery also imported any <code>[app]/components.py</code> files, and used <code>SETTINGS_MODULE</code> to search for component dirs.</p> <p>To migrate from:</p> <ul> <li> <p><code>[app]/components.py</code> - Define each module in <code>COMPONENTS.libraries</code> setting, or import each module inside the <code>AppConfig.ready()</code> hook in respective <code>apps.py</code> files.</p> </li> <li> <p><code>SETTINGS_MODULE</code> - Define component dirs using <code>STATICFILES_DIRS</code></p> </li> </ul> </li> <li> <p>Previously, autodiscovery handled relative files in <code>STATICFILES_DIRS</code>. To align with Django, <code>STATICFILES_DIRS</code> now must be full paths (<a href=https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-STATICFILES_DIRS>Django docs</a>).</p> </li> </ul> </li> </ul> <h2 id=v081>🚨📢 v0.81<a class=headerlink href=#v081 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_5>BREAKING CHANGES<a class=headerlink href=#breaking-changes_5 title="Permanent link">¤</a></h4> <ul> <li>The order of arguments to <code>render_to_response</code> has changed, to align with the (now public) <code>render</code> method of <code>Component</code> class.</li> </ul> <h4 id=feat_16>Feat<a class=headerlink href=#feat_16 title="Permanent link">¤</a></h4> <ul> <li> <p><code>Component.render()</code> is public and documented</p> </li> <li> <p>Slots passed <code>render_to_response</code> and <code>render</code> can now be rendered also as functions.</p> </li> </ul> <h2 id=v080>v0.80<a class=headerlink href=#v080 title="Permanent link">¤</a></h2> <h4 id=feat_17>Feat<a class=headerlink href=#feat_17 title="Permanent link">¤</a></h4> <ul> <li>Vue-like provide/inject with the <code>{% provide %}</code> tag and <code>inject()</code> method.</li> </ul> <h2 id=v079>🚨📢 v0.79<a class=headerlink href=#v079 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_6>BREAKING CHANGES<a class=headerlink href=#breaking-changes_6 title="Permanent link">¤</a></h4> <ul> <li>Default value for the <code>COMPONENTS.context_behavior</code> setting was changes from <code>"isolated"</code> to <code>"django"</code>. If you did not set this value explicitly before, this may be a breaking change. See the rationale for change <a href=https://github.com/django-components/django-components/issues/498>here</a>.</li> </ul> <h2 id=v077>🚨📢 v0.77<a class=headerlink href=#v077 title="Permanent link">¤</a></h2> <h4 id=breaking>BREAKING<a class=headerlink href=#breaking title="Permanent link">¤</a></h4> <ul> <li> <p>The syntax for accessing default slot content has changed from</p> <div class=highlight><pre><span></span><code><a id=__codelineno-28-1 name=__codelineno-28-1 href=#__codelineno-28-1></a><span class=cp>{%</span> <span class=k>fill</span> <span class=s2>&quot;my_slot&quot;</span> <span class=k>as</span> <span class=s2>&quot;alias&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-28-2 name=__codelineno-28-2 href=#__codelineno-28-2></a><span class=x>    </span><span class=cp>{{</span> <span class=nv>alias.default</span> <span class=cp>}}</span>
-<a id=__codelineno-28-3 name=__codelineno-28-3 href=#__codelineno-28-3></a><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
-</code></pre></div> <p>to</p> <div class=highlight><pre><span></span><code><a id=__codelineno-29-1 name=__codelineno-29-1 href=#__codelineno-29-1></a><span class=cp>{%</span> <span class=k>fill</span> <span class=s2>&quot;my_slot&quot;</span> <span class=nv>default</span><span class=o>=</span><span class=s2>&quot;alias&quot;</span> <span class=cp>%}</span>
-<a id=__codelineno-29-2 name=__codelineno-29-2 href=#__codelineno-29-2></a><span class=x>    </span><span class=cp>{{</span> <span class=nv>alias</span> <span class=cp>}}</span>
+<a id=__codelineno-27-3 name=__codelineno-27-3 href=#__codelineno-27-3></a><span class=cp>{%</span> <span class=k>endcomponent</span> <span class=cp>%}</span>
+</code></pre></div> <p>While <code>django_components.shorthand_component_formatter</code> allows you to write components like so:</p> <div class=highlight><pre><span></span><code><a id=__codelineno-28-1 name=__codelineno-28-1 href=#__codelineno-28-1></a><span class=cp>{%</span> <span class=k>button</span> <span class=nv>href</span><span class=o>=</span><span class=s2>&quot;...&quot;</span> <span class=nv>disabled</span> <span class=cp>%}</span>
+<a id=__codelineno-28-2 name=__codelineno-28-2 href=#__codelineno-28-2></a><span class=x>    Click me!</span>
+<a id=__codelineno-28-3 name=__codelineno-28-3 href=#__codelineno-28-3></a><span class=cp>{%</span> <span class=k>endbutton</span> <span class=cp>%}</span>
+</code></pre></div> </li> </ul> <h2 id=v085>🚨📢 v0.85<a class=headerlink href=#v085 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_4>BREAKING CHANGES<a class=headerlink href=#breaking-changes_4 title="Permanent link">¤</a></h4> <ul> <li> <p>Autodiscovery module resolution changed. Following undocumented behavior was removed:</p> <ul> <li> <p>Previously, autodiscovery also imported any <code>[app]/components.py</code> files, and used <code>SETTINGS_MODULE</code> to search for component dirs.</p> <p>To migrate from:</p> <ul> <li> <p><code>[app]/components.py</code> - Define each module in <code>COMPONENTS.libraries</code> setting, or import each module inside the <code>AppConfig.ready()</code> hook in respective <code>apps.py</code> files.</p> </li> <li> <p><code>SETTINGS_MODULE</code> - Define component dirs using <code>STATICFILES_DIRS</code></p> </li> </ul> </li> <li> <p>Previously, autodiscovery handled relative files in <code>STATICFILES_DIRS</code>. To align with Django, <code>STATICFILES_DIRS</code> now must be full paths (<a href=https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-STATICFILES_DIRS>Django docs</a>).</p> </li> </ul> </li> </ul> <h2 id=v081>🚨📢 v0.81<a class=headerlink href=#v081 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_5>BREAKING CHANGES<a class=headerlink href=#breaking-changes_5 title="Permanent link">¤</a></h4> <ul> <li>The order of arguments to <code>render_to_response</code> has changed, to align with the (now public) <code>render</code> method of <code>Component</code> class.</li> </ul> <h4 id=feat_17>Feat<a class=headerlink href=#feat_17 title="Permanent link">¤</a></h4> <ul> <li> <p><code>Component.render()</code> is public and documented</p> </li> <li> <p>Slots passed <code>render_to_response</code> and <code>render</code> can now be rendered also as functions.</p> </li> </ul> <h2 id=v080>v0.80<a class=headerlink href=#v080 title="Permanent link">¤</a></h2> <h4 id=feat_18>Feat<a class=headerlink href=#feat_18 title="Permanent link">¤</a></h4> <ul> <li>Vue-like provide/inject with the <code>{% provide %}</code> tag and <code>inject()</code> method.</li> </ul> <h2 id=v079>🚨📢 v0.79<a class=headerlink href=#v079 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_6>BREAKING CHANGES<a class=headerlink href=#breaking-changes_6 title="Permanent link">¤</a></h4> <ul> <li>Default value for the <code>COMPONENTS.context_behavior</code> setting was changes from <code>"isolated"</code> to <code>"django"</code>. If you did not set this value explicitly before, this may be a breaking change. See the rationale for change <a href=https://github.com/django-components/django-components/issues/498>here</a>.</li> </ul> <h2 id=v077>🚨📢 v0.77<a class=headerlink href=#v077 title="Permanent link">¤</a></h2> <h4 id=breaking>BREAKING<a class=headerlink href=#breaking title="Permanent link">¤</a></h4> <ul> <li> <p>The syntax for accessing default slot content has changed from</p> <div class=highlight><pre><span></span><code><a id=__codelineno-29-1 name=__codelineno-29-1 href=#__codelineno-29-1></a><span class=cp>{%</span> <span class=k>fill</span> <span class=s2>&quot;my_slot&quot;</span> <span class=k>as</span> <span class=s2>&quot;alias&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-29-2 name=__codelineno-29-2 href=#__codelineno-29-2></a><span class=x>    </span><span class=cp>{{</span> <span class=nv>alias.default</span> <span class=cp>}}</span>
 <a id=__codelineno-29-3 name=__codelineno-29-3 href=#__codelineno-29-3></a><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
-</code></pre></div> </li> </ul> <h2 id=v074>v0.74<a class=headerlink href=#v074 title="Permanent link">¤</a></h2> <h4 id=feat_18>Feat<a class=headerlink href=#feat_18 title="Permanent link">¤</a></h4> <ul> <li> <p><code>{% html_attrs %}</code> tag for formatting data as HTML attributes</p> </li> <li> <p><code>prefix:key=val</code> construct for passing dicts to components</p> </li> </ul> <h2 id=v070>🚨📢 v0.70<a class=headerlink href=#v070 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_7>BREAKING CHANGES<a class=headerlink href=#breaking-changes_7 title="Permanent link">¤</a></h4> <ul> <li> <p><code>{% if_filled "my_slot" %}</code> tags were replaced with <code>{{ component_vars.is_filled.my_slot }}</code> variables.</p> </li> <li> <p>Simplified settings - <code>slot_context_behavior</code> and <code>context_behavior</code> were merged. See the <a href=https://github.com/django-components/django-components#context-behavior>documentation</a> for more details.</p> </li> </ul> <h2 id=v067>v0.67<a class=headerlink href=#v067 title="Permanent link">¤</a></h2> <h4 id=refactor_13>Refactor<a class=headerlink href=#refactor_13 title="Permanent link">¤</a></h4> <ul> <li>Changed the default way how context variables are resolved in slots. See the <a href=https://github.com/django-components/django-components/tree/0.67#isolate-components-slots>documentation</a> for more details.</li> </ul> <h2 id=v050>🚨📢 v0.50<a class=headerlink href=#v050 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_8>BREAKING CHANGES<a class=headerlink href=#breaking-changes_8 title="Permanent link">¤</a></h4> <ul> <li> <p><code>{% component_block %}</code> is now <code>{% component %}</code>, and <code>{% component %}</code> blocks need an ending <code>{% endcomponent %}</code> tag.</p> <p>The new <code>python manage.py upgradecomponent</code> command can be used to upgrade a directory (use <code>--path</code> argument to point to each dir) of templates that use components to the new syntax automatically.</p> <p>This change is done to simplify the API in anticipation of a 1.0 release of django_components. After 1.0 we intend to be stricter with big changes like this in point releases.</p> </li> </ul> <h2 id=v034>v0.34<a class=headerlink href=#v034 title="Permanent link">¤</a></h2> <h4 id=feat_19>Feat<a class=headerlink href=#feat_19 title="Permanent link">¤</a></h4> <ul> <li>Components as views, which allows you to handle requests and render responses from within a component. See the <a href=https://github.com/django-components/django-components#use-components-as-views>documentation</a> for more details.</li> </ul> <h2 id=v028>v0.28<a class=headerlink href=#v028 title="Permanent link">¤</a></h2> <h4 id=feat_20>Feat<a class=headerlink href=#feat_20 title="Permanent link">¤</a></h4> <ul> <li>'implicit' slot filling and the <code>default</code> option for <code>slot</code> tags.</li> </ul> <h2 id=v027>v0.27<a class=headerlink href=#v027 title="Permanent link">¤</a></h2> <h4 id=feat_21>Feat<a class=headerlink href=#feat_21 title="Permanent link">¤</a></h4> <ul> <li>A second installable app <code>django_components.safer_staticfiles</code>. It provides the same behavior as <code>django.contrib.staticfiles</code> but with extra security guarantees (more info below in <a href=https://github.com/django-components/django-components#security-notes>Security Notes</a>).</li> </ul> <h2 id=v026>🚨📢 v0.26<a class=headerlink href=#v026 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_9>BREAKING CHANGES<a class=headerlink href=#breaking-changes_9 title="Permanent link">¤</a></h4> <ul> <li> <p>Changed the syntax for <code>{% slot %}</code> tags. From now on, we separate defining a slot (<code>{% slot %}</code>) from filling a slot with content (<code>{% fill %}</code>). This means you will likely need to change a lot of slot tags to fill.</p> <p>We understand this is annoying, but it's the only way we can get support for nested slots that fill in other slots, which is a very nice feature to have access to. Hoping that this will feel worth it!</p> </li> </ul> <h2 id=v022>v0.22<a class=headerlink href=#v022 title="Permanent link">¤</a></h2> <h4 id=feat_22>Feat<a class=headerlink href=#feat_22 title="Permanent link">¤</a></h4> <ul> <li> <p>All files inside components subdirectores are autoimported to simplify setup.</p> <p>An existing project might start to get <code>AlreadyRegistered</code> errors because of this. To solve this, either remove your custom loading of components, or set <code>"autodiscover": False</code> in <code>settings.COMPONENTS</code>.</p> </li> </ul> <h2 id=v017>v0.17<a class=headerlink href=#v017 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_10>BREAKING CHANGES<a class=headerlink href=#breaking-changes_10 title="Permanent link">¤</a></h4> <ul> <li> <p>Renamed <code>Component.context</code> and <code>Component.template</code> to <code>get_context_data</code> and <code>get_template_name</code>. The old methods still work, but emit a deprecation warning.</p> <p>This change was done to sync naming with Django's class based views, and make using django-components more familiar to Django users. <code>Component.context</code> and <code>Component.template</code> will be removed when version 1.0 is released.</p> </li> </ul> <aside class=md-source-file> <span class=md-source-file__fact> <span class=md-icon title="Last update"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg> </span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-timeago" title="December 3, 2024 11:32:21"><span class=timeago datetime=2024-12-03T11:32:21+00:00 locale=en></span></span><span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_date" title="December 3, 2024 11:32:21">2024-12-03</span> </span> <span class=md-source-file__fact> <span class=md-icon title=Contributors> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 4a4 4 0 0 1 4 4 4 4 0 0 1-4 4 4 4 0 0 1-4-4 4 4 0 0 1 4-4m0 10c4.42 0 8 1.79 8 4v2H4v-2c0-2.21 3.58-4 8-4"/></svg> </span> <nav> <a href=mailto:juraj.oravec.josefson@gmail.com>Juro Oravec</a> </nav> </span> </aside> </article> </div> <script>var tabs=__md_get("__tabs");if(Array.isArray(tabs))e:for(var set of document.querySelectorAll(".tabbed-set")){var labels=set.querySelector(".tabbed-labels");for(var tab of tabs)for(var label of labels.getElementsByTagName("label"))if(label.innerText.trim()===tab){var input=document.getElementById(label.htmlFor);input.checked=!0;continue e}}</script> <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script> </div> <button type=button class="md-top md-icon" data-md-component=top hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg> Back to top </button> </main> <footer class=md-footer> <nav class="md-footer__inner md-grid" aria-label=Footer> <a href=../reference/testing_api/ class="md-footer__link md-footer__link--prev" aria-label="Previous: Testing API"> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg> </div> <div class=md-footer__title> <span class=md-footer__direction> Previous </span> <div class=md-ellipsis> Testing API </div> </div> </a> </nav> <div class="md-footer-meta md-typeset"> <div class="md-footer-meta__inner md-grid"> <div class=md-copyright> Made with <a href=https://squidfunk.github.io/mkdocs-material/ target=_blank rel=noopener> Material for MkDocs </a> </div> <div class=md-social> <a href=https://github.com/django-components/django-components target=_blank rel=noopener title=github.com class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </a> <a href=https://pypi.org/project/django-components/ target=_blank rel=noopener title=pypi.org class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 448 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M439.8 200.5c-7.7-30.9-22.3-54.2-53.4-54.2h-40.1v47.4c0 36.8-31.2 67.8-66.8 67.8H172.7c-29.2 0-53.4 25-53.4 54.3v101.8c0 29 25.2 46 53.4 54.3 33.8 9.9 66.3 11.7 106.8 0 26.9-7.8 53.4-23.5 53.4-54.3v-40.7H226.2v-13.6h160.2c31.1 0 42.6-21.7 53.4-54.2 11.2-33.5 10.7-65.7 0-108.6M286.2 404c11.1 0 20.1 9.1 20.1 20.3 0 11.3-9 20.4-20.1 20.4-11 0-20.1-9.2-20.1-20.4.1-11.3 9.1-20.3 20.1-20.3M167.8 248.1h106.8c29.7 0 53.4-24.5 53.4-54.3V91.9c0-29-24.4-50.7-53.4-55.6-35.8-5.9-74.7-5.6-106.8.1-45.2 8-53.4 24.7-53.4 55.6v40.7h106.9v13.6h-147c-31.1 0-58.3 18.7-66.8 54.2-9.8 40.7-10.2 66.1 0 108.6 7.6 31.6 25.7 54.2 56.8 54.2H101v-48.8c0-35.3 30.5-66.4 66.8-66.4m-6.7-142.6c-11.1 0-20.1-9.1-20.1-20.3.1-11.3 9-20.4 20.1-20.4 11 0 20.1 9.2 20.1 20.4s-9 20.3-20.1 20.3"/></svg> </a> </div> </div> </div> </footer> </div> <div class=md-dialog data-md-component=dialog> <div class="md-dialog__inner md-typeset"></div> </div> <div class=md-progress data-md-component=progress role=progressbar></div> <script id=__config type=application/json>{"base": "..", "features": ["content.action.edit", "content.action.view", "content.code.annotate", "content.code.copy", "content.tabs.link", "navigation.expand", "navigation.footer", "navigation.instant", "navigation.instant.progress", "navigation.indexes", "navigation.sections", "navigation.tabs", "navigation.tracking", "navigation.top", "search.highlight", "search.share", "search.suggest", "toc.follow"], "search": "../assets/javascripts/workers/search.f8cc74c7.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"alias": true, "default": ["dev"], "provider": "mike"}}</script> <script src=../assets/javascripts/bundle.c8b220af.min.js></script> <script src=../assets/_markdown_exec_pyodide.js></script> <script src=../js/timeago.min.js></script> <script src=../js/timeago_mkdocs_material.js></script> </body> </html>
\ No newline at end of file
+</code></pre></div> <p>to</p> <div class=highlight><pre><span></span><code><a id=__codelineno-30-1 name=__codelineno-30-1 href=#__codelineno-30-1></a><span class=cp>{%</span> <span class=k>fill</span> <span class=s2>&quot;my_slot&quot;</span> <span class=nv>default</span><span class=o>=</span><span class=s2>&quot;alias&quot;</span> <span class=cp>%}</span>
+<a id=__codelineno-30-2 name=__codelineno-30-2 href=#__codelineno-30-2></a><span class=x>    </span><span class=cp>{{</span> <span class=nv>alias</span> <span class=cp>}}</span>
+<a id=__codelineno-30-3 name=__codelineno-30-3 href=#__codelineno-30-3></a><span class=cp>{%</span> <span class=k>endfill</span> <span class=cp>%}</span>
+</code></pre></div> </li> </ul> <h2 id=v074>v0.74<a class=headerlink href=#v074 title="Permanent link">¤</a></h2> <h4 id=feat_19>Feat<a class=headerlink href=#feat_19 title="Permanent link">¤</a></h4> <ul> <li> <p><code>{% html_attrs %}</code> tag for formatting data as HTML attributes</p> </li> <li> <p><code>prefix:key=val</code> construct for passing dicts to components</p> </li> </ul> <h2 id=v070>🚨📢 v0.70<a class=headerlink href=#v070 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_7>BREAKING CHANGES<a class=headerlink href=#breaking-changes_7 title="Permanent link">¤</a></h4> <ul> <li> <p><code>{% if_filled "my_slot" %}</code> tags were replaced with <code>{{ component_vars.is_filled.my_slot }}</code> variables.</p> </li> <li> <p>Simplified settings - <code>slot_context_behavior</code> and <code>context_behavior</code> were merged. See the <a href=https://github.com/django-components/django-components#context-behavior>documentation</a> for more details.</p> </li> </ul> <h2 id=v067>v0.67<a class=headerlink href=#v067 title="Permanent link">¤</a></h2> <h4 id=refactor_13>Refactor<a class=headerlink href=#refactor_13 title="Permanent link">¤</a></h4> <ul> <li>Changed the default way how context variables are resolved in slots. See the <a href=https://github.com/django-components/django-components/tree/0.67#isolate-components-slots>documentation</a> for more details.</li> </ul> <h2 id=v050>🚨📢 v0.50<a class=headerlink href=#v050 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_8>BREAKING CHANGES<a class=headerlink href=#breaking-changes_8 title="Permanent link">¤</a></h4> <ul> <li> <p><code>{% component_block %}</code> is now <code>{% component %}</code>, and <code>{% component %}</code> blocks need an ending <code>{% endcomponent %}</code> tag.</p> <p>The new <code>python manage.py upgradecomponent</code> command can be used to upgrade a directory (use <code>--path</code> argument to point to each dir) of templates that use components to the new syntax automatically.</p> <p>This change is done to simplify the API in anticipation of a 1.0 release of django_components. After 1.0 we intend to be stricter with big changes like this in point releases.</p> </li> </ul> <h2 id=v034>v0.34<a class=headerlink href=#v034 title="Permanent link">¤</a></h2> <h4 id=feat_20>Feat<a class=headerlink href=#feat_20 title="Permanent link">¤</a></h4> <ul> <li>Components as views, which allows you to handle requests and render responses from within a component. See the <a href=https://github.com/django-components/django-components#use-components-as-views>documentation</a> for more details.</li> </ul> <h2 id=v028>v0.28<a class=headerlink href=#v028 title="Permanent link">¤</a></h2> <h4 id=feat_21>Feat<a class=headerlink href=#feat_21 title="Permanent link">¤</a></h4> <ul> <li>'implicit' slot filling and the <code>default</code> option for <code>slot</code> tags.</li> </ul> <h2 id=v027>v0.27<a class=headerlink href=#v027 title="Permanent link">¤</a></h2> <h4 id=feat_22>Feat<a class=headerlink href=#feat_22 title="Permanent link">¤</a></h4> <ul> <li>A second installable app <code>django_components.safer_staticfiles</code>. It provides the same behavior as <code>django.contrib.staticfiles</code> but with extra security guarantees (more info below in <a href=https://github.com/django-components/django-components#security-notes>Security Notes</a>).</li> </ul> <h2 id=v026>🚨📢 v0.26<a class=headerlink href=#v026 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_9>BREAKING CHANGES<a class=headerlink href=#breaking-changes_9 title="Permanent link">¤</a></h4> <ul> <li> <p>Changed the syntax for <code>{% slot %}</code> tags. From now on, we separate defining a slot (<code>{% slot %}</code>) from filling a slot with content (<code>{% fill %}</code>). This means you will likely need to change a lot of slot tags to fill.</p> <p>We understand this is annoying, but it's the only way we can get support for nested slots that fill in other slots, which is a very nice feature to have access to. Hoping that this will feel worth it!</p> </li> </ul> <h2 id=v022>v0.22<a class=headerlink href=#v022 title="Permanent link">¤</a></h2> <h4 id=feat_23>Feat<a class=headerlink href=#feat_23 title="Permanent link">¤</a></h4> <ul> <li> <p>All files inside components subdirectores are autoimported to simplify setup.</p> <p>An existing project might start to get <code>AlreadyRegistered</code> errors because of this. To solve this, either remove your custom loading of components, or set <code>"autodiscover": False</code> in <code>settings.COMPONENTS</code>.</p> </li> </ul> <h2 id=v017>v0.17<a class=headerlink href=#v017 title="Permanent link">¤</a></h2> <h4 id=breaking-changes_10>BREAKING CHANGES<a class=headerlink href=#breaking-changes_10 title="Permanent link">¤</a></h4> <ul> <li> <p>Renamed <code>Component.context</code> and <code>Component.template</code> to <code>get_context_data</code> and <code>get_template_name</code>. The old methods still work, but emit a deprecation warning.</p> <p>This change was done to sync naming with Django's class based views, and make using django-components more familiar to Django users. <code>Component.context</code> and <code>Component.template</code> will be removed when version 1.0 is released.</p> </li> </ul> <aside class=md-source-file> <span class=md-source-file__fact> <span class=md-icon title="Last update"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg> </span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-timeago" title="December 3, 2024 11:32:21"><span class=timeago datetime=2024-12-03T11:32:21+00:00 locale=en></span></span><span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_date" title="December 3, 2024 11:32:21">2024-12-03</span> </span> <span class=md-source-file__fact> <span class=md-icon title=Contributors> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 4a4 4 0 0 1 4 4 4 4 0 0 1-4 4 4 4 0 0 1-4-4 4 4 0 0 1 4-4m0 10c4.42 0 8 1.79 8 4v2H4v-2c0-2.21 3.58-4 8-4"/></svg> </span> <nav> <a href=mailto:juraj.oravec.josefson@gmail.com>Juro Oravec</a> </nav> </span> </aside> </article> </div> <script>var tabs=__md_get("__tabs");if(Array.isArray(tabs))e:for(var set of document.querySelectorAll(".tabbed-set")){var labels=set.querySelector(".tabbed-labels");for(var tab of tabs)for(var label of labels.getElementsByTagName("label"))if(label.innerText.trim()===tab){var input=document.getElementById(label.htmlFor);input.checked=!0;continue e}}</script> <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script> </div> <button type=button class="md-top md-icon" data-md-component=top hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg> Back to top </button> </main> <footer class=md-footer> <nav class="md-footer__inner md-grid" aria-label=Footer> <a href=../reference/testing_api/ class="md-footer__link md-footer__link--prev" aria-label="Previous: Testing API"> <div class="md-footer__button md-icon"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg> </div> <div class=md-footer__title> <span class=md-footer__direction> Previous </span> <div class=md-ellipsis> Testing API </div> </div> </a> </nav> <div class="md-footer-meta md-typeset"> <div class="md-footer-meta__inner md-grid"> <div class=md-copyright> Made with <a href=https://squidfunk.github.io/mkdocs-material/ target=_blank rel=noopener> Material for MkDocs </a> </div> <div class=md-social> <a href=https://github.com/django-components/django-components target=_blank rel=noopener title=github.com class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 496 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8M97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg> </a> <a href=https://pypi.org/project/django-components/ target=_blank rel=noopener title=pypi.org class=md-social__link> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 448 512"><!-- Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M439.8 200.5c-7.7-30.9-22.3-54.2-53.4-54.2h-40.1v47.4c0 36.8-31.2 67.8-66.8 67.8H172.7c-29.2 0-53.4 25-53.4 54.3v101.8c0 29 25.2 46 53.4 54.3 33.8 9.9 66.3 11.7 106.8 0 26.9-7.8 53.4-23.5 53.4-54.3v-40.7H226.2v-13.6h160.2c31.1 0 42.6-21.7 53.4-54.2 11.2-33.5 10.7-65.7 0-108.6M286.2 404c11.1 0 20.1 9.1 20.1 20.3 0 11.3-9 20.4-20.1 20.4-11 0-20.1-9.2-20.1-20.4.1-11.3 9.1-20.3 20.1-20.3M167.8 248.1h106.8c29.7 0 53.4-24.5 53.4-54.3V91.9c0-29-24.4-50.7-53.4-55.6-35.8-5.9-74.7-5.6-106.8.1-45.2 8-53.4 24.7-53.4 55.6v40.7h106.9v13.6h-147c-31.1 0-58.3 18.7-66.8 54.2-9.8 40.7-10.2 66.1 0 108.6 7.6 31.6 25.7 54.2 56.8 54.2H101v-48.8c0-35.3 30.5-66.4 66.8-66.4m-6.7-142.6c-11.1 0-20.1-9.1-20.1-20.3.1-11.3 9-20.4 20.1-20.4 11 0 20.1 9.2 20.1 20.4s-9 20.3-20.1 20.3"/></svg> </a> </div> </div> </div> </footer> </div> <div class=md-dialog data-md-component=dialog> <div class="md-dialog__inner md-typeset"></div> </div> <div class=md-progress data-md-component=progress role=progressbar></div> <script id=__config type=application/json>{"base": "..", "features": ["content.action.edit", "content.action.view", "content.code.annotate", "content.code.copy", "content.tabs.link", "navigation.expand", "navigation.footer", "navigation.instant", "navigation.instant.progress", "navigation.indexes", "navigation.sections", "navigation.tabs", "navigation.tracking", "navigation.top", "search.highlight", "search.share", "search.suggest", "toc.follow"], "search": "../assets/javascripts/workers/search.f8cc74c7.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"alias": true, "default": ["dev"], "provider": "mike"}}</script> <script src=../assets/javascripts/bundle.c8b220af.min.js></script> <script src=../assets/_markdown_exec_pyodide.js></script> <script src=../js/timeago.min.js></script> <script src=../js/timeago_mkdocs_material.js></script> </body> </html>
\ No newline at end of file
diff --git a/dev/search/search_index.json b/dev/search/search_index.json
index b65f5815..08af209d 100644
--- a/dev/search/search_index.json
+++ b/dev/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to Django Components","text":"<p><code>django-components</code> combines Django's templating system with the modularity seen in modern frontend frameworks like Vue or React.</p> <p>With <code>django-components</code> you can support Django projects small and large without leaving the Django ecosystem.</p>"},{"location":"#quickstart","title":"Quickstart","text":"<p>A component in django-components can be as simple as a Django template and Python code to declare the component:</p> components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n</code></pre> <p>Or a combination of Django template, Python, CSS, and Javascript:</p> components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> components/calendar/calendar.css<pre><code>.calendar {\n  width: 200px;\n  background: pink;\n}\n</code></pre> components/calendar/calendar.js<pre><code>document.querySelector(\".calendar\").onclick = () =&gt; {\n  alert(\"Clicked calendar!\");\n};\n</code></pre> components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    def get_context_data(self, date):\n        return {\"date\": date}\n</code></pre> <p>Use the component like this:</p> <pre><code>{% component \"calendar\" date=\"2024-11-06\" %}{% endcomponent %}\n</code></pre> <p>And this is what gets rendered:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n  Today's date is &lt;span&gt;2024-11-06&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>Read on to learn about all the exciting details and configuration possibilities!</p> <p>(If you instead prefer to jump right into the code, check out the example project)</p>"},{"location":"#features","title":"Features","text":""},{"location":"#modern-and-modular-ui","title":"Modern and modular UI","text":"<ul> <li>Create self-contained, reusable UI elements.</li> <li>Each component can include its own HTML, CSS, and JS, or additional third-party JS and CSS.</li> <li>HTML, CSS, and JS can be defined on the component class, or loaded from files.</li> </ul> <pre><code>from django_components import Component\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template = \"\"\"\n        &lt;div class=\"calendar\"&gt;\n            Today's date is\n            &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css = \"\"\"\n        .calendar {\n            width: 200px;\n            background: pink;\n        }\n    \"\"\"\n\n    js = \"\"\"\n        document.querySelector(\".calendar\")\n            .addEventListener(\"click\", () =&gt; {\n                alert(\"Clicked calendar!\");\n            });\n    \"\"\"\n\n    # Additional JS and CSS\n    class Media:\n        js = [\"https://cdn.jsdelivr.net/npm/htmx.org@2.1.1/dist/htmx.min.js\"]\n        css = [\"bootstrap/dist/css/bootstrap.min.css\"]\n\n    # Variables available in the template\n    def get_context_data(self, date):\n        return {\n            \"date\": date\n        }\n</code></pre>"},{"location":"#composition-with-slots","title":"Composition with slots","text":"<ul> <li>Render components inside templates with <code>{% component %}</code> tag.</li> <li>Compose them with <code>{% slot %}</code> and <code>{% fill %}</code> tags.</li> <li>Vue-like slot system, including scoped slots.</li> </ul> <pre><code>{% component \"Layout\"\n    bookmarks=bookmarks\n    breadcrumbs=breadcrumbs\n%}\n    {% fill \"header\" %}\n        &lt;div class=\"flex justify-between gap-x-12\"&gt;\n            &lt;div class=\"prose\"&gt;\n                &lt;h3&gt;{{ project.name }}&lt;/h3&gt;\n            &lt;/div&gt;\n            &lt;div class=\"font-semibold text-gray-500\"&gt;\n                {{ project.start_date }} - {{ project.end_date }}\n            &lt;/div&gt;\n        &lt;/div&gt;\n    {% endfill %}\n\n    {# Access data passed to `{% slot %}` with `data` #}\n    {% fill \"tabs\" data=\"tabs_data\" %}\n        {% component \"TabItem\" header=\"Project Info\" %}\n            {% component \"ProjectInfo\"\n                project=project\n                project_tags=project_tags\n                attrs:class=\"py-5\"\n                attrs:width=tabs_data.width\n            / %}\n        {% endcomponent %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"#extended-template-tags","title":"Extended template tags","text":"<p><code>django-components</code> extends Django's template tags syntax with:</p> <ul> <li>Literal lists and dictionaries in template tags</li> <li>Self-closing tags <code>{% mytag / %}</code></li> <li>Multi-line template tags</li> <li>Spread operator <code>...</code> to dynamically pass args or kwargs into the template tag</li> <li>Nested template tags like <code>\"{{ first_name }} {{ last_name }}\"</code></li> <li>Flat definition of dictionary keys <code>attr:key=val</code></li> </ul> <pre><code>{% component \"table\"\n    ...default_attrs\n    title=\"Friend list for {{ user.name }}\"\n    headers=[\"Name\", \"Age\", \"Email\"]\n    data=[\n        {\n            \"name\": \"John\"|upper,\n            \"age\": 30|add:1,\n            \"email\": \"john@example.com\",\n            \"hobbies\": [\"reading\"],\n        },\n        {\n            \"name\": \"Jane\"|upper,\n            \"age\": 25|add:1,\n            \"email\": \"jane@example.com\",\n            \"hobbies\": [\"reading\", \"coding\"],\n        },\n    ],\n    attrs:class=\"py-4 ma-2 border-2 border-gray-300 rounded-md\"\n/ %}\n</code></pre>"},{"location":"#html-fragment-support","title":"HTML fragment support","text":"<p><code>django-components</code> makes intergration with HTMX, AlpineJS or jQuery easy by allowing components to be rendered as HTML fragments:</p> <ul> <li> <p>Components's JS and CSS is loaded automatically when the fragment is inserted into the DOM.</p> </li> <li> <p>Expose components as views with <code>get</code>, <code>post</code>, <code>put</code>, <code>patch</code>, <code>delete</code> methods</p> </li> </ul> <pre><code># components/calendar/calendar.py\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n\n    def get(self, request, *args, **kwargs):\n        page = request.GET.get(\"page\", 1)\n        return self.render_to_response(\n            kwargs={\n                \"page\": page,\n            }\n        )\n\n    def get_context_data(self, page):\n        return {\n            \"page\": page,\n        }\n\n# urls.py\npath(\"calendar/\", Calendar.as_view()),\n</code></pre>"},{"location":"#type-hints","title":"Type hints","text":"<p>Opt-in to type hints by defining types for component's args, kwargs, slots, and more:</p> <pre><code>from typing import NotRequired, Tuple, TypedDict, SlotContent, SlotFunc\n\nButtonArgs = Tuple[int, str]\n\nclass ButtonKwargs(TypedDict):\n    variable: str\n    another: int\n    maybe_var: NotRequired[int] # May be omitted\n\nclass ButtonData(TypedDict):\n    variable: str\n\nclass ButtonSlots(TypedDict):\n    my_slot: NotRequired[SlotFunc]\n    another_slot: SlotContent\n\nButtonType = Component[ButtonArgs, ButtonKwargs, ButtonSlots, ButtonData, JsData, CssData]\n\nclass Button(ButtonType):\n    def get_context_data(self, *args, **kwargs):\n        self.input.args[0]  # int\n        self.input.kwargs[\"variable\"]  # str\n        self.input.slots[\"my_slot\"]  # SlotFunc[MySlotData]\n\n        return {}  # Error: Key \"variable\" is missing\n</code></pre> <p>When you then call <code>Button.render()</code> or <code>Button.render_to_response()</code>, you will get type hints:</p> <pre><code>Button.render(\n    # Error: First arg must be `int`, got `float`\n    args=(1.25, \"abc\"),\n    # Error: Key \"another\" is missing\n    kwargs={\n        \"variable\": \"text\",\n    },\n)\n</code></pre>"},{"location":"#extensions","title":"Extensions","text":"<p>Django-components functionality can be extended with \"extensions\". Extensions allow for powerful customization and integrations. They can:</p> <ul> <li>Tap into lifecycle events, such as when a component is created, deleted, or registered.</li> <li>Add new attributes and methods to the components under an extension-specific nested class.</li> </ul> <p>Some of the planned extensions include:</p> <ul> <li>Caching</li> <li>AlpineJS integration</li> <li>Storybook integration</li> <li>Pydantic validation</li> <li>Component-level benchmarking with asv</li> </ul>"},{"location":"#simple-testing","title":"Simple testing","text":"<ul> <li>Write tests for components with <code>@djc_test</code> decorator.</li> <li>The decorator manages global state, ensuring that tests don't leak.</li> <li>If using <code>pytest</code>, the decorator allows you to parametrize Django or Components settings.</li> <li>The decorator also serves as a stand-in for Django's <code>@override_settings</code>.</li> </ul> <pre><code>from djc_test import djc_test\n\nfrom components.my_component import MyTable\n\n@djc_test\ndef test_my_table():\n    rendered = MyTable.render(\n        kwargs={\n            \"title\": \"My table\",\n        },\n    )\n    assert rendered == \"&lt;table&gt;My table&lt;/table&gt;\"\n</code></pre>"},{"location":"#handle-large-projects-with-ease","title":"Handle large projects with ease","text":"<ul> <li>Components can be infinitely nested.</li> <li>(Soon) Optimize performance with component-level caching</li> </ul>"},{"location":"#debugging-features","title":"Debugging features","text":"<ul> <li>Visual component inspection: Highlight components and slots directly in your browser.</li> <li>Detailed tracing logs to supply AI-agents with context: The logs include component and slot names and IDs, and their position in the tree.</li> </ul>"},{"location":"#sharing-components","title":"Sharing components","text":"<ul> <li>Install and use third-party components from PyPI</li> <li>Or publish your own \"component registry\"</li> <li> <p>Highly customizable - Choose how the components are called in the template (and more):</p> <pre><code>{% component \"calendar\" date=\"2024-11-06\" %}\n{% endcomponent %}\n\n{% calendar date=\"2024-11-06\" %}\n{% endcalendar %}\n</code></pre> </li> </ul>"},{"location":"#other-features","title":"Other features","text":"<ul> <li>Vue-like provide / inject system</li> <li>Format HTML attributes with <code>{% html_attrs %}</code></li> </ul>"},{"location":"#performance","title":"Performance","text":"<p>Our aim is to be at least as fast as Django templates.</p> <p>As of <code>0.130</code>, <code>django-components</code> is ~4x slower than Django templates.</p> Render time django 68.9\u00b10.6ms django-components 259\u00b14ms <p>See the full performance breakdown for more information.</p>"},{"location":"#release-notes","title":"Release notes","text":"<p>Read the Release Notes to see the latest features and fixes.</p>"},{"location":"#community-examples","title":"Community examples","text":"<p>One of our goals with <code>django-components</code> is to make it easy to share components between projects. Head over to the Community examples to see some examples.</p>"},{"location":"#contributing-and-development","title":"Contributing and development","text":"<p>Get involved or sponsor this project - See here</p> <p>Running django-components locally for development - See here</p>"},{"location":"migrating_from_safer_staticfiles/","title":"Migrating from safer_staticfiles","text":"<p>This guide is for you if you're upgrating django_components to v0.100 or later from older versions.</p> <p>In version 0.100, we changed how components' static JS and CSS files are handled. See more in the \"Static files\" section.</p> <p>Migration steps:</p> <ol> <li>Remove <code>django_components.safer_staticfiles</code> from <code>INSTALLED_APPS</code> in your <code>settings.py</code>,    and replace it with <code>django.contrib.staticfiles</code>.</li> </ol> <p>Before:</p> <pre><code>INSTALLED_APPS = [\n   \"django.contrib.admin\",\n   ...\n   # \"django.contrib.staticfiles\",  # &lt;-- ADD\n   \"django_components\",\n   \"django_components.safer_staticfiles\",  # &lt;-- REMOVE\n]\n</code></pre> <p>After:</p> <pre><code>INSTALLED_APPS = [\n   \"django.contrib.admin\",\n   ...\n   \"django.contrib.staticfiles\",\n   \"django_components\",\n]\n</code></pre> <ol> <li>Add <code>STATICFILES_FINDERS</code> to <code>settings.py</code>, and add <code>django_components.finders.ComponentsFileSystemFinder</code>:</li> </ol> <pre><code>STATICFILES_FINDERS = [\n   # Default finders\n   \"django.contrib.staticfiles.finders.FileSystemFinder\",\n   \"django.contrib.staticfiles.finders.AppDirectoriesFinder\",\n   # Django components\n   \"django_components.finders.ComponentsFileSystemFinder\",  # &lt;-- ADDED\n]\n</code></pre> <ol> <li>Add <code>COMPONENTS.dirs</code> to <code>settings.py</code>.</li> </ol> <p>If you previously defined <code>STATICFILES_DIRS</code>, move    only those directories from <code>STATICFILES_DIRS</code> that point to components directories, and keep the rest.</p> <p>E.g. if you have <code>STATICFILES_DIRS</code> like this:</p> <pre><code>STATICFILES_DIRS = [\n   BASE_DIR / \"components\",  # &lt;-- MOVE\n   BASE_DIR / \"myapp\" / \"components\",  # &lt;-- MOVE\n   BASE_DIR / \"assets\",\n]\n</code></pre> <p>Then first two entries point to components dirs, whereas <code>/assets</code> points to non-component static files.    In this case move only the first two paths:</p> <pre><code>COMPONENTS = {\n   \"dirs\": [\n      BASE_DIR / \"components\",  # &lt;-- MOVED\n      BASE_DIR / \"myapp\" / \"components\",  # &lt;-- MOVED\n   ],\n}\n\nSTATICFILES_DIRS = [\n   BASE_DIR / \"assets\",\n]\n</code></pre> <p>Moreover, if you defined app-level component directories in <code>STATICFILES_DIRS</code> before,    you can now define as a RELATIVE path in <code>app_dirs</code>:</p> <pre><code>COMPONENTS = {\n   \"dirs\": [\n      # Search top-level \"/components/\" dir\n      BASE_DIR / \"components\",\n   ],\n   \"app_dirs\": [\n      # Search \"/[app]/components/\" dirs\n      \"components\",\n   ],\n}\n\nSTATICFILES_DIRS = [\n   BASE_DIR / \"assets\",\n]\n</code></pre>"},{"location":"release_notes/","title":"Release notes","text":""},{"location":"release_notes/#v0131","title":"v0.131","text":""},{"location":"release_notes/#feat","title":"Feat","text":"<ul> <li> <p>Support for extensions (plugins) for django-components!</p> <ul> <li>Hook into lifecycle events of django-components</li> <li>Pre-/post-process component inputs, outputs, and templates</li> <li>Add extra methods or attributes to Components</li> <li>Add custom extension-specific CLI commands</li> <li>Add custom extension-specific URL routes</li> </ul> <p>Read more on Extensions.</p> </li> <li> <p>New CLI commands:</p> <ul> <li><code>components list</code> - List all components</li> <li><code>components create &lt;name&gt;</code> - Create a new component (supersedes <code>startcomponent</code>)</li> <li><code>components upgrade</code> - Upgrade a component (supersedes <code>upgradecomponent</code>)</li> <li><code>components ext list</code> - List all extensions</li> <li><code>components ext run &lt;extension&gt; &lt;command&gt;</code> - Run a command added by an extension</li> </ul> </li> <li> <p><code>@djc_test</code> decorator for writing tests that involve Components.</p> <ul> <li>The decorator manages global state, ensuring that tests don't leak.</li> <li>If using <code>pytest</code>, the decorator allows you to parametrize Django or Components settings.</li> <li>The decorator also serves as a stand-in for Django's <code>@override_settings</code>.</li> </ul> <p>See the API reference for <code>@djc_test</code> for more details.</p> </li> <li> <p><code>ComponentRegistry</code> now has a <code>has()</code> method to check if a component is registered    without raising an error.</p> </li> <li> <p>Get all created <code>Component</code> classes with <code>all_components()</code>.</p> </li> <li> <p>Get all created <code>ComponentRegistry</code> instances with <code>all_registries()</code>.</p> </li> </ul>"},{"location":"release_notes/#refactor","title":"Refactor","text":"<ul> <li> <p>The <code>startcomponent</code> and <code>upgradecomponent</code> commands are deprecated, and will be removed in v1.</p> <p>Instead, use <code>components create &lt;name&gt;</code> and <code>components upgrade</code>.</p> </li> </ul>"},{"location":"release_notes/#internal","title":"Internal","text":"<ul> <li>Settings are now loaded only once, and thus are considered immutable once loaded. Previously,   django-components would load settings from <code>settings.COMPONENTS</code> on each access. The new behavior   aligns with Django's settings.</li> </ul>"},{"location":"release_notes/#v0130","title":"v0.130","text":""},{"location":"release_notes/#feat_1","title":"Feat","text":"<ul> <li> <p>Access the HttpRequest object under <code>Component.request</code>.</p> <p>To pass the request object to a component, either: - Render a template or component with <code>RequestContext</code>, - Or set the <code>request</code> kwarg to <code>Component.render()</code> or <code>Component.render_to_response()</code>.</p> <p>Read more on HttpRequest.</p> </li> <li> <p>Access the context processors data under <code>Component.context_processors_data</code>.</p> <p>Context processors data is available only when the component has access to the <code>request</code> object, either by: - Passing the request to <code>Component.render()</code> or <code>Component.render_to_response()</code>, - Or by rendering a template or component with <code>RequestContext</code>, - Or being nested in another component that has access to the request object.</p> <p>The data from context processors is automatically available within the component's template.</p> <p>Read more on HttpRequest.</p> </li> </ul>"},{"location":"release_notes/#v0129","title":"v0.129","text":""},{"location":"release_notes/#fix","title":"Fix","text":"<ul> <li>Fix thread unsafe media resolve validation by moving it to ComponentMedia <code>__post_init</code> (#977</li> <li>Fix bug: Relative path in extends and include does not work when using template_file (#976</li> <li>Fix error when template cache setting (<code>template_cache_size</code>) is set to 0 (#974</li> </ul>"},{"location":"release_notes/#v0128","title":"v0.128","text":""},{"location":"release_notes/#feat_2","title":"Feat","text":"<ul> <li> <p>Configurable cache - Set <code>COMPONENTS.cache</code> to change where and how django-components caches JS and CSS files. (#946)</p> <p>Read more on Caching.</p> </li> <li> <p>Highlight coponents and slots in the UI - We've added two boolean settings <code>COMPONENTS.debug_highlight_components</code> and <code>COMPONENTS.debug_highlight_slots</code>, which can be independently set to <code>True</code>. First will wrap components in a blue border, the second will wrap slots in a red border. (#942)</p> <p>Read more on Troubleshooting.</p> </li> </ul>"},{"location":"release_notes/#refactor_1","title":"Refactor","text":"<ul> <li>Removed use of eval for node validation (#944)</li> </ul>"},{"location":"release_notes/#perf","title":"Perf","text":"<ul> <li> <p>Components can now be infinitely nested. (#936)</p> </li> <li> <p>Component input validation is now 6-7x faster on CPython and PyPy. This previously made up 10-30% of the total render time. (#945)</p> </li> </ul>"},{"location":"release_notes/#v0127","title":"v0.127","text":""},{"location":"release_notes/#fix_1","title":"Fix","text":"<ul> <li>Fix component rendering when using <code>{% cache %}</code> with remote cache and multiple web servers (#930)</li> </ul>"},{"location":"release_notes/#v0126","title":"v0.126","text":""},{"location":"release_notes/#refactor_2","title":"Refactor","text":"<ul> <li>Replaced BeautifulSoup4 with a custom HTML parser.</li> <li>The heuristic for inserting JS and CSS dependenies into the default place has changed.<ul> <li>JS is still inserted at the end of the <code>&lt;body&gt;</code>, and CSS at the end of <code>&lt;head&gt;</code>.</li> <li>However, we find end of <code>&lt;body&gt;</code> by searching for last occurrence of <code>&lt;/body&gt;</code></li> <li>And for the end of <code>&lt;head&gt;</code> we search for the first occurrence of <code>&lt;/head&gt;</code></li> </ul> </li> </ul>"},{"location":"release_notes/#v0125","title":"v0.125","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - We migrated from <code>EmilStenstrom/django-components</code> to <code>django-components/django-components</code>.</p> <p>Repo name and documentation URL changed. Package name remains the same.</p> <p>If you see any broken links or other issues, please report them in #922.</p>"},{"location":"release_notes/#feat_3","title":"Feat","text":"<ul> <li><code>@template_tag</code> and <code>BaseNode</code> - A decorator and a class that allow you to define   custom template tags that will behave similarly to django-components' own template tags.</li> </ul> <p>Read more on Template tags.</p> <p>Template tags defined with <code>@template_tag</code> and <code>BaseNode</code> will have the following features:</p> <ul> <li> <p>Accepting args, kwargs, and flags.</p> </li> <li> <p>Allowing literal lists and dicts as inputs as:</p> <p><code>key=[1, 2, 3]</code> or <code>key={\"a\": 1, \"b\": 2}</code>   - Using template tags tag inputs as:</p> <p><code>{% my_tag key=\"{% lorem 3 w %}\" / %}</code>   - Supporting the flat dictionary definition:</p> <p><code>attr:key=value</code>   - Spreading args and kwargs with <code>...</code>:</p> <p><code>{% my_tag ...args ...kwargs / %}</code>   - Being able to call the template tag as:</p> <p><code>{% my_tag %} ... {% endmy_tag %}</code> or <code>{% my_tag / %}</code></p> </li> </ul>"},{"location":"release_notes/#refactor_3","title":"Refactor","text":"<ul> <li> <p>Refactored template tag input validation. When you now call template tags like   <code>{% slot %}</code>, <code>{% fill %}</code>, <code>{% html_attrs %}</code>, and others, their inputs are now   validated the same way as Python function inputs are.</p> <p>So, for example</p> <pre><code>{% slot \"my_slot\" name=\"content\" / %}\n</code></pre> <p>will raise an error, because the positional argument <code>name</code> is given twice.</p> <p>NOTE: Special kwargs whose keys are not valid Python variable names are not affected by this change. So when you define:</p> <pre><code>{% component data-id=123 / %}\n</code></pre> <p>The <code>data-id</code> will still be accepted as a valid kwarg, assuming that your <code>get_context_data()</code> accepts <code>**kwargs</code>:</p> <pre><code>def get_context_data(self, **kwargs):\n    return {\n        \"data_id\": kwargs[\"data-id\"],\n    }\n</code></pre> </li> </ul>"},{"location":"release_notes/#v0124","title":"v0.124","text":""},{"location":"release_notes/#feat_4","title":"Feat","text":"<ul> <li> <p>Instead of inlining the JS and CSS under <code>Component.js</code> and <code>Component.css</code>, you can move     them to their own files, and link the JS/CSS files with <code>Component.js_file</code>  and <code>Component.css_file</code>.</p> <p>Even when you specify the JS/CSS with <code>Component.js_file</code> or <code>Component.css_file</code>, then you can still access the content under <code>Component.js</code> or <code>Component.css</code> - behind the scenes, the content of the JS/CSS files will be set to <code>Component.js</code> / <code>Component.css</code> upon first access.</p> <p>The same applies to <code>Component.template_file</code>, which will populate <code>Component.template</code> upon first access.</p> <p>With this change, the role of <code>Component.js/css</code> and the JS/CSS in <code>Component.Media</code> has changed:</p> <ul> <li>The JS/CSS defined in <code>Component.js/css</code> or <code>Component.js/css_file</code> is the \"main\" JS/CSS</li> <li>The JS/CSS defined in <code>Component.Media.js/css</code> are secondary or additional</li> </ul> <p>See the updated \"Getting Started\" tutorial</p> </li> </ul>"},{"location":"release_notes/#refactor_4","title":"Refactor","text":"<ul> <li> <p>The canonical way to define a template file was changed from <code>template_name</code> to <code>template_file</code>, to align with the rest of the API.</p> <p><code>template_name</code> remains for backwards compatibility. When you get / set <code>template_name</code>, internally this is proxied to <code>template_file</code>.</p> </li> <li> <p>The undocumented <code>Component.component_id</code> was removed. Instead, use <code>Component.id</code>. Changes:</p> <ul> <li>While <code>component_id</code> was unique every time you instantiated <code>Component</code>, the new <code>id</code> is unique every time you render the component (e.g. with <code>Component.render()</code>)</li> <li>The new <code>id</code> is available only during render, so e.g. from within <code>get_context_data()</code></li> </ul> </li> <li> <p>Component's HTML / CSS / JS are now resolved and loaded lazily. That is, if you specify <code>template_name</code>/<code>template_file</code>,   <code>js_file</code>, <code>css_file</code>, or <code>Media.js/css</code>, the file paths will be resolved only once you:</p> <ol> <li>Try to access component's HTML / CSS / JS, or</li> <li>Render the component.</li> </ol> <p>Read more on Accessing component's HTML / JS / CSS.</p> </li> <li> <p>Component inheritance:</p> <ul> <li>When you subclass a component, the JS and CSS defined on parent's <code>Media</code> class is now inherited by the child component.</li> <li>You can disable or customize Media inheritance by setting <code>extend</code> attribute on the <code>Component.Media</code> nested class. This work similarly to Django's <code>Media.extend</code>.</li> <li>When child component defines either <code>template</code> or <code>template_file</code>, both of parent's <code>template</code> and <code>template_file</code> are ignored. The same applies to <code>js_file</code> and <code>css_file</code>.</li> </ul> </li> <li> <p>Autodiscovery now ignores files and directories that start with an underscore (<code>_</code>), except <code>__init__.py</code></p> </li> <li> <p>The Signals emitted by or during the use of django-components are now documented, together the <code>template_rendered</code> signal.</p> </li> </ul>"},{"location":"release_notes/#v0123","title":"v0.123","text":""},{"location":"release_notes/#fix_2","title":"Fix","text":"<ul> <li>Fix edge cases around rendering components whose templates used the <code>{% extends %}</code> template tag (#859)</li> </ul>"},{"location":"release_notes/#v0122","title":"v0.122","text":""},{"location":"release_notes/#feat_5","title":"Feat","text":"<ul> <li>Add support for HTML fragments. HTML fragments can be rendered by passing <code>type=\"fragment\"</code> to <code>Component.render()</code> or <code>Component.render_to_response()</code>. Read more on how to use HTML fragments with HTMX, AlpineJS, or vanillaJS.</li> </ul>"},{"location":"release_notes/#v0121","title":"v0.121","text":""},{"location":"release_notes/#fix_3","title":"Fix","text":"<ul> <li>Fix the use of Django template filters (<code>|lower:\"etc\"</code>) with component inputs #855.</li> </ul>"},{"location":"release_notes/#v0120","title":"v0.120","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.121 to fix bugs introduced in v0.119.</p>"},{"location":"release_notes/#fix_4","title":"Fix","text":"<ul> <li>Fix the use of translation strings <code>_(\"bla\")</code> as inputs to components #849.</li> </ul>"},{"location":"release_notes/#v0119","title":"v0.119","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - This release introduced bugs #849, #855. Please update to v0.121.</p>"},{"location":"release_notes/#fix_5","title":"Fix","text":"<ul> <li>Fix compatibility with custom subclasses of Django's <code>Template</code> that need to access   <code>origin</code> or other initialization arguments. (https://github.com/django-components/django-components/pull/828)</li> </ul>"},{"location":"release_notes/#refactor_5","title":"Refactor","text":"<ul> <li>Compatibility with <code>django-debug-toolbar-template-profiler</code>:</li> <li> <p>Monkeypatching of Django's <code>Template</code> now happens at <code>AppConfig.ready()</code> (https://github.com/django-components/django-components/pull/825)</p> </li> <li> <p>Internal parsing of template tags tag was updated. No API change. (https://github.com/django-components/django-components/pull/827)</p> </li> </ul>"},{"location":"release_notes/#v0118","title":"v0.118","text":""},{"location":"release_notes/#feat_6","title":"Feat","text":"<ul> <li>Add support for <code>context_processors</code> and <code>RenderContext</code> inside component templates</li> </ul> <p><code>Component.render()</code> and <code>Component.render_to_response()</code> now accept an extra kwarg <code>request</code>.</p> <pre><code>```py\ndef my_view(request)\n    return MyTable.render_to_response(\n        request=request\n    )\n```\n</code></pre> <ul> <li> <p>When you pass in <code>request</code>, the component will use <code>RenderContext</code> instead of <code>Context</code>.     Thus the context processors will be applied to the context.</p> </li> <li> <p>NOTE: When you pass in both <code>request</code> and <code>context</code> to <code>Component.render()</code>, and <code>context</code> is already an instance of <code>Context</code>, the <code>request</code> kwarg will be ignored.</p> </li> </ul>"},{"location":"release_notes/#v0117","title":"v0.117","text":""},{"location":"release_notes/#fix_6","title":"Fix","text":"<ul> <li>The HTML parser no longer erronously inserts <code>&lt;html&gt;&lt;head&gt;&lt;body&gt;</code> on some occasions, and   no longer tries to close unclosed HTML tags.</li> </ul>"},{"location":"release_notes/#refactor_6","title":"Refactor","text":"<ul> <li>Replaced Selectolax with BeautifulSoup4 as project dependencies.</li> </ul>"},{"location":"release_notes/#v0116","title":"v0.116","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_7","title":"Fix","text":"<ul> <li>Fix the order of execution of JS scripts:</li> <li>Scripts in <code>Component.Media.js</code> are executed in the order they are defined</li> <li> <p>Scripts in <code>Component.js</code> are executed AFTER <code>Media.js</code> scripts</p> </li> <li> <p>Fix compatibility with AlpineJS</p> </li> <li>Scripts in <code>Component.Media.js</code> are now again inserted as <code>&lt;script&gt;</code> tags</li> <li>By default, <code>Component.Media.js</code> are inserted as synchronous <code>&lt;script&gt;</code> tags,     so the AlpineJS components registered in the <code>Media.js</code> scripts will now again     run BEFORE the core AlpineJS script.</li> </ul> <p>AlpineJS can be configured like so:</p> <p>Option 1 - AlpineJS loaded in <code>&lt;head&gt;</code> with <code>defer</code> attribute:   <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    {% component_css_dependencies %}\n    &lt;script defer src=\"https://unpkg.com/alpinejs\"&gt;&lt;/script&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component 'my_alpine_component' / %}\n    {% component_js_dependencies %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre></p> <p>Option 2 - AlpineJS loaded in <code>&lt;body&gt;</code> AFTER <code>{% component_js_depenencies %}</code>:   <pre><code>&lt;html&gt;\n    &lt;head&gt;\n        {% component_css_dependencies %}\n    &lt;/head&gt;\n    &lt;body&gt;\n        {% component 'my_alpine_component' / %}\n        {% component_js_dependencies %}\n\n        &lt;script src=\"https://unpkg.com/alpinejs\"&gt;&lt;/script&gt;\n    &lt;/body&gt;\n&lt;/html&gt;\n</code></pre></p>"},{"location":"release_notes/#v0115","title":"v0.115","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_8","title":"Fix","text":"<ul> <li>Fix integration with ManifestStaticFilesStorage on Windows by resolving component filepaths   (like <code>Component.template_name</code>) to POSIX paths.</li> </ul>"},{"location":"release_notes/#v0114","title":"v0.114","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_9","title":"Fix","text":"<ul> <li>Prevent rendering Slot tags during fill discovery stage to fix a case when a component inside a slot   fill tried to access provided data too early.</li> </ul>"},{"location":"release_notes/#v0113","title":"v0.113","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_10","title":"Fix","text":"<ul> <li>Ensure consistent order of scripts in <code>Component.Media.js</code></li> </ul>"},{"location":"release_notes/#v0112","title":"v0.112","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_11","title":"Fix","text":"<ul> <li>Allow components to accept default fill even if no default slot was encountered during rendering</li> </ul>"},{"location":"release_notes/#v0111","title":"v0.111","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_12","title":"Fix","text":"<ul> <li>Prevent rendering Component tags during fill discovery stage to fix a case when a component inside the default slot   tried to access provided data too early.</li> </ul>"},{"location":"release_notes/#v0110","title":"\ud83d\udea8\ud83d\udce2 v0.110","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#general","title":"General","text":""},{"location":"release_notes/#breaking-changes","title":"\ud83d\udea8\ud83d\udce2 BREAKING CHANGES","text":"<ul> <li> <p>Installation changes:</p> <ul> <li>If your components include JS or CSS, you now must use the middleware and add django-components' URLs to your <code>urlpatterns</code> (See \"Adding support for JS and CSS\")</li> </ul> </li> <li> <p>Component typing signature changed from</p> <pre><code>Component[Args, Kwargs, Data, Slots]\n</code></pre> <p>to</p> <pre><code>Component[Args, Kwargs, Slots, Data, JsData, CssData]\n</code></pre> </li> <li> <p>If you rendered a component A with <code>Component.render()</code> and then inserted that into another component B, now you must pass <code>render_dependencies=False</code> to component A:</p> <pre><code>prerendered_a = CompA.render(\n    args=[...],\n    kwargs={...},\n    render_dependencies=False,\n)\n\nhtml = CompB.render(\n    kwargs={\n        content=prerendered_a,\n    },\n)\n</code></pre> </li> </ul>"},{"location":"release_notes/#feat_7","title":"Feat","text":"<ul> <li>Intellisense and mypy validation for settings:</li> </ul> <p>Instead of defining the <code>COMPONENTS</code> settings as a plain dict, you can use <code>ComponentsSettings</code>:</p> <pre><code># settings.py\nfrom django_components import ComponentsSettings\n\nCOMPONENTS = ComponentsSettings(\n    autodiscover=True,\n    ...\n)\n</code></pre> <ul> <li>Use <code>get_component_dirs()</code> and <code>get_component_files()</code> to get the same list of dirs / files that would be imported by <code>autodiscover()</code>, but without actually importing them.</li> </ul>"},{"location":"release_notes/#refactor_7","title":"Refactor","text":"<ul> <li> <p>For advanced use cases, use can omit the middleware and instead manage component JS and CSS dependencies yourself with <code>render_dependencies</code></p> </li> <li> <p>The <code>ComponentRegistry</code> settings <code>RegistrySettings</code>   were lowercased to align with the global settings:</p> </li> <li><code>RegistrySettings.CONTEXT_BEHAVIOR</code> -&gt; <code>RegistrySettings.context_behavior</code></li> <li><code>RegistrySettings.TAG_FORMATTER</code> -&gt; <code>RegistrySettings.tag_formatter</code></li> </ul> <p>The old uppercase settings <code>CONTEXT_BEHAVIOR</code> and <code>TAG_FORMATTER</code> are deprecated and will be removed in v1.</p> <ul> <li> <p>The setting <code>reload_on_template_change</code> was renamed to   <code>reload_on_file_change</code>.   And now it properly triggers server reload when any file in the component dirs change. The old name <code>reload_on_template_change</code>   is deprecated and will be removed in v1.</p> </li> <li> <p>The setting <code>forbidden_static_files</code> was renamed to   <code>static_files_forbidden</code>   to align with <code>static_files_allowed</code>   The old name <code>forbidden_static_files</code> is deprecated and will be removed in v1.</p> </li> </ul>"},{"location":"release_notes/#tags","title":"Tags","text":""},{"location":"release_notes/#breaking-changes_1","title":"\ud83d\udea8\ud83d\udce2 BREAKING CHANGES","text":"<ul> <li> <p><code>{% component_dependencies %}</code> tag was removed. Instead, use <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code></p> <ul> <li> <p>The combined tag was removed to encourage the best practice of putting JS scripts at the end of <code>&lt;body&gt;</code>, and CSS styles inside <code>&lt;head&gt;</code>.</p> <p>On the other hand, co-locating JS script and CSS styles can lead to a flash of unstyled content, as either JS scripts will block the rendering, or CSS will load too late.</p> </li> </ul> </li> <li> <p>The undocumented keyword arg <code>preload</code> of <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code> tags was removed.   This will be replaced with HTML fragment support.</p> </li> </ul>"},{"location":"release_notes/#fix_13","title":"Fix","text":"<ul> <li>Allow using forward slash (<code>/</code>) when defining custom TagFormatter,   e.g. <code>{% MyComp %}..{% /MyComp %}</code>.</li> </ul>"},{"location":"release_notes/#refactor_8","title":"Refactor","text":"<ul> <li><code>{% component_dependencies %}</code> tags are now OPTIONAL - If your components use JS and CSS, but you don't use <code>{% component_dependencies %}</code> tags, the JS and CSS will now be, by default, inserted at the end of <code>&lt;body&gt;</code> and at the end of <code>&lt;head&gt;</code> respectively.</li> </ul>"},{"location":"release_notes/#slots","title":"Slots","text":""},{"location":"release_notes/#feat_8","title":"Feat","text":"<ul> <li>Fills can now be defined within loops (<code>{% for %}</code>) or other tags (like <code>{% with %}</code>),   or even other templates using <code>{% include %}</code>.</li> </ul> <p>Following is now possible</p> <pre><code>{% component \"table\" %}\n  {% for slot_name in slots %}\n    {% fill name=slot_name %}\n    {% endfill %}\n  {% endfor %}\n{% endcomponent %}\n</code></pre> <ul> <li>If you need to access the data or the default content of a default fill, you can   set the <code>name</code> kwarg to <code>\"default\"</code>.</li> </ul> <p>Previously, a default fill would be defined simply by omitting the <code>{% fill %}</code> tags:</p> <pre><code>{% component \"child\" %}\n  Hello world\n{% endcomponent %}\n</code></pre> <p>But in that case you could not access the slot data or the default content, like it's possible   for named fills:</p> <pre><code>{% component \"child\" %}\n  {% fill name=\"header\" data=\"data\" %}\n    Hello {{ data.user.name }}\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <p>Now, you can specify default tag by using <code>name=\"default\"</code>:</p> <pre><code>{% component \"child\" %}\n  {% fill name=\"default\" data=\"data\" %}\n    Hello {{ data.user.name }}\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <ul> <li>When inside <code>get_context_data()</code> or other component methods, the default fill   can now be accessed as <code>Component.input.slots[\"default\"]</code>, e.g.:</li> </ul> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        default_slot = self.input.slots[\"default\"]\n        ...\n</code></pre> <ul> <li>You can now dynamically pass all slots to a child component. This is similar to   passing all slots in Vue:</li> </ul> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"slots\": self.input.slots,\n        }\n\n    template: \"\"\"\n      &lt;div&gt;\n        {% component \"child\" %}\n          {% for slot_name in slots %}\n            {% fill name=slot_name data=\"data\" %}\n              {% slot name=slot_name ...data / %}\n            {% endfill %}\n          {% endfor %}\n        {% endcomponent %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre>"},{"location":"release_notes/#fix_14","title":"Fix","text":"<ul> <li> <p>Slots defined with <code>{% fill %}</code> tags are now properly accessible via <code>self.input.slots</code> in <code>get_context_data()</code></p> </li> <li> <p>Do not raise error if multiple slots with same name are flagged as default</p> </li> <li> <p>Slots can now be defined within loops (<code>{% for %}</code>) or other tags (like <code>{% with %}</code>),   or even other templates using <code>{% include %}</code>.</p> </li> </ul> <p>Previously, following would cause the kwarg <code>name</code> to be an empty string:</p> <pre><code>{% for slot_name in slots %}\n  {% slot name=slot_name %}\n{% endfor %}\n</code></pre>"},{"location":"release_notes/#refactor_9","title":"Refactor","text":"<ul> <li>When you define multiple slots with the same name inside a template,   you now have to set the <code>default</code> and <code>required</code> flags individually.</li> </ul> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"image\" default required %}Image here{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"image\" default required %}Image here{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>This means you can also have multiple slots with the same name but   different conditions.</p> <p>E.g. in this example, we have a component that renders a user avatar   - a small circular image with a profile picture of name initials.</p> <p>If the component is given <code>image_src</code> or <code>name_initials</code> variables,   the <code>image</code> slot is optional. But if neither of those are provided,   you MUST fill the <code>image</code> slot.</p> <pre><code>&lt;div class=\"avatar\"&gt;\n    {% if image_src %}\n        {% slot \"image\" default %}\n            &lt;img src=\"{{ image_src }}\" /&gt;\n        {% endslot %}\n    {% elif name_initials %}\n        {% slot \"image\" default required %}\n            &lt;div style=\"\n                border-radius: 25px;\n                width: 50px;\n                height: 50px;\n                background: blue;\n            \"&gt;\n                {{ name_initials }}\n            &lt;/div&gt;\n        {% endslot %}\n    {% else %}\n        {% slot \"image\" default required / %}\n    {% endif %}\n&lt;/div&gt;\n</code></pre> <ul> <li>The slot fills that were passed to a component and which can be accessed as <code>Component.input.slots</code>   can now be passed through the Django template, e.g. as inputs to other tags.</li> </ul> <p>Internally, django-components handles slot fills as functions.</p> <p>Previously, if you tried to pass a slot fill within a template, Django would try to call it as a function.</p> <p>Now, something like this is possible:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"child_slot\": self.input.slots[\"child_slot\"],\n        }\n\n    template: \"\"\"\n      &lt;div&gt;\n        {% component \"child\" content=child_slot / %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre> <p>NOTE: Using <code>{% slot %}</code> and <code>{% fill %}</code> tags is still the preferred method, but the approach above   may be necessary in some complex or edge cases.</p> <ul> <li>The <code>is_filled</code> variable (and the <code>{{ component_vars.is_filled }}</code> context variable) now returns   <code>False</code> when you try to access a slot name which has not been defined:</li> </ul> <p>Before:</p> <pre><code>{{ component_vars.is_filled.header }} -&gt; True\n{{ component_vars.is_filled.footer }} -&gt; False\n{{ component_vars.is_filled.nonexist }} -&gt; \"\" (empty string)\n</code></pre> <p>After:   <pre><code>{{ component_vars.is_filled.header }} -&gt; True\n{{ component_vars.is_filled.footer }} -&gt; False\n{{ component_vars.is_filled.nonexist }} -&gt; False\n</code></pre></p> <ul> <li> <p>Components no longer raise an error if there are extra slot fills</p> </li> <li> <p>Components will raise error when a slot is doubly-filled. </p> </li> </ul> <p>E.g. if we have a component with a default slot:</p> <pre><code>{% slot name=\"content\" default / %}\n</code></pre> <p>Now there is two ways how we can target this slot: Either using <code>name=\"default\"</code>   or <code>name=\"content\"</code>.</p> <p>In case you specify BOTH, the component will raise an error:</p> <pre><code>{% component \"child\" %}\n  {% fill slot=\"default\" %}\n    Hello from default slot\n  {% endfill %}\n  {% fill slot=\"content\" data=\"data\" %}\n    Hello from content slot\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"release_notes/#v0100","title":"\ud83d\udea8\ud83d\udce2 v0.100","text":""},{"location":"release_notes/#breaking-changes_2","title":"BREAKING CHANGES","text":"<ul> <li> <p><code>django_components.safer_staticfiles</code> app was removed. It is no longer needed.</p> </li> <li> <p>Installation changes:</p> <ul> <li>Instead of defining component directories in <code>STATICFILES_DIRS</code>, set them to <code>COMPONENTS.dirs</code>.</li> <li> <p>You now must define <code>STATICFILES_FINDERS</code></p> </li> <li> <p>See here how to migrate your settings.py</p> </li> </ul> </li> </ul>"},{"location":"release_notes/#feat_9","title":"Feat","text":"<ul> <li>Beside the top-level <code>/components</code> directory, you can now define also app-level components dirs, e.g. <code>[app]/components</code>   (See <code>COMPONENTS.app_dirs</code>).</li> </ul>"},{"location":"release_notes/#refactor_10","title":"Refactor","text":"<ul> <li>When you call <code>as_view()</code> on a component instance, that instance will be passed to <code>View.as_view()</code></li> </ul>"},{"location":"release_notes/#v097","title":"v0.97","text":""},{"location":"release_notes/#fix_15","title":"Fix","text":"<ul> <li>Fixed template caching. You can now also manually create cached templates with <code>cached_template()</code></li> </ul>"},{"location":"release_notes/#refactor_11","title":"Refactor","text":"<ul> <li> <p>The previously undocumented <code>get_template</code> was made private.</p> </li> <li> <p>In it's place, there's a new <code>get_template</code>, which supersedes <code>get_template_string</code> (will be removed in v1). The new <code>get_template</code> is the same as <code>get_template_string</code>, except   it allows to return either a string or a Template instance.</p> </li> <li> <p>You now must use only one of <code>template</code>, <code>get_template</code>, <code>template_name</code>, or <code>get_template_name</code>.</p> </li> </ul>"},{"location":"release_notes/#v096","title":"v0.96","text":""},{"location":"release_notes/#feat_10","title":"Feat","text":"<ul> <li> <p>Run-time type validation for Python 3.11+ - If the <code>Component</code> class is typed, e.g. <code>Component[Args, Kwargs, ...]</code>, the args, kwargs, slots, and data are validated against the given types. (See Runtime input validation with types)</p> </li> <li> <p>Render hooks - Set <code>on_render_before</code> and <code>on_render_after</code> methods on <code>Component</code> to intercept or modify the template or context before rendering, or the rendered result afterwards. (See Component hooks)</p> </li> <li> <p><code>component_vars.is_filled</code> context variable can be accessed from within <code>on_render_before</code> and <code>on_render_after</code> hooks as <code>self.is_filled.my_slot</code></p> </li> </ul>"},{"location":"release_notes/#095","title":"0.95","text":""},{"location":"release_notes/#feat_11","title":"Feat","text":"<ul> <li>Added support for dynamic components, where the component name is passed as a variable. (See Dynamic components)</li> </ul>"},{"location":"release_notes/#refactor_12","title":"Refactor","text":"<ul> <li>Changed <code>Component.input</code> to raise <code>RuntimeError</code> if accessed outside of render context. Previously it returned <code>None</code> if unset.</li> </ul>"},{"location":"release_notes/#v094","title":"v0.94","text":""},{"location":"release_notes/#feat_12","title":"Feat","text":"<ul> <li> <p>django_components now automatically configures Django to support multi-line tags. (See Multi-line tags)</p> </li> <li> <p>New setting <code>reload_on_template_change</code>. Set this to <code>True</code> to reload the dev server on changes to component template files. (See Reload dev server on component file changes)</p> </li> </ul>"},{"location":"release_notes/#v093","title":"v0.93","text":""},{"location":"release_notes/#feat_13","title":"Feat","text":"<ul> <li> <p>Spread operator <code>...dict</code> inside template tags. (See Spread operator)</p> </li> <li> <p>Use template tags inside string literals in component inputs. (See Use template tags inside component inputs)</p> </li> <li> <p>Dynamic slots, fills and provides - The <code>name</code> argument for these can now be a variable, a template expression, or via spread operator</p> </li> <li> <p>Component library authors can now configure <code>CONTEXT_BEHAVIOR</code> and <code>TAG_FORMATTER</code> settings independently from user settings.</p> </li> </ul>"},{"location":"release_notes/#v092","title":"\ud83d\udea8\ud83d\udce2 v0.92","text":""},{"location":"release_notes/#breaking-changes_3","title":"BREAKING CHANGES","text":"<ul> <li><code>Component</code> class is no longer a subclass of <code>View</code>. To configure the <code>View</code> class, set the <code>Component.View</code> nested class. HTTP methods like <code>get</code> or <code>post</code> can still be defined directly on <code>Component</code> class, and <code>Component.as_view()</code> internally calls <code>Component.View.as_view()</code>. (See Modifying the View class)</li> </ul>"},{"location":"release_notes/#feat_14","title":"Feat","text":"<ul> <li> <p>The inputs (args, kwargs, slots, context, ...) that you pass to <code>Component.render()</code> can be accessed from within <code>get_context_data</code>, <code>get_template</code> and <code>get_template_name</code> via <code>self.input</code>. (See Accessing data passed to the component)</p> </li> <li> <p>Typing: <code>Component</code> class supports generics that specify types for <code>Component.render</code> (See Adding type hints with Generics)</p> </li> </ul>"},{"location":"release_notes/#v090","title":"v0.90","text":""},{"location":"release_notes/#feat_15","title":"Feat","text":"<ul> <li> <p>All tags (<code>component</code>, <code>slot</code>, <code>fill</code>, ...) now support \"self-closing\" or \"inline\" form, where you can omit the closing tag:</p> <pre><code>{# Before #}\n{% component \"button\" %}{% endcomponent %}\n{# After #}\n{% component \"button\" / %}\n</code></pre> </li> <li> <p>All tags now support the \"dictionary key\" or \"aggregate\" syntax (<code>kwarg:key=val</code>):</p> <pre><code>{% component \"button\" attrs:class=\"hidden\" %}\n</code></pre> </li> <li> <p>You can change how the components are written in the template with TagFormatter.</p> <p>The default is <code>django_components.component_formatter</code>:</p> <pre><code>{% component \"button\" href=\"...\" disabled %}\n    Click me!\n{% endcomponent %}\n</code></pre> <p>While <code>django_components.shorthand_component_formatter</code> allows you to write components like so:</p> <pre><code>{% button href=\"...\" disabled %}\n    Click me!\n{% endbutton %}\n</code></pre> </li> </ul>"},{"location":"release_notes/#v085","title":"\ud83d\udea8\ud83d\udce2 v0.85","text":""},{"location":"release_notes/#breaking-changes_4","title":"BREAKING CHANGES","text":"<ul> <li> <p>Autodiscovery module resolution changed. Following undocumented behavior was removed:</p> <ul> <li> <p>Previously, autodiscovery also imported any <code>[app]/components.py</code> files, and used <code>SETTINGS_MODULE</code> to search for component dirs.</p> <p>To migrate from:</p> <ul> <li> <p><code>[app]/components.py</code> - Define each module in <code>COMPONENTS.libraries</code> setting,     or import each module inside the <code>AppConfig.ready()</code> hook in respective <code>apps.py</code> files.</p> </li> <li> <p><code>SETTINGS_MODULE</code> - Define component dirs using <code>STATICFILES_DIRS</code></p> </li> </ul> </li> <li> <p>Previously, autodiscovery handled relative files in <code>STATICFILES_DIRS</code>. To align with Django, <code>STATICFILES_DIRS</code> now must be full paths (Django docs).</p> </li> </ul> </li> </ul>"},{"location":"release_notes/#v081","title":"\ud83d\udea8\ud83d\udce2 v0.81","text":""},{"location":"release_notes/#breaking-changes_5","title":"BREAKING CHANGES","text":"<ul> <li>The order of arguments to <code>render_to_response</code> has changed, to align with the (now public) <code>render</code> method of <code>Component</code> class.</li> </ul>"},{"location":"release_notes/#feat_16","title":"Feat","text":"<ul> <li> <p><code>Component.render()</code> is public and documented</p> </li> <li> <p>Slots passed <code>render_to_response</code> and <code>render</code> can now be rendered also as functions.</p> </li> </ul>"},{"location":"release_notes/#v080","title":"v0.80","text":""},{"location":"release_notes/#feat_17","title":"Feat","text":"<ul> <li>Vue-like provide/inject with the <code>{% provide %}</code> tag and <code>inject()</code> method.</li> </ul>"},{"location":"release_notes/#v079","title":"\ud83d\udea8\ud83d\udce2 v0.79","text":""},{"location":"release_notes/#breaking-changes_6","title":"BREAKING CHANGES","text":"<ul> <li>Default value for the <code>COMPONENTS.context_behavior</code> setting was changes from <code>\"isolated\"</code> to <code>\"django\"</code>. If you did not set this value explicitly before, this may be a breaking change. See the rationale for change here.</li> </ul>"},{"location":"release_notes/#v077","title":"\ud83d\udea8\ud83d\udce2 v0.77","text":""},{"location":"release_notes/#breaking","title":"BREAKING","text":"<ul> <li> <p>The syntax for accessing default slot content has changed from</p> <pre><code>{% fill \"my_slot\" as \"alias\" %}\n    {{ alias.default }}\n{% endfill %}\n</code></pre> <p>to</p> <pre><code>{% fill \"my_slot\" default=\"alias\" %}\n    {{ alias }}\n{% endfill %}\n</code></pre> </li> </ul>"},{"location":"release_notes/#v074","title":"v0.74","text":""},{"location":"release_notes/#feat_18","title":"Feat","text":"<ul> <li> <p><code>{% html_attrs %}</code> tag for formatting data as HTML attributes</p> </li> <li> <p><code>prefix:key=val</code> construct for passing dicts to components</p> </li> </ul>"},{"location":"release_notes/#v070","title":"\ud83d\udea8\ud83d\udce2 v0.70","text":""},{"location":"release_notes/#breaking-changes_7","title":"BREAKING CHANGES","text":"<ul> <li> <p><code>{% if_filled \"my_slot\" %}</code> tags were replaced with <code>{{ component_vars.is_filled.my_slot }}</code> variables.</p> </li> <li> <p>Simplified settings - <code>slot_context_behavior</code> and <code>context_behavior</code> were merged. See the documentation for more details.</p> </li> </ul>"},{"location":"release_notes/#v067","title":"v0.67","text":""},{"location":"release_notes/#refactor_13","title":"Refactor","text":"<ul> <li>Changed the default way how context variables are resolved in slots. See the documentation for more details.</li> </ul>"},{"location":"release_notes/#v050","title":"\ud83d\udea8\ud83d\udce2 v0.50","text":""},{"location":"release_notes/#breaking-changes_8","title":"BREAKING CHANGES","text":"<ul> <li> <p><code>{% component_block %}</code> is now <code>{% component %}</code>, and <code>{% component %}</code> blocks need an ending <code>{% endcomponent %}</code> tag.</p> <p>The new <code>python manage.py upgradecomponent</code> command can be used to upgrade a directory (use <code>--path</code> argument to point to each dir) of templates that use components to the new syntax automatically.</p> <p>This change is done to simplify the API in anticipation of a 1.0 release of django_components. After 1.0 we intend to be stricter with big changes like this in point releases.</p> </li> </ul>"},{"location":"release_notes/#v034","title":"v0.34","text":""},{"location":"release_notes/#feat_19","title":"Feat","text":"<ul> <li>Components as views, which allows you to handle requests and render responses from within a component. See the documentation for more details.</li> </ul>"},{"location":"release_notes/#v028","title":"v0.28","text":""},{"location":"release_notes/#feat_20","title":"Feat","text":"<ul> <li>'implicit' slot filling and the <code>default</code> option for <code>slot</code> tags.</li> </ul>"},{"location":"release_notes/#v027","title":"v0.27","text":""},{"location":"release_notes/#feat_21","title":"Feat","text":"<ul> <li>A second installable app <code>django_components.safer_staticfiles</code>. It provides the same behavior as <code>django.contrib.staticfiles</code> but with extra security guarantees (more info below in Security Notes).</li> </ul>"},{"location":"release_notes/#v026","title":"\ud83d\udea8\ud83d\udce2 v0.26","text":""},{"location":"release_notes/#breaking-changes_9","title":"BREAKING CHANGES","text":"<ul> <li> <p>Changed the syntax for <code>{% slot %}</code> tags. From now on, we separate defining a slot (<code>{% slot %}</code>) from filling a slot with content (<code>{% fill %}</code>). This means you will likely need to change a lot of slot tags to fill.</p> <p>We understand this is annoying, but it's the only way we can get support for nested slots that fill in other slots, which is a very nice feature to have access to. Hoping that this will feel worth it!</p> </li> </ul>"},{"location":"release_notes/#v022","title":"v0.22","text":""},{"location":"release_notes/#feat_22","title":"Feat","text":"<ul> <li> <p>All files inside components subdirectores are autoimported to simplify setup.</p> <p>An existing project might start to get <code>AlreadyRegistered</code> errors because of this. To solve this, either remove your custom loading of components, or set <code>\"autodiscover\": False</code> in <code>settings.COMPONENTS</code>.</p> </li> </ul>"},{"location":"release_notes/#v017","title":"v0.17","text":""},{"location":"release_notes/#breaking-changes_10","title":"BREAKING CHANGES","text":"<ul> <li> <p>Renamed <code>Component.context</code> and <code>Component.template</code> to <code>get_context_data</code> and <code>get_template_name</code>. The old methods still work, but emit a deprecation warning.</p> <p>This change was done to sync naming with Django's class based views, and make using django-components more familiar to Django users. <code>Component.context</code> and <code>Component.template</code> will be removed when version 1.0 is released.</p> </li> </ul>"},{"location":"concepts/advanced/authoring_component_libraries/","title":"Authoring component libraries","text":"<p>You can publish and share your components for others to use. Below you will find the steps to do so.</p> <p>For live examples, see the Community examples.</p>"},{"location":"concepts/advanced/authoring_component_libraries/#writing-component-libraries","title":"Writing component libraries","text":"<ol> <li> <p>Create a Django project with a similar structure:</p> <pre><code>project/\n  |--  myapp/\n    |--  __init__.py\n    |--  apps.py\n    |--  templates/\n      |--  table/\n        |--  table.py\n        |--  table.js\n        |--  table.css\n        |--  table.html\n    |--  menu.py   &lt;--- single-file component\n  |--  templatetags/\n    |--  __init__.py\n    |--  mytags.py\n</code></pre> </li> <li> <p>Create custom <code>Library</code>     and <code>ComponentRegistry</code> instances in <code>mytags.py</code></p> <p>This will be the entrypoint for using the components inside Django templates.</p> <p>Remember that Django requires the <code>Library</code> instance to be accessible under the <code>register</code> variable (See Django docs):</p> <pre><code>from django.template import Library\nfrom django_components import ComponentRegistry, RegistrySettings\n\nregister = library = django.template.Library()\ncomp_registry = ComponentRegistry(\n    library=library,\n    settings=RegistrySettings(\n        context_behavior=\"isolated\",\n        tag_formatter=\"django_components.component_formatter\",\n    ),\n)\n</code></pre> <p>As you can see above, this is also the place where we configure how our components should behave, using the <code>settings</code> argument. If omitted, default settings are used.</p> <p>For library authors, we recommend setting <code>context_behavior</code> to <code>\"isolated\"</code>, so that the state cannot leak into the components, and so the components' behavior is configured solely through the inputs. This means that the components will be more predictable and easier to debug.</p> <p>Next, you can decide how will others use your components by setting the <code>tag_formatter</code> options.</p> <p>If omitted or set to <code>\"django_components.component_formatter\"</code>, your components will be used like this:</p> <pre><code>{% component \"table\" items=items headers=headers %}\n{% endcomponent %}\n</code></pre> <p>Or you can use <code>\"django_components.component_shorthand_formatter\"</code> to use components like so:</p> <pre><code>{% table items=items headers=headers %}\n{% endtable %}\n</code></pre> <p>Or you can define a custom TagFormatter.</p> <p>Either way, these settings will be scoped only to your components. So, in the user code, there may be components side-by-side that use different formatters:</p> <pre><code>{% load mytags %}\n\n{# Component from your library \"mytags\", using the \"shorthand\" formatter #}\n{% table items=items headers=header %}\n{% endtable %}\n\n{# User-created components using the default settings #}\n{% component \"my_comp\" title=\"Abc...\" %}\n{% endcomponent %}\n</code></pre> </li> <li> <p>Write your components and register them with your instance of <code>ComponentRegistry</code></p> <p>There's one difference when you are writing components that are to be shared, and that's that the components must be explicitly registered with your instance of <code>ComponentRegistry</code> from the previous step.</p> <p>For better user experience, you can also define the types for the args, kwargs, slots and data.</p> <p>It's also a good idea to have a common prefix for your components, so they can be easily distinguished from users' components. In the example below, we use the prefix <code>my_</code> / <code>My</code>.</p> <pre><code>from typing import Dict, NotRequired, Optional, Tuple, TypedDict\n\nfrom django_components import Component, SlotFunc, register, types\n\nfrom myapp.templatetags.mytags import comp_registry\n\n# Define the types\nclass EmptyDict(TypedDict):\n    pass\n\ntype MyMenuArgs = Tuple[int, str]\n\nclass MyMenuSlots(TypedDict):\n    default: NotRequired[Optional[SlotFunc[EmptyDict]]]\n\nclass MyMenuProps(TypedDict):\n    vertical: NotRequired[bool]\n    klass: NotRequired[str]\n    style: NotRequired[str]\n\n# Define the component\n# NOTE: Don't forget to set the `registry`!\n@register(\"my_menu\", registry=comp_registry)\nclass MyMenu(Component[MyMenuArgs, MyMenuProps, MyMenuSlots, Any, Any, Any]):\n    def get_context_data(\n        self,\n        *args,\n        attrs: Optional[Dict] = None,\n    ):\n        return {\n            \"attrs\": attrs,\n        }\n\n    template: types.django_html = \"\"\"\n        {# Load django_components template tags #}\n        {% load component_tags %}\n\n        &lt;div {% html_attrs attrs class=\"my-menu\" %}&gt;\n            &lt;div class=\"my-menu__content\"&gt;\n                {% slot \"default\" default / %}\n            &lt;/div&gt;\n        &lt;/div&gt;\n    \"\"\"\n</code></pre> </li> <li> <p>Import the components in <code>apps.py</code></p> <p>Normally, users rely on autodiscovery and <code>COMPONENTS.dirs</code> to load the component files.</p> <p>Since you, as the library author, are not in control of the file system, it is recommended to load the components manually.</p> <p>We recommend doing this in the <code>AppConfig.ready()</code> hook of your <code>apps.py</code>:</p> <pre><code>from django.apps import AppConfig\n\nclass MyAppConfig(AppConfig):\n    default_auto_field = \"django.db.models.BigAutoField\"\n    name = \"myapp\"\n\n    # This is the code that gets run when user adds myapp\n    # to Django's INSTALLED_APPS\n    def ready(self) -&gt; None:\n        # Import the components that you want to make available\n        # inside the templates.\n        from myapp.templates import (\n            menu,\n            table,\n        )\n</code></pre> <p>Note that you can also include any other startup logic within <code>AppConfig.ready()</code>.</p> </li> </ol> <p>And that's it! The next step is to publish it.</p>"},{"location":"concepts/advanced/authoring_component_libraries/#publishing-component-libraries","title":"Publishing component libraries","text":"<p>Once you are ready to share your library, you need to build a distribution and then publish it to PyPI.</p> <p>django_components uses the <code>build</code> utility to build a distribution:</p> <pre><code>python -m build --sdist --wheel --outdir dist/ .\n</code></pre> <p>And to publish to PyPI, you can use <code>twine</code> (See Python user guide)</p> <pre><code>twine upload --repository pypi dist/* -u __token__ -p &lt;PyPI_TOKEN&gt;\n</code></pre> <p>Notes on publishing:</p> <ul> <li>If you use components where the HTML / CSS / JS files are separate, you may need to define   <code>MANIFEST.in</code>   to include those files with the distribution   (see user guide).</li> </ul>"},{"location":"concepts/advanced/authoring_component_libraries/#installing-and-using-component-libraries","title":"Installing and using component libraries","text":"<p>After the package has been published, all that remains is to install it in other django projects:</p> <ol> <li> <p>Install the package:</p> <pre><code>pip install myapp django_components\n</code></pre> </li> <li> <p>Add the package to <code>INSTALLED_APPS</code></p> <pre><code>INSTALLED_APPS = [\n    ...\n    \"django_components\",\n    \"myapp\",\n]\n</code></pre> </li> <li> <p>Optionally add the template tags to the <code>builtins</code>,    so you don't have to call <code>{% load mytags %}</code> in every template:</p> <pre><code>TEMPLATES = [\n    {\n        ...,\n        'OPTIONS': {\n            'builtins': [\n                'myapp.templatetags.mytags',\n            ]\n        },\n    },\n]\n</code></pre> </li> <li> <p>And, at last, you can use the components in your own project!</p> <pre><code>{% my_menu title=\"Abc...\" %}\n    Hello World!\n{% endmy_menu %}\n</code></pre> </li> </ol>"},{"location":"concepts/advanced/component_registry/","title":"Registering components","text":"<p>In previous examples you could repeatedly see us using <code>@register()</code> to \"register\" the components. In this section we dive deeper into what it actually means and how you can manage (add or remove) components.</p> <p>As a reminder, we may have a component like this:</p> <pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"template.html\"\n\n    # This component takes one parameter, a date string to show in the template\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n</code></pre> <p>which we then render in the template as:</p> <pre><code>{% component \"calendar\" date=\"1970-01-01\" %}\n{% endcomponent %}\n</code></pre> <p>As you can see, <code>@register</code> links up the component class with the <code>{% component %}</code> template tag. So when the template tag comes across a component called <code>\"calendar\"</code>, it can look up it's class and instantiate it.</p>"},{"location":"concepts/advanced/component_registry/#what-is-componentregistry","title":"What is ComponentRegistry","text":"<p>The <code>@register</code> decorator is a shortcut for working with the <code>ComponentRegistry</code>.</p> <p><code>ComponentRegistry</code> manages which components can be used in the template tags.</p> <p>Each <code>ComponentRegistry</code> instance is associated with an instance of Django's <code>Library</code>. And Libraries are inserted into Django template using the <code>{% load %}</code> tags.</p> <p>The <code>@register</code> decorator accepts an optional kwarg <code>registry</code>, which specifies, the <code>ComponentRegistry</code> to register components into. If omitted, the default <code>ComponentRegistry</code> instance defined in django_components is used.</p> <pre><code>my_registry = ComponentRegistry()\n\n@register(registry=my_registry)\nclass MyComponent(Component):\n    ...\n</code></pre> <p>The default <code>ComponentRegistry</code> is associated with the <code>Library</code> that you load when you call <code>{% load component_tags %}</code> inside your template, or when you add <code>django_components.templatetags.component_tags</code> to the template builtins.</p> <p>So when you register or unregister a component to/from a component registry, then behind the scenes the registry automatically adds/removes the component's template tags to/from the Library, so you can call the component from within the templates such as <code>{% component \"my_comp\" %}</code>.</p>"},{"location":"concepts/advanced/component_registry/#working-with-componentregistry","title":"Working with ComponentRegistry","text":"<p>The default <code>ComponentRegistry</code> instance can be imported as:</p> <pre><code>from django_components import registry\n</code></pre> <p>You can use the registry to manually add/remove/get components:</p> <pre><code>from django_components import registry\n\n# Register components\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\n\n# Get all or single\nregistry.all()  # {\"button\": ButtonComponent, \"card\": CardComponent}\nregistry.get(\"card\")  # CardComponent\n\n# Check if component is registered\nregistry.has(\"button\")  # True\n\n# Unregister single component\nregistry.unregister(\"card\")\n\n# Unregister all components\nregistry.clear()\n</code></pre>"},{"location":"concepts/advanced/component_registry/#registering-components-to-custom-componentregistry","title":"Registering components to custom ComponentRegistry","text":"<p>If you are writing a component library to be shared with others, you may want to manage your own instance of <code>ComponentRegistry</code> and register components onto a different <code>Library</code> instance than the default one.</p> <p>The <code>Library</code> instance can be set at instantiation of <code>ComponentRegistry</code>. If omitted, then the default Library instance from django_components is used.</p> <pre><code>from django.template import Library\nfrom django_components import ComponentRegistry\n\nmy_library = Library(...)\nmy_registry = ComponentRegistry(library=my_library)\n</code></pre> <p>When you have defined your own <code>ComponentRegistry</code>, you can either register the components with <code>my_registry.register()</code>, or pass the registry to the <code>@component.register()</code> decorator via the <code>registry</code> kwarg:</p> <pre><code>from path.to.my.registry import my_registry\n\n@register(\"my_component\", registry=my_registry)\nclass MyComponent(Component):\n    ...\n</code></pre> <p>NOTE: The Library instance can be accessed under <code>library</code> attribute of <code>ComponentRegistry</code>.</p>"},{"location":"concepts/advanced/component_registry/#componentregistry-settings","title":"ComponentRegistry settings","text":"<p>When you are creating an instance of <code>ComponentRegistry</code>, you can define the components' behavior within the template.</p> <p>The registry accepts these settings:</p> <ul> <li><code>context_behavior</code></li> <li><code>tag_formatter</code></li> </ul> <pre><code>from django.template import Library\nfrom django_components import ComponentRegistry, RegistrySettings\n\nregister = library = django.template.Library()\ncomp_registry = ComponentRegistry(\n    library=library,\n    settings=RegistrySettings(\n        context_behavior=\"isolated\",\n        tag_formatter=\"django_components.component_formatter\",\n    ),\n)\n</code></pre> <p>These settings are the same as the ones you can set for django_components.</p> <p>In fact, when you set <code>COMPONENT.tag_formatter</code> or <code>COMPONENT.context_behavior</code>, these are forwarded to the default <code>ComponentRegistry</code>.</p> <p>This makes it possible to have multiple registries with different settings in one projects, and makes sharing of component libraries possible.</p>"},{"location":"concepts/advanced/extensions/","title":"Extensions","text":"<p>New in version 0.131</p> <p>Django-components functionality can be extended with \"extensions\". Extensions allow for powerful customization and integrations. They can:</p> <ul> <li>Tap into lifecycle events, such as when a component is created, deleted, registered, or unregistered.</li> <li>Add new attributes and methods to the components under an extension-specific nested class.</li> <li>Define custom commands that can be executed via the Django management command interface.</li> </ul>"},{"location":"concepts/advanced/extensions/#setting-up-extensions","title":"Setting up extensions","text":"<p>Extensions are configured in the Django settings under <code>COMPONENTS.extensions</code>.</p> <p>Extensions can be set by either as an import string or by passing in a class:</p> <pre><code># settings.py\n\nclass MyExtension(ComponentExtension):\n    name = \"my_extension\"\n\n    class ExtensionClass(ComponentExtension.ExtensionClass):\n        ...\n\nCOMPONENTS = ComponentsSettings(\n    extensions=[\n        MyExtension,\n        \"another_app.extensions.AnotherExtension\",\n        \"my_app.extensions.ThirdExtension\",\n    ],\n)\n</code></pre>"},{"location":"concepts/advanced/extensions/#lifecycle-hooks","title":"Lifecycle hooks","text":"<p>Extensions can define methods to hook into lifecycle events, such as:</p> <ul> <li>Component creation or deletion</li> <li>Un/registering a component</li> <li>Creating or deleting a registry</li> <li>Pre-processing data passed to a component on render</li> <li>Post-processing data returned from <code>get_context_data()</code>   and others.</li> </ul> <p>See the full list in Extension Hooks Reference.</p>"},{"location":"concepts/advanced/extensions/#configuring-extensions-per-component","title":"Configuring extensions per component","text":"<p>Each extension has a corresponding nested class within the <code>Component</code> class. These allow to configure the extensions on a per-component basis.</p> <p>Note</p> <p>Accessing the component instance from inside the nested classes:</p> <p>Each method of the nested classes has access to the <code>component</code> attribute, which points to the component instance.</p> <pre><code>class MyTable(Component):\n    class View:\n        def get(self, request):\n            # `self.component` points to the instance of `MyTable` Component.\n            return self.component.get(request)\n</code></pre>"},{"location":"concepts/advanced/extensions/#example-component-as-view","title":"Example: Component as View","text":"<p>The Components as Views feature is actually implemented as an extension that is configured by a <code>View</code> nested class.</p> <p>You can override the <code>get</code>, <code>post</code>, etc methods to customize the behavior of the component as a view:</p> <pre><code>class MyTable(Component):\n    class View:\n        def get(self, request):\n            return self.component.get(request)\n\n        def post(self, request):\n            return self.component.post(request)\n\n        ...\n</code></pre>"},{"location":"concepts/advanced/extensions/#example-storybook-integration","title":"Example: Storybook integration","text":"<p>The Storybook integration (work in progress) is an extension that is configured by a <code>Storybook</code> nested class.</p> <p>You can override methods such as <code>title</code>, <code>parameters</code>, etc, to customize how to generate a Storybook JSON file from the component.</p> <pre><code>class MyTable(Component):\n    class Storybook:\n        def title(self):\n            return self.component.__class__.__name__\n\n        def parameters(self) -&gt; Parameters:\n            return {\n                \"server\": {\n                    \"id\": self.component.__class__.__name__,\n                }\n            }\n\n        def stories(self) -&gt; List[StoryAnnotations]:\n            return []\n\n        ...\n</code></pre>"},{"location":"concepts/advanced/extensions/#accessing-extensions-in-components","title":"Accessing extensions in components","text":"<p>Above, we've configured extensions <code>View</code> and <code>Storybook</code> for the <code>MyTable</code> component.</p> <p>You can access the instances of these extension classes in the component instance.</p> <p>For example, the View extension is available as <code>self.view</code>:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, request):\n        # `self.view` points to the instance of `View` extension.\n        return {\n            \"view\": self.view,\n        }\n</code></pre> <p>And the Storybook extension is available as <code>self.storybook</code>:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, request):\n        # `self.storybook` points to the instance of `Storybook` extension.\n        return {\n            \"title\": self.storybook.title(),\n        }\n</code></pre> <p>Thus, you can use extensions to add methods or attributes that will be available to all components in their component context.</p>"},{"location":"concepts/advanced/extensions/#writing-extensions","title":"Writing extensions","text":"<p>Creating extensions in django-components involves defining a class that inherits from <code>ComponentExtension</code>. This class can implement various lifecycle hooks and define new attributes or methods to be added to components.</p>"},{"location":"concepts/advanced/extensions/#defining-an-extension","title":"Defining an extension","text":"<p>To create an extension, define a class that inherits from <code>ComponentExtension</code> and implement the desired hooks.</p> <ul> <li>Each extension MUST have a <code>name</code> attribute. The name MUST be a valid Python identifier.</li> <li>The extension MAY implement any of the hook methods.</li> <li>Each hook method receives a context object with relevant data.</li> </ul> <pre><code>from django_components.extension import ComponentExtension, OnComponentClassCreatedContext\n\nclass MyExtension(ComponentExtension):\n    name = \"my_extension\"\n\n    def on_component_class_created(self, ctx: OnComponentClassCreatedContext) -&gt; None:\n        # Custom logic for when a component class is created\n        ctx.component_cls.my_attr = \"my_value\"\n</code></pre>"},{"location":"concepts/advanced/extensions/#defining-the-extension-class","title":"Defining the extension class","text":"<p>In previous sections we've seen the <code>View</code> and <code>Storybook</code> extensions classes that were nested within the <code>Component</code> class:</p> <pre><code>class MyComponent(Component):\n    class View:\n        ...\n\n    class Storybook:\n        ...\n</code></pre> <p>These can be understood as component-specific overrides or configuration.</p> <p>The nested extension classes like <code>View</code> or <code>Storybook</code> will actually subclass from a base extension class as defined on the <code>ComponentExtension.ExtensionClass</code>.</p> <p>This is how extensions define the \"default\" behavior of their nested extension classes.</p> <p>For example, the <code>View</code> base extension class defines the handlers for GET, POST, etc:</p> <pre><code>from django_components.extension import ComponentExtension\n\nclass ViewExtension(ComponentExtension):\n    name = \"view\"\n\n    # The default behavior of the `View` extension class.\n    class ExtensionClass(ComponentExtension.ExtensionClass):\n        def get(self, request):\n            return self.component.get(request)\n\n        def post(self, request):\n            return self.component.post(request)\n\n        ...\n</code></pre> <p>In any component that then defines a nested <code>View</code> extension class, the <code>View</code> extension class will actually subclass from the <code>ViewExtension.ExtensionClass</code> class.</p> <p>In other words, when you define a component like this:</p> <pre><code>class MyTable(Component):\n    class View:\n        def get(self, request):\n            # Do something\n            ...\n</code></pre> <p>It will actually be implemented as if the <code>View</code> class subclassed from base class <code>ViewExtension.ExtensionClass</code>:</p> <pre><code>class MyTable(Component):\n    class View(ViewExtension.ExtensionClass):\n        def get(self, request):\n            # Do something\n            ...\n</code></pre> <p>Warning</p> <p>When writing an extension, the <code>ExtensionClass</code> MUST subclass the base class <code>ComponentExtension.ExtensionClass</code>.</p> <p>This base class ensures that the extension class will have access to the component instance.</p>"},{"location":"concepts/advanced/extensions/#registering-extensions","title":"Registering extensions","text":"<p>Once the extension is defined, it needs to be registered in the Django settings to be used by the application.</p> <p>Extensions can be given either as an extension class, or its import string:</p> <pre><code># settings.py\nCOMPONENTS = {\n    \"extensions\": [\n        \"my_app.extensions.MyExtension\",\n    ],\n}\n</code></pre> <p>Or by reference:</p> <pre><code># settings.py\nfrom my_app.extensions import MyExtension\n\nCOMPONENTS = {\n    \"extensions\": [\n        MyExtension,\n    ],\n}\n</code></pre>"},{"location":"concepts/advanced/extensions/#full-example-custom-logging-extension","title":"Full example: Custom logging extension","text":"<p>To tie it all together, here's an example of a custom logging extension that logs when components are created, deleted, or rendered:</p> <ul> <li>Each component can specify which color to use for the logging by setting <code>Component.ColorLogger.color</code>.</li> <li>The extension will log the component name and color when the component is created, deleted, or rendered.</li> </ul> <pre><code>from django_components.extension import (\n    ComponentExtension,\n    OnComponentClassCreatedContext,\n    OnComponentClassDeletedContext,\n    OnComponentInputContext,\n)\n\nclass ColorLoggerExtensionClass(ComponentExtension.ExtensionClass):\n    color: str\n\n\nclass ColorLoggerExtension(ComponentExtension):\n    name = \"color_logger\"\n\n    # All `Component.ColorLogger` classes will inherit from this class.\n    ExtensionClass = ColorLoggerExtensionClass\n\n    # These hooks don't have access to the Component instance, only to the Component class,\n    # so we access the color as `Component.ColorLogger.color`.\n    def on_component_class_created(self, ctx: OnComponentClassCreatedContext) -&gt; None:\n        log.info(\n            f\"Component {ctx.component_cls} created.\",\n            color=ctx.component_cls.ColorLogger.color,\n        )\n\n    def on_component_class_deleted(self, ctx: OnComponentClassDeletedContext) -&gt; None:\n        log.info(\n            f\"Component {ctx.component_cls} deleted.\",\n            color=ctx.component_cls.ColorLogger.color,\n        )\n\n    # This hook has access to the Component instance, so we access the color\n    # as `self.component.color_logger.color`.\n    def on_component_input(self, ctx: OnComponentInputContext) -&gt; None:\n        log.info(\n            f\"Rendering component {ctx.component_cls}.\",\n            color=ctx.component.color_logger.color,\n        )\n</code></pre> <p>To use the <code>ColorLoggerExtension</code>, add it to your settings:</p> <pre><code># settings.py\nCOMPONENTS = {\n    \"extensions\": [\n        ColorLoggerExtension,\n    ],\n}\n</code></pre> <p>Once registered, in any component, you can define a <code>ColorLogger</code> attribute:</p> <pre><code>class MyComponent(Component):\n    class ColorLogger:\n        color = \"red\"\n</code></pre> <p>This will log the component name and color when the component is created, deleted, or rendered.</p>"},{"location":"concepts/advanced/extensions/#utility-functions","title":"Utility functions","text":"<p>django-components provides a few utility functions to help with writing extensions:</p> <ul> <li><code>all_components()</code> - returns a list of all created component classes.</li> <li><code>all_registries()</code> - returns a list of all created registry instances.</li> </ul>"},{"location":"concepts/advanced/extensions/#accessing-the-component-class-from-within-an-extension","title":"Accessing the component class from within an extension","text":"<p>When you are writing the extension class that will be nested inside a Component class, e.g.</p> <pre><code>class MyTable(Component):\n    class MyExtension:\n        def some_method(self):\n            ...\n</code></pre> <p>You can access the owner Component class (<code>MyTable</code>) from within methods of the extension class (<code>MyExtension</code>) by using the <code>component_class</code> attribute:</p> <pre><code>class MyTable(Component):\n    class MyExtension:\n        def some_method(self):\n            print(self.component_class)\n</code></pre> <p>Here is how the <code>component_class</code> attribute may be used with our <code>ColorLogger</code> extension shown above:</p> <pre><code>class ColorLoggerExtensionClass(ComponentExtension.ExtensionClass):\n    color: str\n\n    def log(self, msg: str) -&gt; None:\n        print(f\"{self.component_class.name}: {msg}\")\n\n\nclass ColorLoggerExtension(ComponentExtension):\n    name = \"color_logger\"\n\n    # All `Component.ColorLogger` classes will inherit from this class.\n    ExtensionClass = ColorLoggerExtensionClass\n</code></pre>"},{"location":"concepts/advanced/extensions/#extension-commands","title":"Extension Commands","text":"<p>Extensions in django-components can define custom commands that can be executed via the Django management command interface. This allows for powerful automation and customization capabilities.</p> <p>For example, if you have an extension that defines a command that prints \"Hello world\", you can run the command with:</p> <pre><code>python manage.py components ext run my_ext hello\n</code></pre> <p>Where:</p> <ul> <li><code>python manage.py components</code> - is the Django entrypoint</li> <li><code>ext run</code> - is the subcommand to run extension commands</li> <li><code>my_ext</code> - is the extension name</li> <li><code>hello</code> - is the command name</li> </ul>"},{"location":"concepts/advanced/extensions/#defining-commands","title":"Defining Commands","text":"<p>To define a command, subclass from <code>ComponentCommand</code>. This subclass should define:</p> <ul> <li><code>name</code> - the command's name</li> <li><code>help</code> - the command's help text</li> <li><code>handle</code> - the logic to execute when the command is run</li> </ul> <pre><code>from django_components import ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n\n    def handle(self, *args, **kwargs):\n        print(\"Hello, world!\")\n\nclass MyExt(ComponentExtension):\n    name = \"my_ext\"\n    commands = [HelloCommand]\n</code></pre>"},{"location":"concepts/advanced/extensions/#defining-command-arguments-and-options","title":"Defining Command Arguments and Options","text":"<p>Commands can accept positional arguments and options (e.g. <code>--foo</code>), which are defined using the <code>arguments</code> attribute of the <code>ComponentCommand</code> class.</p> <p>The arguments are parsed with <code>argparse</code> into a dictionary of arguments and options. These are then available as keyword arguments to the <code>handle</code> method of the command.</p> <pre><code>from django_components import CommandArg, ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n\n    arguments = [\n        # Positional argument\n        CommandArg(\n            name_or_flags=\"name\",\n            help=\"The name to say hello to\",\n        ),\n        # Optional argument\n        CommandArg(\n            name_or_flags=[\"--shout\", \"-s\"],\n            action=\"store_true\",\n            help=\"Shout the hello\",\n        ),\n    ]\n\n    def handle(self, name: str, *args, **kwargs):\n        shout = kwargs.get(\"shout\", False)\n        msg = f\"Hello, {name}!\"\n        if shout:\n            msg = msg.upper()\n        print(msg)\n</code></pre> <p>You can run the command with arguments and options:</p> <pre><code>python manage.py components ext run my_ext hello John --shout\n&gt;&gt;&gt; HELLO, JOHN!\n</code></pre> <p>Note</p> <p>Command definitions are parsed with <code>argparse</code>, so you can use all the features of <code>argparse</code> to define your arguments and options.</p> <p>See the argparse documentation for more information.</p> <p>django-components defines types as <code>CommandArg</code>, <code>CommandArgGroup</code>, <code>CommandSubcommand</code>, and <code>CommandParserInput</code> to help with type checking.</p> <p>Note</p> <p>If a command doesn't have the <code>handle</code> method defined, the command will print a help message and exit.</p>"},{"location":"concepts/advanced/extensions/#grouping-arguments","title":"Grouping Arguments","text":"<p>Arguments can be grouped using <code>CommandArgGroup</code> to provide better organization and help messages.</p> <p>Read more on argparse argument groups.</p> <pre><code>from django_components import CommandArg, CommandArgGroup, ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n\n    # Argument parsing is managed by `argparse`.\n    arguments = [\n        # Positional argument\n        CommandArg(\n            name_or_flags=\"name\",\n            help=\"The name to say hello to\",\n        ),\n        # Optional argument\n        CommandArg(\n            name_or_flags=[\"--shout\", \"-s\"],\n            action=\"store_true\",\n            help=\"Shout the hello\",\n        ),\n        # When printing the command help message, `--bar` and `--baz`\n        # will be grouped under \"group bar\".\n        CommandArgGroup(\n            title=\"group bar\",\n            description=\"Group description.\",\n            arguments=[\n                CommandArg(\n                    name_or_flags=\"--bar\",\n                    help=\"Bar description.\",\n                ),\n                CommandArg(\n                    name_or_flags=\"--baz\",\n                    help=\"Baz description.\",\n                ),\n            ],\n        ),\n    ]\n\n    def handle(self, name: str, *args, **kwargs):\n        shout = kwargs.get(\"shout\", False)\n        msg = f\"Hello, {name}!\"\n        if shout:\n            msg = msg.upper()\n        print(msg)\n</code></pre>"},{"location":"concepts/advanced/extensions/#subcommands","title":"Subcommands","text":"<p>Extensions can define subcommands, allowing for more complex command structures.</p> <p>Subcommands are defined similarly to root commands, as subclasses of <code>ComponentCommand</code> class.</p> <p>However, instead of defining the subcommands in the <code>commands</code> attribute of the extension, you define them in the <code>subcommands</code> attribute of the parent command:</p> <pre><code>from django_components import CommandArg, CommandArgGroup, ComponentCommand, ComponentExtension\n\nclass ChildCommand(ComponentCommand):\n    name = \"child\"\n    help = \"Child command\"\n\n    def handle(self, *args, **kwargs):\n        print(\"Child command\")\n\nclass ParentCommand(ComponentCommand):\n    name = \"parent\"\n    help = \"Parent command\"\n    subcommands = [\n        ChildCommand,\n    ]\n\n    def handle(self, *args, **kwargs):\n        print(\"Parent command\")\n</code></pre> <p>In this example, we can run two commands.</p> <p>Either the parent command:</p> <pre><code>python manage.py components ext run parent\n&gt;&gt;&gt; Parent command\n</code></pre> <p>Or the child command:</p> <pre><code>python manage.py components ext run parent child\n&gt;&gt;&gt; Child command\n</code></pre> <p>Warning</p> <p>Subcommands are independent of the parent command. When a subcommand runs, the parent command is NOT executed.</p> <p>As such, if you want to pass arguments to both the parent and child commands, e.g.:</p> <pre><code>python manage.py components ext run parent --foo child --bar\n</code></pre> <p>You should instead pass all the arguments to the subcommand:</p> <pre><code>python manage.py components ext run parent child --foo --bar\n</code></pre>"},{"location":"concepts/advanced/extensions/#print-command-help","title":"Print command help","text":"<p>By default, all commands will print their help message when run with the <code>--help</code> / <code>-h</code> flag.</p> <pre><code>python manage.py components ext run my_ext --help\n</code></pre> <p>The help message prints out all the arguments and options available for the command, as well as any subcommands.</p>"},{"location":"concepts/advanced/extensions/#testing-commands","title":"Testing Commands","text":"<p>Commands can be tested using Django's <code>call_command()</code> function, which allows you to simulate running the command in tests.</p> <pre><code>from django.core.management import call_command\n\ncall_command('components', 'ext', 'run', 'my_ext', 'hello', '--name', 'John')\n</code></pre> <p>To capture the output of the command, you can use the <code>StringIO</code> module to redirect the output to a string:</p> <pre><code>from io import StringIO\n\nout = StringIO()\nwith patch(\"sys.stdout\", new=out):\n    call_command('components', 'ext', 'run', 'my_ext', 'hello', '--name', 'John')\noutput = out.getvalue()\n</code></pre> <p>And to temporarily set the extensions, you can use the <code>@djc_test</code> decorator.</p> <p>Thus, a full test example can then look like this:</p> <pre><code>from io import StringIO\nfrom unittest.mock import patch\n\nfrom django.core.management import call_command\nfrom django_components.testing import djc_test\n\n@djc_test(\n    components_settings={\n        \"extensions\": [\n            \"my_app.extensions.MyExtension\",\n        ],\n    },\n)\ndef test_hello_command(self):\n    out = StringIO()\n    with patch(\"sys.stdout\", new=out):\n        call_command('components', 'ext', 'run', 'my_ext', 'hello', '--name', 'John')\n    output = out.getvalue()\n    assert output == \"Hello, John!\\n\"\n</code></pre>"},{"location":"concepts/advanced/extensions/#extension-urls","title":"Extension URLs","text":"<p>Extensions can define custom views and endpoints that can be accessed through the Django application.</p> <p>To define URLs for an extension, set them in the <code>urls</code> attribute of your <code>ComponentExtension</code> class. Each URL is defined using the <code>URLRoute</code> class, which specifies the path, handler, and optional name for the route.</p> <p>Here's an example of how to define URLs within an extension:</p> <pre><code>from django_components.extension import ComponentExtension, URLRoute\nfrom django.http import HttpResponse\n\ndef my_view(request):\n    return HttpResponse(\"Hello from my extension!\")\n\nclass MyExtension(ComponentExtension):\n    name = \"my_extension\"\n\n    urls = [\n        URLRoute(path=\"my-view/\", handler=my_view, name=\"my_view\"),\n        URLRoute(path=\"another-view/&lt;int:id&gt;/\", handler=my_view, name=\"another_view\"),\n    ]\n</code></pre> <p>Warning</p> <p>The <code>URLRoute</code> objects are different from objects created with Django's <code>django.urls.path()</code>. Do NOT use <code>URLRoute</code> objects in Django's <code>urlpatterns</code> and vice versa!</p> <p>django-components uses a custom <code>URLRoute</code> class to define framework-agnostic routing rules.</p> <p>As of v0.131, <code>URLRoute</code> objects are directly converted to Django's <code>URLPattern</code> and <code>URLResolver</code> objects.</p>"},{"location":"concepts/advanced/extensions/#accessing-extension-urls","title":"Accessing Extension URLs","text":"<p>The URLs defined in an extension are available under the path</p> <pre><code>/components/ext/&lt;extension_name&gt;/\n</code></pre> <p>For example, if you have defined a URL with the path <code>my-view/&lt;str:name&gt;/</code> in an extension named <code>my_extension</code>, it can be accessed at:</p> <pre><code>/components/ext/my_extension/my-view/john/\n</code></pre>"},{"location":"concepts/advanced/extensions/#nested-urls","title":"Nested URLs","text":"<p>Extensions can also define nested URLs to allow for more complex routing structures.</p> <p>To define nested URLs, set the <code>children</code> attribute of the <code>URLRoute</code> object to a list of child <code>URLRoute</code> objects:</p> <pre><code>class MyExtension(ComponentExtension):\n    name = \"my_extension\"\n\n    urls = [\n        URLRoute(\n            path=\"parent/\",\n            name=\"parent_view\",\n            children=[\n                URLRoute(path=\"child/&lt;str:name&gt;/\", handler=my_view, name=\"child_view\"),\n            ],\n        ),\n    ]\n</code></pre> <p>In this example, the URL</p> <pre><code>/components/ext/my_extension/parent/child/john/\n</code></pre> <p>would call the <code>my_view</code> handler with the parameter <code>name</code> set to <code>\"John\"</code>.</p>"},{"location":"concepts/advanced/extensions/#passing-kwargs-and-other-extra-fields-to-url-routes","title":"Passing kwargs and other extra fields to URL routes","text":"<p>The <code>URLRoute</code> class is framework-agnostic, so that extensions could be used with non-Django frameworks in the future.</p> <p>However, that means that there may be some extra fields that Django's <code>django.urls.path()</code> accepts, but which are not defined on the <code>URLRoute</code> object.</p> <p>To address this, the <code>URLRoute</code> object has an <code>extra</code> attribute, which is a dictionary that can be used to pass any extra kwargs to <code>django.urls.path()</code>:</p> <pre><code>URLRoute(\n    path=\"my-view/&lt;str:name&gt;/\",\n    handler=my_view,\n    name=\"my_view\",\n    extra={\"kwargs\": {\"foo\": \"bar\"} },\n)\n</code></pre> <p>Is the same as:</p> <pre><code>django.urls.path(\n    \"my-view/&lt;str:name&gt;/\",\n    view=my_view,\n    name=\"my_view\",\n    kwargs={\"foo\": \"bar\"},\n)\n</code></pre> <p>because <code>URLRoute</code> is converted to Django's route like so:</p> <pre><code>django.urls.path(\n    route.path,\n    view=route.handler,\n    name=route.name,\n    **route.extra,\n)\n</code></pre>"},{"location":"concepts/advanced/hooks/","title":"Lifecycle hooks","text":"<p>New in version 0.96</p> <p>Component hooks are functions that allow you to intercept the rendering process at specific positions.</p>"},{"location":"concepts/advanced/hooks/#available-hooks","title":"Available hooks","text":"<ul> <li><code>on_render_before</code></li> </ul> <pre><code>def on_render_before(\n    self: Component,\n    context: Context,\n    template: Template\n) -&gt; None:\n</code></pre> <p>Hook that runs just before the component's template is rendered.</p> <p>You can use this hook to access or modify the context or the template:</p> <pre><code>def on_render_before(self, context, template) -&gt; None:\n    # Insert value into the Context\n    context[\"from_on_before\"] = \":)\"\n\n    # Append text into the Template\n    template.nodelist.append(TextNode(\"FROM_ON_BEFORE\"))\n</code></pre> <ul> <li><code>on_render_after</code></li> </ul> <pre><code>def on_render_after(\n    self: Component,\n    context: Context,\n    template: Template,\n    content: str\n) -&gt; None | str | SafeString:\n</code></pre> <p>Hook that runs just after the component's template was rendered.   It receives the rendered output as the last argument.</p> <p>You can use this hook to access the context or the template, but modifying   them won't have any effect.</p> <p>To override the content that gets rendered, you can return a string or SafeString from this hook:</p> <pre><code>def on_render_after(self, context, template, content):\n    # Prepend text to the rendered content\n    return \"Chocolate cookie recipe: \" + content\n</code></pre>"},{"location":"concepts/advanced/hooks/#component-hooks-example","title":"Component hooks example","text":"<p>You can use hooks together with provide / inject to create components that accept a list of items via a slot.</p> <p>In the example below, each <code>tab_item</code> component will be rendered on a separate tab page, but they are all defined in the default slot of the <code>tabs</code> component.</p> <p>See here for how it was done</p> <pre><code>{% component \"tabs\" %}\n  {% component \"tab_item\" header=\"Tab 1\" %}\n    &lt;p&gt;\n      hello from tab 1\n    &lt;/p&gt;\n    {% component \"button\" %}\n      Click me!\n    {% endcomponent %}\n  {% endcomponent %}\n\n  {% component \"tab_item\" header=\"Tab 2\" %}\n    Hello this is tab 2\n  {% endcomponent %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/advanced/html_fragments/","title":"HTML fragments","text":"<p>Django-components provides a seamless integration with HTML fragments (HTML over the wire), whether you're using HTMX, AlpineJS, or vanilla JavaScript.</p> <p>When you define a component that has extra JS or CSS, and you use django-components to render the fragment, django-components will:</p> <ul> <li>Automatically load the associated JS and CSS</li> <li>Ensure that JS is loaded and executed only once even if the fragment is inserted multiple times</li> </ul> <p>Info</p> <p>What are HTML fragments and \"HTML over the wire\"?</p> <p>It is one of the methods for updating the state in the browser UI upon user interaction.</p> <p>How it works is that:</p> <ol> <li>User makes an action - clicks a button or submits a form</li> <li>The action causes a request to be made from the client to the server.</li> <li>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).</li> <li>A library like HTMX, AlpineJS, or custom function inserts the new HTML into    the correct place.</li> </ol>"},{"location":"concepts/advanced/html_fragments/#document-and-fragment-types","title":"Document and fragment types","text":"<p>Components support two modes of rendering - As a \"document\" or as a \"fragment\".</p> <p>What's the difference?</p>"},{"location":"concepts/advanced/html_fragments/#document-mode","title":"Document mode","text":"<p>Document mode assumes that the rendered components will be embedded into the HTML of the initial page load. This means that:</p> <ul> <li>The JS and CSS is embedded into the HTML as <code>&lt;script&gt;</code> and <code>&lt;style&gt;</code> tags   (see JS and CSS output locations)</li> <li>Django-components injects a JS script for managing JS and CSS assets</li> </ul> <p>A component is rendered as a \"document\" when:</p> <ul> <li>It is embedded inside a template as <code>{% component %}</code></li> <li>It is rendered with <code>Component.render()</code> or <code>Component.render_to_response()</code>   with the <code>type</code> kwarg set to <code>\"document\"</code> (default)</li> </ul> <p>Example:</p> <pre><code>MyTable.render(\n    kwargs={...},\n)\n\n# or\n\nMyTable.render(\n    kwargs={...},\n    type=\"document\",\n)\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#fragment-mode","title":"Fragment mode","text":"<p>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:</p> <ul> <li>JS and CSS is not directly embedded to avoid duplicately executing the same JS scripts.   So template tags like <code>{% component_js_dependencies %}</code>   inside of fragments are ignored.</li> <li>Instead, django-components appends the fragment's content with a JSON <code>&lt;script&gt;</code> to trigger a call   to its asset manager JS script, which will load the JS and CSS smartly.</li> <li>The asset manager JS script is assumed to be already loaded on the page.</li> </ul> <p>A component is rendered as \"fragment\" when:</p> <ul> <li>It is rendered with <code>Component.render()</code>   or <code>Component.render_to_response()</code>   with the <code>type</code> kwarg set to <code>\"fragment\"</code></li> </ul> <p>Example:</p> <pre><code>MyTable.render(\n    kwargs={...},\n    type=\"fragment\",\n)\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#live-examples","title":"Live examples","text":"<p>For live interactive examples, start our demo project (<code>sampleproject</code>).</p> <p>Then navigate to these URLs:</p> <ul> <li><code>/fragment/base/alpine</code></li> <li><code>/fragment/base/htmx</code></li> <li><code>/fragment/base/js</code></li> </ul>"},{"location":"concepts/advanced/html_fragments/#example-htmx","title":"Example - HTMX","text":""},{"location":"concepts/advanced/html_fragments/#1-define-document-html","title":"1. Define document HTML","text":"[root]/components/demo.py<pre><code>from django_components import Component, types\n\n# HTML into which a fragment will be loaded using HTMX\nclass MyPage(Component):\n    def get(self, request):\n        return self.render_to_response()\n\n    template = \"\"\"\n        {% load component_tags %}\n        &lt;!DOCTYPE html&gt;\n        &lt;html&gt;\n            &lt;head&gt;\n                {% component_css_dependencies %}\n                &lt;script src=\"https://unpkg.com/htmx.org@1.9.12\"&gt;&lt;/script&gt;\n            &lt;/head&gt;\n            &lt;body&gt;\n                &lt;div id=\"target\"&gt;OLD&lt;/div&gt;\n\n                &lt;button\n                    hx-get=\"/mypage/frag\"\n                    hx-swap=\"outerHTML\"\n                    hx-target=\"#target\"\n                &gt;\n                  Click me!\n                &lt;/button&gt;\n\n                {% component_js_dependencies %}\n            &lt;/body&gt;\n        &lt;/html&gt;\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#2-define-fragment-html","title":"2. Define fragment HTML","text":"[root]/components/demo.py<pre><code>class Frag(Component):\n    def get(self, request):\n        return self.render_to_response(\n            # IMPORTANT: Don't forget `type=\"fragment\"`\n            type=\"fragment\",\n        )\n\n    template = \"\"\"\n        &lt;div class=\"frag\"&gt;\n            123\n            &lt;span id=\"frag-text\"&gt;&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    js = \"\"\"\n        document.querySelector('#frag-text').textContent = 'xxx';\n    \"\"\"\n\n    css = \"\"\"\n        .frag {\n            background: blue;\n        }\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#3-create-view-and-urls","title":"3. Create view and URLs","text":"[app]/urls.py<pre><code>from django.urls import path\n\nfrom components.demo import MyPage, Frag\n\nurlpatterns = [\n    path(\"mypage/\", MyPage.as_view())\n    path(\"mypage/frag\", Frag.as_view()),\n]\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#example-alpinejs","title":"Example - AlpineJS","text":""},{"location":"concepts/advanced/html_fragments/#1-define-document-html_1","title":"1. Define document HTML","text":"[root]/components/demo.py<pre><code>from django_components import Component, types\n\n# HTML into which a fragment will be loaded using AlpineJS\nclass MyPage(Component):\n    def get(self, request):\n        return self.render_to_response()\n\n    template = \"\"\"\n        {% load component_tags %}\n        &lt;!DOCTYPE html&gt;\n        &lt;html&gt;\n            &lt;head&gt;\n                {% component_css_dependencies %}\n                &lt;script defer src=\"https://unpkg.com/alpinejs\"&gt;&lt;/script&gt;\n            &lt;/head&gt;\n            &lt;body x-data=\"{\n                htmlVar: 'OLD',\n                loadFragment: function () {\n                    const url = '/mypage/frag';\n                    fetch(url)\n                        .then(response =&gt; response.text())\n                        .then(html =&gt; {\n                            this.htmlVar = html;\n                        });\n                }\n            }\"&gt;\n                &lt;div id=\"target\" x-html=\"htmlVar\"&gt;OLD&lt;/div&gt;\n\n                &lt;button @click=\"loadFragment\"&gt;\n                  Click me!\n                &lt;/button&gt;\n\n                {% component_js_dependencies %}\n            &lt;/body&gt;\n        &lt;/html&gt;\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#2-define-fragment-html_1","title":"2. Define fragment HTML","text":"[root]/components/demo.py<pre><code>class Frag(Component):\n    def get(self, request):\n        # IMPORTANT: Don't forget `type=\"fragment\"`\n        return self.render_to_response(\n            type=\"fragment\",\n        )\n\n    # NOTE: We wrap the actual fragment in a template tag with x-if=\"false\" to prevent it\n    #       from being rendered until we have registered the component with AlpineJS.\n    template = \"\"\"\n        &lt;template x-if=\"false\" data-name=\"frag\"&gt;\n            &lt;div class=\"frag\"&gt;\n                123\n                &lt;span x-data=\"frag\" x-text=\"fragVal\"&gt;\n                &lt;/span&gt;\n            &lt;/div&gt;\n        &lt;/template&gt;\n    \"\"\"\n\n    js = \"\"\"\n        Alpine.data('frag', () =&gt; ({\n            fragVal: 'xxx',\n        }));\n\n        // Now that the component has been defined in AlpineJS, we can \"activate\"\n        // all instances where we use the `x-data=\"frag\"` directive.\n        document.querySelectorAll('[data-name=\"frag\"]').forEach((el) =&gt; {\n            el.setAttribute('x-if', 'true');\n        });\n    \"\"\"\n\n    css = \"\"\"\n        .frag {\n            background: blue;\n        }\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#3-create-view-and-urls_1","title":"3. Create view and URLs","text":"[app]/urls.py<pre><code>from django.urls import path\n\nfrom components.demo import MyPage, Frag\n\nurlpatterns = [\n    path(\"mypage/\", MyPage.as_view())\n    path(\"mypage/frag\", Frag.as_view()),\n]\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#example-vanilla-js","title":"Example - Vanilla JS","text":""},{"location":"concepts/advanced/html_fragments/#1-define-document-html_2","title":"1. Define document HTML","text":"[root]/components/demo.py<pre><code>from django_components import Component, types\n\n# HTML into which a fragment will be loaded using JS\nclass MyPage(Component):\n    def get(self, request):\n        return self.render_to_response()\n\n    template = \"\"\"\n        {% load component_tags %}\n        &lt;!DOCTYPE html&gt;\n        &lt;html&gt;\n            &lt;head&gt;\n                {% component_css_dependencies %}\n            &lt;/head&gt;\n            &lt;body&gt;\n                &lt;div id=\"target\"&gt;OLD&lt;/div&gt;\n\n                &lt;button&gt;\n                  Click me!\n                &lt;/button&gt;\n                &lt;script&gt;\n                    const url = `/mypage/frag`;\n                    document.querySelector('#loader').addEventListener('click', function () {\n                        fetch(url)\n                            .then(response =&gt; response.text())\n                            .then(html =&gt; {\n                                document.querySelector('#target').outerHTML = html;\n                            });\n                    });\n                &lt;/script&gt;\n\n                {% component_js_dependencies %}\n            &lt;/body&gt;\n        &lt;/html&gt;\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#2-define-fragment-html_2","title":"2. Define fragment HTML","text":"[root]/components/demo.py<pre><code>class Frag(Component):\n    def get(self, request):\n        return self.render_to_response(\n            # IMPORTANT: Don't forget `type=\"fragment\"`\n            type=\"fragment\",\n        )\n\n    template = \"\"\"\n        &lt;div class=\"frag\"&gt;\n            123\n            &lt;span id=\"frag-text\"&gt;&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    js = \"\"\"\n        document.querySelector('#frag-text').textContent = 'xxx';\n    \"\"\"\n\n    css = \"\"\"\n        .frag {\n            background: blue;\n        }\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#3-create-view-and-urls_2","title":"3. Create view and URLs","text":"[app]/urls.py<pre><code>from django.urls import path\n\nfrom components.demo import MyPage, Frag\n\nurlpatterns = [\n    path(\"mypage/\", MyPage.as_view())\n    path(\"mypage/frag\", Frag.as_view()),\n]\n</code></pre>"},{"location":"concepts/advanced/provide_inject/","title":"Prop drilling and provide / inject","text":"<p>New in version 0.80:</p> <p>Django components supports the provide / inject or ContextProvider pattern with the combination of:</p> <ol> <li><code>{% provide %}</code> tag</li> <li><code>inject()</code> method of the <code>Component</code> class</li> </ol>"},{"location":"concepts/advanced/provide_inject/#what-is-prop-drilling","title":"What is \"prop drilling\"?","text":"<p>Prop drilling refers to a scenario in UI development where you need to pass data through many layers of a component tree to reach the nested components that actually need the data.</p> <p>Normally, you'd use props to send data from a parent component to its children. However, this straightforward method becomes cumbersome and inefficient if the data has to travel through many levels or if several components scattered at different depths all need the same piece of information.</p> <p>This results in a situation where the intermediate components, which don't need the data for their own functioning, end up having to manage and pass along these props. This clutters the component tree and makes the code verbose and harder to manage.</p> <p>A neat solution to avoid prop drilling is using the \"provide and inject\" technique.</p> <p>With provide / inject, a parent component acts like a data hub for all its descendants. This setup allows any component, no matter how deeply nested it is, to access the required data directly from this centralized provider without having to messily pass props down the chain. This approach significantly cleans up the code and makes it easier to maintain.</p> <p>This feature is inspired by Vue's Provide / Inject and React's Context / useContext.</p>"},{"location":"concepts/advanced/provide_inject/#how-to-use-provide-inject","title":"How to use provide / inject","text":"<p>As the name suggest, using provide / inject consists of 2 steps</p> <ol> <li>Providing data</li> <li>Injecting provided data</li> </ol> <p>For examples of advanced uses of provide / inject, see this discussion.</p>"},{"location":"concepts/advanced/provide_inject/#using-provide-tag","title":"Using <code>{% provide %}</code> tag","text":"<p>First we use the <code>{% provide %}</code> tag to define the data we want to \"provide\" (make available).</p> <pre><code>{% provide \"my_data\" key=\"hi\" another=123 %}\n    {% component \"child\" / %}  &lt;--- Can access \"my_data\"\n{% endprovide %}\n\n{% component \"child\" / %}  &lt;--- Cannot access \"my_data\"\n</code></pre> <p>Notice that the <code>provide</code> tag REQUIRES a name as a first argument. This is the key by which we can then access the data passed to this tag.</p> <p><code>provide</code> tag name must resolve to a valid identifier (AKA a valid Python variable name).</p> <p>Once you've set the name, you define the data you want to \"provide\" by passing it as keyword arguments. This is similar to how you pass data to the <code>{% with %}</code> tag.</p> <p>NOTE: Kwargs passed to <code>{% provide %}</code> are NOT added to the context. In the example below, the <code>{{ key }}</code> won't render anything:</p> <pre><code>{% provide \"my_data\" key=\"hi\" another=123 %}\n    {{ key }}\n{% endprovide %}\n</code></pre> <p>Similarly to slots and fills, also provide's name argument can be set dynamically via a variable, a template expression, or a spread operator:</p> <pre><code>{% provide name=name ... %}\n    ...\n{% provide %}\n&lt;/table&gt;\n</code></pre>"},{"location":"concepts/advanced/provide_inject/#using-inject-method","title":"Using <code>inject()</code> method","text":"<p>To \"inject\" (access) the data defined on the <code>provide</code> tag, you can use the <code>inject()</code> method inside of <code>get_context_data()</code>.</p> <p>For a component to be able to \"inject\" some data, the component (<code>{% component %}</code> tag) must be nested inside the <code>{% provide %}</code> tag.</p> <p>In the example from previous section, we've defined two kwargs: <code>key=\"hi\" another=123</code>. That means that if we now inject <code>\"my_data\"</code>, we get an object with 2 attributes - <code>key</code> and <code>another</code>.</p> <pre><code>class ChildComponent(Component):\n    def get_context_data(self):\n        my_data = self.inject(\"my_data\")\n        print(my_data.key)     # hi\n        print(my_data.another) # 123\n        return {}\n</code></pre> <p>First argument to <code>inject</code> is the key (or name) of the provided data. This must match the string that you used in the <code>provide</code> tag. If no provider with given key is found, <code>inject</code> raises a <code>KeyError</code>.</p> <p>To avoid the error, you can pass a second argument to <code>inject</code> to which will act as a default value, similar to <code>dict.get(key, default)</code>:</p> <pre><code>class ChildComponent(Component):\n    def get_context_data(self):\n        my_data = self.inject(\"invalid_key\", DEFAULT_DATA)\n        assert my_data == DEFAUKT_DATA\n        return {}\n</code></pre> <p>The instance returned from <code>inject()</code> is a subclass of <code>NamedTuple</code>, so the instance is immutable. This ensures that the data returned from <code>inject</code> will always have all the keys that were passed to the <code>provide</code> tag.</p> <p>NOTE: <code>inject()</code> works strictly only in <code>get_context_data</code>. If you try to call it from elsewhere, it will raise an error.</p>"},{"location":"concepts/advanced/provide_inject/#full-example","title":"Full example","text":"<pre><code>@register(\"child\")\nclass ChildComponent(Component):\n    template = \"\"\"\n        &lt;div&gt; {{ my_data.key }} &lt;/div&gt;\n        &lt;div&gt; {{ my_data.another }} &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self):\n        my_data = self.inject(\"my_data\", \"default\")\n        return {\"my_data\": my_data}\n\ntemplate_str = \"\"\"\n    {% load component_tags %}\n    {% provide \"my_data\" key=\"hi\" another=123 %}\n        {% component \"child\" / %}\n    {% endprovide %}\n\"\"\"\n</code></pre> <p>renders:</p> <pre><code>&lt;div&gt;hi&lt;/div&gt;\n&lt;div&gt;123&lt;/div&gt;\n</code></pre>"},{"location":"concepts/advanced/rendering_js_css/","title":"Rendering JS / CSS","text":""},{"location":"concepts/advanced/rendering_js_css/#js-and-css-output-locations","title":"JS and CSS output locations","text":"<p>If:</p> <ol> <li>Your components use JS and CSS via any of:<ul> <li><code>Component.css</code></li> <li><code>Component.js</code></li> <li><code>Component.Media.css</code></li> <li><code>Component.Media.js</code></li> </ul> </li> <li>And you use the <code>ComponentDependencyMiddleware</code> middleware</li> </ol> <p>Then, by default, the components' JS and CSS will be automatically inserted into the HTML:</p> <ul> <li>CSS styles will be inserted at the end of the <code>&lt;head&gt;</code></li> <li>JS scripts will be inserted at the end of the <code>&lt;body&gt;</code></li> </ul> <p>If you want to place the dependencies elsewhere in the HTML, you can override the locations by inserting following Django template tags:</p> <ul> <li><code>{% component_js_dependencies %}</code> - Set new location(s) for JS scripts</li> <li><code>{% component_css_dependencies %}</code> - Set new location(s) for CSS styles</li> </ul> <p>So if you have a component with JS and CSS:</p> <pre><code>from django_components import Component, types\n\nclass MyButton(Component):\n    template: types.django_html = \"\"\"\n        &lt;button class=\"my-button\"&gt;\n            Click me!\n        &lt;/button&gt;\n    \"\"\"\n    js: types.js = \"\"\"\n        for (const btnEl of document.querySelectorAll(\".my-button\")) {\n            btnEl.addEventListener(\"click\", () =&gt; {\n                console.log(\"BUTTON CLICKED!\");\n            });\n        }\n    \"\"\"\n    css: types.css \"\"\"\n        .my-button {\n            background: green;\n        }\n    \"\"\"\n\n    class Media:\n        js = [\"/extra/script.js\"]\n        css = [\"/extra/style.css\"]\n</code></pre> <p>Then the JS from <code>MyButton.js</code> and <code>MyButton.Media.js</code> will be rendered at the default place, or in <code>{% component_js_dependencies %}</code>.</p> <p>And the CSS from <code>MyButton.css</code> and <code>MyButton.Media.css</code> will be rendered at the default place, or in <code>{% component_css_dependencies %}</code>.</p> <p>And if you don't specify <code>{% component_dependencies %}</code> tags, it is the equivalent of:</p> <pre><code>&lt;!doctype html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    &lt;title&gt;MyPage&lt;/title&gt;\n    ...\n    {% component_css_dependencies %}\n  &lt;/head&gt;\n  &lt;body&gt;\n    &lt;main&gt;\n      ...\n    &lt;/main&gt;\n    {% component_js_dependencies %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre>"},{"location":"concepts/advanced/rendering_js_css/#setting-up-the-middleware","title":"Setting up the middleware","text":"<p><code>ComponentDependencyMiddleware</code> is a Django middleware designed to manage and inject CSS / JS dependencies of rendered components dynamically. It ensures that only the necessary stylesheets and scripts are loaded in your HTML responses, based on the components used in your Django templates.</p> <p>To set it up, add the middleware to your <code>MIDDLEWARE</code> in <code>settings.py</code>:</p> <pre><code>MIDDLEWARE = [\n    # ... other middleware classes ...\n    'django_components.middleware.ComponentDependencyMiddleware'\n    # ... other middleware classes ...\n]\n</code></pre>"},{"location":"concepts/advanced/rendering_js_css/#render_dependencies-and-rendering-js-css-without-the-middleware","title":"<code>render_dependencies</code> and rendering JS / CSS without the middleware","text":"<p>For most scenarios, using the <code>ComponentDependencyMiddleware</code> middleware will be just fine.</p> <p>However, this section is for you if you want to:</p> <ul> <li>Render HTML that will NOT be sent as a server response</li> <li>Insert pre-rendered HTML into another component</li> <li>Render HTML fragments (partials)</li> </ul> <p>Every time there is an HTML string that has parts which were rendered using components, and any of those components has JS / CSS, then this HTML string MUST be processed with <code>render_dependencies()</code>.</p> <p>It is actually <code>render_dependencies()</code> that finds all used components in the HTML string, and inserts the component's JS and CSS into <code>{% component_dependencies %}</code> tags, or at the default locations.</p>"},{"location":"concepts/advanced/rendering_js_css/#render-js-css-without-the-middleware","title":"Render JS / CSS without the middleware","text":"<p>The truth is that the <code>ComponentDependencyMiddleware</code> middleware just calls <code>render_dependencies()</code>, passing in the HTML content. So if you render a template that contained <code>{% component %}</code> tags, you MUST pass the result through <code>render_dependencies()</code>. And the middleware is just one of the options.</p> <p>Here is how you can achieve the same, without the middleware, using <code>render_dependencies()</code>:</p> <pre><code>from django.template.base import Template\nfrom django.template.context import Context\nfrom django_component import render_dependencies\n\ntemplate = Template(\"\"\"\n    {% load component_tags %}\n    &lt;!doctype html&gt;\n    &lt;html&gt;\n    &lt;head&gt;\n        &lt;title&gt;MyPage&lt;/title&gt;\n    &lt;/head&gt;\n    &lt;body&gt;\n        &lt;main&gt;\n            {% component \"my_button\" %}\n                Click me!\n            {% endcomponent %}\n        &lt;/main&gt;\n    &lt;/body&gt;\n    &lt;/html&gt;\n\"\"\")\n\nrendered = template.render(Context())\nrendered = render_dependencies(rendered)\n</code></pre> <p>Same applies if you render a template using Django's <code>django.shortcuts.render</code>:</p> <pre><code>from django.shortcuts import render\n\ndef my_view(request):\n    rendered = render(request, \"pages/home.html\")\n    rendered = render_dependencies(rendered)\n    return rendered\n</code></pre> <p>Alternatively, when you render HTML with <code>Component.render()</code> or <code>Component.render_to_response()</code>, these, by default, call <code>render_dependencies()</code> for you, so you don't have to:</p> <pre><code>from django_components import Component\n\nclass MyButton(Component):\n    ...\n\n# No need to call `render_dependencies()`\nrendered = MyButton.render()\n</code></pre>"},{"location":"concepts/advanced/rendering_js_css/#inserting-pre-rendered-html-into-another-component","title":"Inserting pre-rendered HTML into another component","text":"<p>In previous section we've shown that <code>render_dependencies()</code> does NOT need to be called when you render a component via <code>Component.render()</code>.</p> <p>API of django_components makes it possible to compose components in a \"React-like\" way, where we pre-render a piece of HTML and then insert it into a larger structure.</p> <p>To do this, you must add <code>render_dependencies=False</code> to the nested components:</p> <pre><code>card_actions = CardActions.render(\n    kwargs={\"editable\": editable},\n    render_dependencies=False,\n)\n\ncard = Card.render(\n    slots={\"actions\": card_actions},\n    render_dependencies=False,\n)\n\npage = MyPage.render(\n    slots={\"card\": card},\n)\n</code></pre> <p>Why is <code>render_dependencies=False</code> required?</p> <p>This is a technical limitation of the current implementation.</p> <p>As mentioned earlier, each time we call <code>Component.render()</code>, we also call <code>render_dependencies()</code>.</p> <p>However, there is a problem here - When we call <code>render_dependencies()</code> inside <code>CardActions.render()</code>, we extract and REMOVE the info on components' JS and CSS from the HTML. But the template of <code>CardActions</code> contains no <code>{% component_depedencies %}</code> tags, and nor <code>&lt;head&gt;</code> nor <code>&lt;body&gt;</code> HTML tags. So the component's JS and CSS will NOT be inserted, and will be lost.</p> <p>To work around this, you must set <code>render_dependencies=False</code> when rendering pieces of HTML with <code>Component.render()</code> and inserting them into larger structures.</p>"},{"location":"concepts/advanced/rendering_js_css/#summary","title":"Summary","text":"<ol> <li>Every time you render HTML that contained components, you have to call <code>render_dependencies()</code>    on the rendered output.</li> <li>There are several ways to call <code>render_dependencies()</code>:<ul> <li>Using the <code>ComponentDependencyMiddleware</code> middleware</li> <li>Rendering the HTML by calling <code>Component.render()</code> with <code>render_dependencies=True</code> (default)</li> <li>Rendering the HTML by calling <code>Component.render_to_response()</code> (always renders dependencies)</li> <li>Directly passing rendered HTML to <code>render_dependencies()</code></li> </ul> </li> <li>If you pre-render one component to pass it into another, the pre-rendered component must be rendered with    <code>render_dependencies=False</code>.</li> </ol>"},{"location":"concepts/advanced/tag_formatter/","title":"Tag formatters","text":""},{"location":"concepts/advanced/tag_formatter/#customizing-component-tags-with-tagformatter","title":"Customizing component tags with TagFormatter","text":"<p>New in version 0.89</p> <p>By default, components are rendered using the pair of <code>{% component %}</code> / <code>{% endcomponent %}</code> template tags:</p> <pre><code>{% component \"button\" href=\"...\" disabled %}\nClick me!\n{% endcomponent %}\n\n{# or #}\n\n{% component \"button\" href=\"...\" disabled / %}\n</code></pre> <p>You can change this behaviour in the settings under the <code>COMPONENTS.tag_formatter</code>.</p> <p>For example, if you set the tag formatter to</p> <p><code>django_components.component_shorthand_formatter</code></p> <p>then the components' names will be used as the template tags:</p> <pre><code>{% button href=\"...\" disabled %}\n  Click me!\n{% endbutton %}\n\n{# or #}\n\n{% button href=\"...\" disabled / %}\n</code></pre>"},{"location":"concepts/advanced/tag_formatter/#available-tagformatters","title":"Available TagFormatters","text":"<p>django_components provides following predefined TagFormatters:</p> <ul> <li><code>ComponentFormatter</code> (<code>django_components.component_formatter</code>)</li> </ul> <p>Default</p> <p>Uses the <code>component</code> and <code>endcomponent</code> tags, and the component name is gives as the first positional argument.</p> <p>Example as block:</p> <pre><code>{% component \"button\" href=\"...\" %}\n    {% fill \"content\" %}\n        ...\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>Example as inlined tag:</p> <pre><code>{% component \"button\" href=\"...\" / %}\n</code></pre> <ul> <li><code>ShorthandComponentFormatter</code> (<code>django_components.component_shorthand_formatter</code>)</li> </ul> <p>Uses the component name as start tag, and <code>end&lt;component_name&gt;</code>   as an end tag.</p> <p>Example as block:</p> <pre><code>{% button href=\"...\" %}\n    Click me!\n{% endbutton %}\n</code></pre> <p>Example as inlined tag:</p> <pre><code>{% button href=\"...\" / %}\n</code></pre>"},{"location":"concepts/advanced/tag_formatter/#writing-your-own-tagformatter","title":"Writing your own TagFormatter","text":""},{"location":"concepts/advanced/tag_formatter/#background","title":"Background","text":"<p>First, let's discuss how TagFormatters work, and how components are rendered in django_components.</p> <p>When you render a component with <code>{% component %}</code> (or your own tag), the following happens:</p> <ol> <li><code>component</code> must be registered as a Django's template tag</li> <li>Django triggers django_components's tag handler for tag <code>component</code>.</li> <li>The tag handler passes the tag contents for pre-processing to <code>TagFormatter.parse()</code>.</li> </ol> <p>So if you render this:</p> <pre><code>{% component \"button\" href=\"...\" disabled %}\n{% endcomponent %}\n</code></pre> <p>Then <code>TagFormatter.parse()</code> will receive a following input:</p> <pre><code>[\"component\", '\"button\"', 'href=\"...\"', 'disabled']\n</code></pre> <ol> <li><code>TagFormatter</code> extracts the component name and the remaining input.</li> </ol> <p>So, given the above, <code>TagFormatter.parse()</code> returns the following:</p> <pre><code>TagResult(\n    component_name=\"button\",\n    tokens=['href=\"...\"', 'disabled']\n)\n</code></pre> <ol> <li>The tag handler resumes, using the tokens returned from <code>TagFormatter</code>.</li> </ol> <p>So, continuing the example, at this point the tag handler practically behaves as if you rendered:</p> <pre><code>{% component href=\"...\" disabled %}\n</code></pre> <ol> <li>Tag handler looks up the component <code>button</code>, and passes the args, kwargs, and slots to it.</li> </ol>"},{"location":"concepts/advanced/tag_formatter/#tagformatter","title":"TagFormatter","text":"<p><code>TagFormatter</code> handles following parts of the process above:</p> <ul> <li> <p>Generates start/end tags, given a component. This is what you then call from within your template as <code>{% component %}</code>.</p> </li> <li> <p>When you <code>{% component %}</code>, tag formatter pre-processes the tag contents, so it can link back the custom template tag to the right component.</p> </li> </ul> <p>To do so, subclass from <code>TagFormatterABC</code> and implement following method:</p> <ul> <li><code>start_tag</code></li> <li><code>end_tag</code></li> <li><code>parse</code></li> </ul> <p>For example, this is the implementation of <code>ShorthandComponentFormatter</code></p> <pre><code>class ShorthandComponentFormatter(TagFormatterABC):\n    # Given a component name, generate the start template tag\n    def start_tag(self, name: str) -&gt; str:\n        return name  # e.g. 'button'\n\n    # Given a component name, generate the start template tag\n    def end_tag(self, name: str) -&gt; str:\n        return f\"end{name}\"  # e.g. 'endbutton'\n\n    # Given a tag, e.g.\n    # `{% button href=\"...\" disabled %}`\n    #\n    # The parser receives:\n    # `['button', 'href=\"...\"', 'disabled']`\n    def parse(self, tokens: List[str]) -&gt; TagResult:\n        tokens = [*tokens]\n        name = tokens.pop(0)\n        return TagResult(\n            name,  # e.g. 'button'\n            tokens  # e.g. ['href=\"...\"', 'disabled']\n        )\n</code></pre> <p>That's it! And once your <code>TagFormatter</code> is ready, don't forget to update the settings!</p>"},{"location":"concepts/advanced/template_tags/","title":"Custom template tags","text":"<p>Template tags introduced by django-components, such as <code>{% component %}</code> and <code>{% slot %}</code>, offer additional features over the default Django template tags:</p> <ul> <li>Self-closing tags <code>{% mytag / %}</code></li> <li>Allowing the use of <code>:</code>, <code>-</code> (and more) in keys</li> <li>Spread operator <code>...</code></li> <li>Using template tags as inputs to other template tags</li> <li>Flat definition of dictionaries <code>attr:key=val</code></li> <li>Function-like input validation</li> </ul> <p>You too can easily create custom template tags that use the above features.</p>"},{"location":"concepts/advanced/template_tags/#defining-template-tags-with-template_tag","title":"Defining template tags with <code>@template_tag</code>","text":"<p>The simplest way to create a custom template tag is using the <code>template_tag</code> decorator. This decorator allows you to define a template tag by just writing a function that returns the rendered content.</p> <pre><code>from django.template import Context, Library\nfrom django_components import BaseNode, template_tag\n\nlibrary = Library()\n\n@template_tag(\n    library,\n    tag=\"mytag\",\n    end_tag=\"endmytag\",\n    allowed_flags=[\"required\"]\n)\ndef mytag(node: BaseNode, context: Context, name: str, **kwargs) -&gt; str:\n    return f\"Hello, {name}!\"\n</code></pre> <p>This will allow you to use the tag in your templates like this:</p> <pre><code>{% mytag name=\"John\" %}\n{% endmytag %}\n\n{# or with self-closing syntax #}\n{% mytag name=\"John\" / %}\n\n{# or with flags #}\n{% mytag name=\"John\" required %}\n{% endmytag %}\n</code></pre>"},{"location":"concepts/advanced/template_tags/#parameters","title":"Parameters","text":"<p>The <code>@template_tag</code> decorator accepts the following parameters:</p> <ul> <li><code>library</code>: The Django template library to register the tag with</li> <li><code>tag</code>: The name of the template tag (e.g. <code>\"mytag\"</code> for <code>{% mytag %}</code>)</li> <li><code>end_tag</code>: Optional. The name of the end tag (e.g. <code>\"endmytag\"</code> for <code>{% endmytag %}</code>)</li> <li><code>allowed_flags</code>: Optional. List of flags that can be used with the tag (e.g. <code>[\"required\"]</code> for <code>{% mytag required %}</code>)</li> </ul>"},{"location":"concepts/advanced/template_tags/#function-signature","title":"Function signature","text":"<p>The function decorated with <code>@template_tag</code> must accept at least two arguments:</p> <ol> <li><code>node</code>: The node instance (we'll explain this in detail in the next section)</li> <li><code>context</code>: The Django template context</li> </ol> <p>Any additional parameters in your function's signature define what inputs your template tag accepts. For example:</p> <pre><code>@template_tag(library, tag=\"greet\")\ndef greet(\n    node: BaseNode,\n    context: Context,\n    name: str,                    # required positional argument\n    count: int = 1,              # optional positional argument\n    *,                           # keyword-only arguments marker\n    msg: str,                    # required keyword argument\n    mode: str = \"default\",       # optional keyword argument\n) -&gt; str:\n    return f\"{msg}, {name}!\" * count\n</code></pre> <p>This allows the tag to be used like:</p> <pre><code>{# All parameters #}\n{% greet \"John\" count=2 msg=\"Hello\" mode=\"custom\" %}\n\n{# Only required parameters #}\n{% greet \"John\" msg=\"Hello\" %}\n\n{# Missing required parameter - will raise error #}\n{% greet \"John\" %}  {# Error: missing 'msg' #}\n</code></pre> <p>When you pass input to a template tag, it behaves the same way as if you passed the input to a function:</p> <ul> <li>If required parameters are missing, an error is raised</li> <li>If unexpected parameters are passed, an error is raised</li> </ul> <p>To accept keys that are not valid Python identifiers (e.g. <code>data-id</code>), or would conflict with Python keywords (e.g. <code>is</code>), you can use the <code>**kwargs</code> syntax:</p> <pre><code>@template_tag(library, tag=\"greet\")\ndef greet(\n    node: BaseNode,\n    context: Context,\n    **kwargs,\n) -&gt; str:\n    attrs = kwargs.copy()\n    is_var = attrs.pop(\"is\", None)\n    attrs_str = \" \".join(f'{k}=\"{v}\"' for k, v in attrs.items())\n\n    return mark_safe(f\"\"\"\n        &lt;div {attrs_str}&gt;\n            Hello, {is_var}!\n        &lt;/div&gt;\n    \"\"\")\n</code></pre> <p>This allows you to use the tag like this:</p> <pre><code>{% greet is=\"John\" data-id=\"123\" %}\n</code></pre>"},{"location":"concepts/advanced/template_tags/#defining-template-tags-with-basenode","title":"Defining template tags with <code>BaseNode</code>","text":"<p>For more control over your template tag, you can subclass <code>BaseNode</code> directly instead of using the decorator. This gives you access to additional features like the node's internal state and parsing details.</p> <pre><code>from django_components import BaseNode\n\nclass GreetNode(BaseNode):\n    tag = \"greet\"\n    end_tag = \"endgreet\"\n    allowed_flags = [\"required\"]\n\n    def render(self, context: Context, name: str, **kwargs) -&gt; str:\n        # Access node properties\n        if self.flags[\"required\"]:\n            return f\"Required greeting: Hello, {name}!\"\n        return f\"Hello, {name}!\"\n\n# Register the node\nGreetNode.register(library)\n</code></pre>"},{"location":"concepts/advanced/template_tags/#node-properties","title":"Node properties","text":"<p>When using <code>BaseNode</code>, you have access to several useful properties:</p> <ul> <li><code>node_id</code>: A unique identifier for this node instance</li> <li><code>flags</code>: Dictionary of flag values (e.g. <code>{\"required\": True}</code>)</li> <li><code>params</code>: List of raw parameters passed to the tag</li> <li><code>nodelist</code>: The template nodes between the start and end tags</li> <li><code>active_flags</code>: List of flags that are currently set to True</li> </ul> <p>This is what the <code>node</code> parameter in the <code>@template_tag</code> decorator gives you access to - it's the instance of the node class that was automatically created for your template tag.</p>"},{"location":"concepts/advanced/template_tags/#rendering-content-between-tags","title":"Rendering content between tags","text":"<p>When your tag has an end tag, you can access and render the content between the tags using <code>nodelist</code>:</p> <pre><code>class WrapNode(BaseNode):\n    tag = \"wrap\"\n    end_tag = \"endwrap\"\n\n    def render(self, context: Context, tag: str = \"div\", **attrs) -&gt; str:\n        # Render the content between tags\n        inner = self.nodelist.render(context)\n        attrs_str = \" \".join(f'{k}=\"{v}\"' for k, v in attrs.items())\n        return f\"&lt;{tag} {attrs_str}&gt;{inner}&lt;/{tag}&gt;\"\n\n# Usage:\n{% wrap tag=\"section\" class=\"content\" %}\n    Hello, world!\n{% endwrap %}\n</code></pre>"},{"location":"concepts/advanced/template_tags/#unregistering-nodes","title":"Unregistering nodes","text":"<p>You can unregister a node from a library using the <code>unregister</code> method:</p> <pre><code>GreetNode.unregister(library)\n</code></pre> <p>This is particularly useful in testing when you want to clean up after registering temporary tags.</p>"},{"location":"concepts/advanced/testing/","title":"Testing","text":"<p>New in version 0.131</p> <p>The <code>@djc_test</code> decorator is a powerful tool for testing components created with <code>django-components</code>. It ensures that each test is properly isolated, preventing components registered in one test from affecting others.</p>"},{"location":"concepts/advanced/testing/#usage","title":"Usage","text":"<p>The <code>@djc_test</code> decorator can be applied to functions, methods, or classes. When applied to a class, it recursively decorates all methods starting with <code>test_</code>, including those in nested classes. This allows for comprehensive testing of component behavior.</p>"},{"location":"concepts/advanced/testing/#applying-to-a-function","title":"Applying to a Function","text":"<p>To apply <code>djc_test</code> to a function, simply decorate the function as shown below:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\n@djc_test\ndef test_my_component():\n    @register(\"my_component\")\n    class MyComponent(Component):\n        template = \"...\"\n    ...\n</code></pre>"},{"location":"concepts/advanced/testing/#applying-to-a-class","title":"Applying to a Class","text":"<p>When applied to a class, <code>djc_test</code> decorates each <code>test_</code> method individually:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\n@djc_test\nclass TestMyComponent:\n    def test_something(self):\n        ...\n\n    class Nested:\n        def test_something_else(self):\n            ...\n</code></pre> <p>This is equivalent to applying the decorator to each method individually:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\nclass TestMyComponent:\n    @djc_test\n    def test_something(self):\n        ...\n\n    class Nested:\n        @djc_test\n        def test_something_else(self):\n            ...\n</code></pre>"},{"location":"concepts/advanced/testing/#arguments","title":"Arguments","text":"<p>See the API reference for <code>@djc_test</code> for more details.</p>"},{"location":"concepts/advanced/testing/#setting-up-django","title":"Setting Up Django","text":"<p>Before using <code>djc_test</code>, ensure Django is set up:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\n@djc_test\ndef test_my_component():\n    ...\n</code></pre>"},{"location":"concepts/advanced/testing/#example-parametrizing-context-behavior","title":"Example: Parametrizing Context Behavior","text":"<p>You can parametrize the context behavior using <code>djc_test</code>:</p> <pre><code>from django_components.testing import djc_test\n\n@djc_test(\n    # Settings applied to all cases\n    components_settings={\n        \"app_dirs\": [\"custom_dir\"],\n    },\n    # Parametrized settings\n    parametrize=(\n        [\"components_settings\"],\n        [\n            [{\"context_behavior\": \"django\"}],\n            [{\"context_behavior\": \"isolated\"}],\n        ],\n        [\"django\", \"isolated\"],\n    )\n)\ndef test_context_behavior(components_settings):\n    rendered = MyComponent().render()\n    ...\n</code></pre>"},{"location":"concepts/advanced/typing_and_validation/","title":"Typing and validation","text":""},{"location":"concepts/advanced/typing_and_validation/#adding-type-hints-with-generics","title":"Adding type hints with Generics","text":"<p>New in version 0.92</p> <p>The <code>Component</code> class optionally accepts type parameters that allow you to specify the types of args, kwargs, slots, and data:</p> <pre><code>class Button(Component[Args, Kwargs, Slots, Data, JsData, CssData]):\n    ...\n</code></pre> <ul> <li><code>Args</code> - Must be a <code>Tuple</code> or <code>Any</code></li> <li><code>Kwargs</code> - Must be a <code>TypedDict</code> or <code>Any</code></li> <li><code>Data</code> - Must be a <code>TypedDict</code> or <code>Any</code></li> <li><code>Slots</code> - Must be a <code>TypedDict</code> or <code>Any</code></li> </ul> <p>Here's a full example:</p> <pre><code>from typing import NotRequired, Tuple, TypedDict, SlotContent, SlotFunc\n\n# Positional inputs\nArgs = Tuple[int, str]\n\n# Kwargs inputs\nclass Kwargs(TypedDict):\n    variable: str\n    another: int\n    maybe_var: NotRequired[int] # May be ommited\n\n# Data returned from `get_context_data`\nclass Data(TypedDict):\n    variable: str\n\n# The data available to the `my_slot` scoped slot\nclass MySlotData(TypedDict):\n    value: int\n\n# Slots\nclass Slots(TypedDict):\n    # Use SlotFunc for slot functions.\n    # The generic specifies the `data` dictionary\n    my_slot: NotRequired[SlotFunc[MySlotData]]\n    # SlotContent == Union[str, SafeString]\n    another_slot: SlotContent\n\nclass Button(Component[Args, Kwargs, Slots, Data, JsData, CssData]):\n    def get_context_data(self, variable, another):\n        return {\n            \"variable\": variable,\n        }\n</code></pre> <p>When you then call <code>Component.render</code> or <code>Component.render_to_response</code>, you will get type hints:</p> <pre><code>Button.render(\n    # Error: First arg must be `int`, got `float`\n    args=(1.25, \"abc\"),\n    # Error: Key \"another\" is missing\n    kwargs={\n        \"variable\": \"text\",\n    },\n)\n</code></pre>"},{"location":"concepts/advanced/typing_and_validation/#usage-for-python-311","title":"Usage for Python &lt;3.11","text":"<p>On Python 3.8-3.10, use <code>typing_extensions</code></p> <pre><code>from typing_extensions import TypedDict, NotRequired\n</code></pre> <p>Additionally on Python 3.8-3.9, also import <code>annotations</code>:</p> <pre><code>from __future__ import annotations\n</code></pre> <p>Moreover, on 3.10 and less, you may not be able to use <code>NotRequired</code>, and instead you will need to mark either all keys are required, or all keys as optional, using TypeDict's <code>total</code> kwarg.</p> <p>See PEP-655 for more info.</p>"},{"location":"concepts/advanced/typing_and_validation/#passing-additional-args-or-kwargs","title":"Passing additional args or kwargs","text":"<p>You may have a function that supports any number of args or kwargs:</p> <pre><code>def get_context_data(self, *args, **kwargs):\n    ...\n</code></pre> <p>This is not supported with the typed components.</p> <p>As a workaround:</p> <ul> <li>For <code>*args</code>, set a positional argument that accepts a list of values:</li> </ul> <pre><code># Tuple of one member of list of strings\nArgs = Tuple[List[str]]\n</code></pre> <ul> <li>For <code>*kwargs</code>, set a keyword argument that accepts a dictionary of values:</li> </ul> <pre><code>class Kwargs(TypedDict):\n    variable: str\n    another: int\n    # Pass any extra keys under `extra`\n    extra: Dict[str, any]\n</code></pre>"},{"location":"concepts/advanced/typing_and_validation/#handling-no-args-or-no-kwargs","title":"Handling no args or no kwargs","text":"<p>To declare that a component accepts no Args, Kwargs, etc, you can use <code>EmptyTuple</code> and <code>EmptyDict</code> types:</p> <pre><code>from django_components import Component, EmptyDict, EmptyTuple\n\nArgs = EmptyTuple\nKwargs = Data = Slots = EmptyDict\n\nclass Button(Component[Args, Kwargs, Slots, Data, JsData, CssData]):\n    ...\n</code></pre>"},{"location":"concepts/advanced/typing_and_validation/#runtime-input-validation-with-types","title":"Runtime input validation with types","text":"<p>New in version 0.96</p> <p>NOTE: Kwargs, slots, and data validation is supported only for Python &gt;=3.11</p> <p>In Python 3.11 and later, when you specify the component types, you will get also runtime validation of the inputs you pass to <code>Component.render</code> or <code>Component.render_to_response</code>.</p> <p>So, using the example from before, if you ignored the type errors and still ran the following code:</p> <pre><code>Button.render(\n    # Error: First arg must be `int`, got `float`\n    args=(1.25, \"abc\"),\n    # Error: Key \"another\" is missing\n    kwargs={\n        \"variable\": \"text\",\n    },\n)\n</code></pre> <p>This would raise a <code>TypeError</code>:</p> <pre><code>Component 'Button' expected positional argument at index 0 to be &lt;class 'int'&gt;, got 1.25 of type &lt;class 'float'&gt;\n</code></pre> <p>In case you need to skip these errors, you can either set the faulty member to <code>Any</code>, e.g.:</p> <pre><code># Changed `int` to `Any`\nArgs = Tuple[Any, str]\n</code></pre> <p>Or you can replace <code>Args</code> with <code>Any</code> altogether, to skip the validation of args:</p> <pre><code># Replaced `Args` with `Any`\nclass Button(Component[Any, Kwargs, Slots, Data, JsData, CssData]):\n    ...\n</code></pre> <p>Same applies to kwargs, data, and slots.</p>"},{"location":"concepts/fundamentals/access_component_input/","title":"Accessing component inputs","text":"<p>When you call <code>Component.render</code> or <code>Component.render_to_response</code>, the inputs to these methods can be accessed from within the instance under <code>self.input</code>.</p> <p>This means that you can use <code>self.input</code> inside:</p> <ul> <li><code>get_context_data</code></li> <li><code>get_template_name</code></li> <li><code>get_template</code></li> <li><code>on_render_before</code></li> <li><code>on_render_after</code></li> </ul> <p><code>self.input</code> is only defined during the execution of <code>Component.render</code>, and raises a <code>RuntimeError</code> when called outside of this context.</p> <p><code>self.input</code> has the same fields as the input to <code>Component.render</code>:</p> <pre><code>class TestComponent(Component):\n    def get_context_data(self, var1, var2, variable, another, **attrs):\n        assert self.input.args == (123, \"str\")\n        assert self.input.kwargs == {\"variable\": \"test\", \"another\": 1}\n        assert self.input.slots == {\"my_slot\": \"MY_SLOT\"}\n        assert isinstance(self.input.context, Context)\n\n        return {\n            \"variable\": variable,\n        }\n\nrendered = TestComponent.render(\n    kwargs={\"variable\": \"test\", \"another\": 1},\n    args=(123, \"str\"),\n    slots={\"my_slot\": \"MY_SLOT\"},\n)\n</code></pre> <p>NOTE: The slots in <code>self.input.slots</code> are normalized to slot functions.</p>"},{"location":"concepts/fundamentals/autodiscovery/","title":"Autodiscovery","text":"<p>Every component that you want to use in the template with the <code>{% component %}</code> tag needs to be registered with the <code>ComponentRegistry</code>. Normally, we use the <code>@register</code> decorator for that:</p> <pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    ...\n</code></pre> <p>But for the component to be registered, the code needs to be executed - and for that, the file needs to be imported as a module.</p> <p>One way to do that is by importing all your components in <code>apps.py</code>:</p> <pre><code>from django.apps import AppConfig\n\nclass MyAppConfig(AppConfig):\n    name = \"my_app\"\n\n    def ready(self) -&gt; None:\n        from components.card.card import Card\n        from components.list.list import List\n        from components.menu.menu import Menu\n        from components.button.button import Button\n        ...\n</code></pre> <p>However, there's a simpler way!</p> <p>By default, the Python files in the <code>COMPONENTS.dirs</code> directories (and app-level <code>[app]/components/</code>) are auto-imported in order to auto-register the components.</p> <p>Autodiscovery occurs when Django is loaded, during the <code>AppConfig.ready</code> hook of the <code>apps.py</code> file.</p> <p>If you are using autodiscovery, keep a few points in mind:</p> <ul> <li>Avoid defining any logic on the module-level inside the <code>components</code> dir, that you would not want to run anyway.</li> <li>Components inside the auto-imported files still need to be registered with <code>@register</code></li> <li>Auto-imported component files must be valid Python modules, they must use suffix <code>.py</code>, and module name should follow PEP-8.</li> <li>Subdirectories and files starting with an underscore <code>_</code> (except <code>__init__.py</code>) are ignored.</li> </ul> <p>Autodiscovery can be disabled in the settings.</p>"},{"location":"concepts/fundamentals/autodiscovery/#manually-trigger-autodiscovery","title":"Manually trigger autodiscovery","text":"<p>Autodiscovery can be also triggered manually, using the <code>autodiscover</code> function. This is useful if you want to run autodiscovery at a custom point of the lifecycle:</p> <pre><code>from django_components import autodiscover\n\nautodiscover()\n</code></pre> <p>To get the same list of modules that <code>autodiscover()</code> would return, but without importing them, use <code>get_component_files()</code>:</p> <pre><code>from django_components import get_component_files\n\nmodules = get_component_files(\".py\")\n</code></pre>"},{"location":"concepts/fundamentals/component_context_scope/","title":"Component context and scope","text":"<p>By default, context variables are passed down the template as in regular Django - deeper scopes can access the variables from the outer scopes. So if you have several nested forloops, then inside the deep-most loop you can access variables defined by all previous loops.</p> <p>With this in mind, the <code>{% component %}</code> tag behaves similarly to <code>{% include %}</code> tag - inside the component tag, you can access all variables that were defined outside of it.</p> <p>And just like with <code>{% include %}</code>, if you don't want a specific component template to have access to the parent context, add <code>only</code> to the <code>{% component %}</code> tag:</p> <pre><code>{% component \"calendar\" date=\"2015-06-19\" only / %}\n</code></pre> <p>NOTE: <code>{% csrf_token %}</code> tags need access to the top-level context, and they will not function properly if they are rendered in a component that is called with the <code>only</code> modifier.</p> <p>If you find yourself using the <code>only</code> modifier often, you can set the context_behavior option to <code>\"isolated\"</code>, which automatically applies the <code>only</code> modifier. This is useful if you want to make sure that components don't accidentally access the outer context.</p> <p>Components can also access the outer context in their context methods like <code>get_context_data</code> by accessing the property <code>self.outer_context</code>.</p>"},{"location":"concepts/fundamentals/component_context_scope/#example-of-accessing-outer-context","title":"Example of Accessing Outer Context","text":"<pre><code>&lt;div&gt;\n  {% component \"calender\" / %}\n&lt;/div&gt;\n</code></pre> <p>Assuming that the rendering context has variables such as <code>date</code>, you can use <code>self.outer_context</code> to access them from within <code>get_context_data</code>. Here's how you might implement it:</p> <pre><code>class Calender(Component):\n\n    ...\n\n    def get_context_data(self):\n        outer_field = self.outer_context[\"date\"]\n        return {\n            \"date\": outer_fields,\n        }\n</code></pre> <p>However, as a best practice, it\u2019s recommended not to rely on accessing the outer context directly through <code>self.outer_context</code>. Instead, explicitly pass the variables to the component. For instance, continue passing the variables in the component tag as shown in the previous examples.</p>"},{"location":"concepts/fundamentals/component_context_scope/#context-behavior","title":"Context behavior","text":"<p>django_components supports both Django and Vue-like behavior when it comes to passing data to and through components. This can be configured in context_behavior.</p> <p>This has two modes:</p> <ul> <li> <p><code>\"django\"</code></p> <p>The default Django template behavior.</p> <p>Inside the <code>{% fill %}</code> tag, the context variables you can access are a union of:</p> <ul> <li>All the variables that were OUTSIDE the fill tag, including any\\   <code>{% with %}</code> tags.</li> <li>Any loops (<code>{% for ... %}</code>)   that the <code>{% fill %}</code> tag is part of.</li> <li>Data returned from <code>Component.get_context_data()</code>   of the component that owns the fill tag.</li> </ul> </li> <li> <p><code>\"isolated\"</code></p> <p>Similar behavior to Vue or React, this is useful if you want to make sure that components don't accidentally access variables defined outside of the component.</p> <p>Inside the <code>{% fill %}</code> tag, you can ONLY access variables from 2 places:</p> <ul> <li>Any loops (<code>{% for ... %}</code>)   that the <code>{% fill %}</code> tag is part of.</li> <li><code>Component.get_context_data()</code>   of the component which defined the template (AKA the \"root\" component).</li> </ul> </li> </ul> <p>Warning</p> <p>Notice that the component whose <code>get_context_data()</code> we use inside <code>{% fill %}</code> is NOT the same across the two modes!</p> <p>Consider this example:</p> <pre><code>class Outer(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% component \"inner\" %}\n          {% fill \"content\" %}\n            {{ my_var }}\n          {% endfill %}\n        {% endcomponent %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre> <ul> <li> <p><code>\"django\"</code> - <code>my_var</code> has access to data from <code>get_context_data()</code> of both <code>Inner</code> and <code>Outer</code>.   If there are variables defined in both, then <code>Inner</code> overshadows <code>Outer</code>.</p> </li> <li> <p><code>\"isolated\"</code> - <code>my_var</code> has access to data from <code>get_context_data()</code> of ONLY <code>Outer</code>.</p> </li> </ul>"},{"location":"concepts/fundamentals/component_context_scope/#example-django","title":"Example \"django\"","text":"<p>Given this template:</p> <pre><code>@register(\"root_comp\")\nclass RootComp(Component):\n    template = \"\"\"\n        {% with cheese=\"feta\" %}\n            {% component 'my_comp' %}\n                {{ my_var }}  # my_var\n                {{ cheese }}  # cheese\n            {% endcomponent %}\n        {% endwith %}\n    \"\"\"\n\n    def get_context_data(self):\n        return { \"my_var\": 123 }\n</code></pre> <p>Then if <code>get_context_data()</code> of the component <code>\"my_comp\"</code> returns following data:</p> <pre><code>{ \"my_var\": 456 }\n</code></pre> <p>Then the template will be rendered as:</p> <pre><code>456   # my_var\nfeta  # cheese\n</code></pre> <p>Because <code>\"my_comp\"</code> overshadows the outer variable <code>\"my_var\"</code>, so <code>{{ my_var }}</code> equals <code>456</code>.</p> <p>And variable <code>\"cheese\"</code> equals <code>feta</code>, because the fill CAN access all the data defined in the outer layers, like the <code>{% with %}</code> tag.</p>"},{"location":"concepts/fundamentals/component_context_scope/#example-isolated","title":"Example \"isolated\"","text":"<p>Given this template:</p> <pre><code>class RootComp(Component):\n    template = \"\"\"\n        {% with cheese=\"feta\" %}\n            {% component 'my_comp' %}\n                {{ my_var }}  # my_var\n                {{ cheese }}  # cheese\n            {% endcomponent %}\n        {% endwith %}\n    \"\"\"\n\n    def get_context_data(self):\n        return { \"my_var\": 123 }\n</code></pre> <p>Then if <code>get_context_data()</code> of the component <code>\"my_comp\"</code> returns following data:</p> <pre><code>{ \"my_var\": 456 }\n</code></pre> <p>Then the template will be rendered as:</p> <pre><code>123   # my_var\n    # cheese\n</code></pre> <p>Because variables <code>\"my_var\"</code> and <code>\"cheese\"</code> are searched only inside <code>RootComponent.get_context_data()</code>. But since <code>\"cheese\"</code> is not defined there, it's empty.</p> <p>Info</p> <p>Notice that the variables defined with the <code>{% with %}</code> tag are ignored inside the <code>{% fill %}</code> tag with the <code>\"isolated\"</code> mode.</p>"},{"location":"concepts/fundamentals/components_as_views/","title":"Components as views","text":"<p>New in version 0.34</p> <p>Note: Since 0.92, Component no longer subclasses View. To configure the View class, set the nested <code>Component.View</code> class</p> <p>Components can now be used as views:</p> <ul> <li> <p>Components define the <code>Component.as_view()</code> class method that can be used the same as <code>View.as_view()</code>.</p> </li> <li> <p>By default, you can define GET, POST or other HTTP handlers directly on the Component, same as you do with View. For example, you can override <code>get</code> and <code>post</code> to handle GET and POST requests, respectively.</p> </li> <li> <p>In addition, <code>Component</code> now has a <code>render_to_response</code> method that renders the component template based on the provided context and slots' data and returns an <code>HttpResponse</code> object.</p> </li> </ul>"},{"location":"concepts/fundamentals/components_as_views/#component-as-view-example","title":"Component as view example","text":"<p>Here's an example of a calendar component defined as a view:</p> <pre><code># In a file called [project root]/components/calendar.py\nfrom django_components import Component, ComponentView, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n\n    template = \"\"\"\n        &lt;div class=\"calendar-component\"&gt;\n            &lt;div class=\"header\"&gt;\n                {% slot \"header\" / %}\n            &lt;/div&gt;\n            &lt;div class=\"body\"&gt;\n                Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n            &lt;/div&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    # Handle GET requests\n    def get(self, request, *args, **kwargs):\n        context = {\n            \"date\": request.GET.get(\"date\", \"2020-06-06\"),\n        }\n        slots = {\n            \"header\": \"Calendar header\",\n        }\n        # Return HttpResponse with the rendered content\n        return self.render_to_response(\n            context=context,\n            slots=slots,\n        )\n</code></pre> <p>Then, to use this component as a view, you should create a <code>urls.py</code> file in your components directory, and add a path to the component's view:</p> <pre><code># In a file called [project root]/components/urls.py\nfrom django.urls import path\nfrom components.calendar.calendar import Calendar\n\nurlpatterns = [\n    path(\"calendar/\", Calendar.as_view()),\n]\n</code></pre> <p><code>Component.as_view()</code> is a shorthand for calling <code>View.as_view()</code> and passing the component instance as one of the arguments.</p> <p>Remember to add <code>__init__.py</code> to your components directory, so that Django can find the <code>urls.py</code> file.</p> <p>Finally, include the component's urls in your project's <code>urls.py</code> file:</p> <pre><code># In a file called [project root]/urls.py\nfrom django.urls import include, path\n\nurlpatterns = [\n    path(\"components/\", include(\"components.urls\")),\n]\n</code></pre> <p>Note: Slots content are automatically escaped by default to prevent XSS attacks. To disable escaping, set <code>escape_slots_content=False</code> in the <code>render_to_response</code> method. If you do so, you should make sure that any content you pass to the slots is safe, especially if it comes from user input.</p> <p>If you're planning on passing an HTML string, check Django's use of <code>format_html</code> and <code>mark_safe</code>.</p>"},{"location":"concepts/fundamentals/components_as_views/#modifying-the-view-class","title":"Modifying the View class","text":"<p>The View class that handles the requests is defined on <code>Component.View</code>.</p> <p>When you define a GET or POST handlers on the <code>Component</code> class, like so:</p> <pre><code>class MyComponent(Component):\n    def get(self, request, *args, **kwargs):\n        return self.render_to_response(\n            context={\n                \"date\": request.GET.get(\"date\", \"2020-06-06\"),\n            },\n        )\n\n    def post(self, request, *args, **kwargs) -&gt; HttpResponse:\n        variable = request.POST.get(\"variable\")\n        return self.render_to_response(\n            kwargs={\"variable\": variable}\n        )\n</code></pre> <p>Then the request is still handled by <code>Component.View.get()</code> or <code>Component.View.post()</code> methods. However, by default, <code>Component.View.get()</code> points to <code>Component.get()</code>, and so on.</p> <pre><code>class ComponentView(View):\n    component: Component = None\n    ...\n\n    def get(self, request, *args, **kwargs):\n        return self.component.get(request, *args, **kwargs)\n\n    def post(self, request, *args, **kwargs):\n        return self.component.post(request, *args, **kwargs)\n\n    ...\n</code></pre> <p>If you want to define your own <code>View</code> class, you need to:</p> <ol> <li>Set the class as <code>Component.View</code></li> <li>Subclass from <code>ComponentView</code>, so the View instance has access to the component instance.</li> </ol> <p>In the example below, we added extra logic into <code>View.setup()</code>.</p> <p>Note that the POST handler is still defined at the top. This is because <code>View</code> subclasses <code>ComponentView</code>, which defines the <code>post()</code> method that calls <code>Component.post()</code>.</p> <p>If you were to overwrite the <code>View.post()</code> method, then <code>Component.post()</code> would be ignored.</p> <pre><code>from django_components import Component, ComponentView\n\nclass MyComponent(Component):\n\n    def post(self, request, *args, **kwargs) -&gt; HttpResponse:\n        variable = request.POST.get(\"variable\")\n        return self.component.render_to_response(\n            kwargs={\"variable\": variable}\n        )\n\n    class View(ComponentView):\n        def setup(self, request, *args, **kwargs):\n            super(request, *args, **kwargs)\n\n            do_something_extra(request, *args, **kwargs)\n</code></pre>"},{"location":"concepts/fundamentals/components_in_python/","title":"Components in Python","text":"<p>New in version 0.81</p> <p>Components can be rendered outside of Django templates, calling them as regular functions (\"React-style\").</p> <p>The component class defines <code>render</code> and <code>render_to_response</code> class methods. These methods accept positional args, kwargs, and slots, offering the same flexibility as the <code>{% component %}</code> tag:</p> <pre><code>class SimpleComponent(Component):\n    template = \"\"\"\n        {% load component_tags %}\n        hello: {{ hello }}\n        foo: {{ foo }}\n        kwargs: {{ kwargs|safe }}\n        slot_first: {% slot \"first\" required / %}\n    \"\"\"\n\n    def get_context_data(self, arg1, arg2, **kwargs):\n        return {\n            \"hello\": arg1,\n            \"foo\": arg2,\n            \"kwargs\": kwargs,\n        }\n\nrendered = SimpleComponent.render(\n    args=[\"world\", \"bar\"],\n    kwargs={\"kw1\": \"test\", \"kw2\": \"ooo\"},\n    slots={\"first\": \"FIRST_SLOT\"},\n    context={\"from_context\": 98},\n)\n</code></pre> <p>Renders:</p> <pre><code>hello: world\nfoo: bar\nkwargs: {'kw1': 'test', 'kw2': 'ooo'}\nslot_first: FIRST_SLOT\n</code></pre>"},{"location":"concepts/fundamentals/components_in_python/#inputs-of-render-and-render_to_response","title":"Inputs of <code>render</code> and <code>render_to_response</code>","text":"<p>Both <code>render</code> and <code>render_to_response</code> accept the same input:</p> <pre><code>Component.render(\n    context: Mapping | django.template.Context | None = None,\n    args: List[Any] | None = None,\n    kwargs: Dict[str, Any] | None = None,\n    slots: Dict[str, str | SafeString | SlotFunc] | None = None,\n    escape_slots_content: bool = True\n) -&gt; str:\n</code></pre> <ul> <li> <p><code>args</code> - Positional args for the component. This is the same as calling the component   as <code>{% component \"my_comp\" arg1 arg2 ... %}</code></p> </li> <li> <p><code>kwargs</code> - Keyword args for the component. This is the same as calling the component   as <code>{% component \"my_comp\" key1=val1 key2=val2 ... %}</code></p> </li> <li> <p><code>slots</code> - Component slot fills. This is the same as pasing <code>{% fill %}</code> tags to the component.   Accepts a dictionary of <code>{ slot_name: slot_content }</code> where <code>slot_content</code> can be a string   or <code>SlotFunc</code>.</p> </li> <li> <p><code>escape_slots_content</code> - Whether the content from <code>slots</code> should be escaped. <code>True</code> by default to prevent XSS attacks. If you disable escaping, you should make sure that any content you pass to the slots is safe, especially if it comes from user input.</p> </li> <li> <p><code>context</code> - A context (dictionary or Django's Context) within which the component   is rendered. The keys on the context can be accessed from within the template.</p> </li> <li> <p>NOTE: In \"isolated\" mode, context is NOT accessible, and data MUST be passed via     component's args and kwargs.</p> </li> <li> <p><code>request</code> - A Django request object. This is used to enable Django template <code>context_processors</code> to run,   allowing for template tags like <code>{% csrf_token %}</code> and variables like <code>{{ debug }}</code>.  </p> </li> <li>Similar behavior can be achieved with provide / inject.</li> <li>This is used internally to convert <code>context</code> to a RequestContext. It does nothing if <code>context</code> is already      a <code>Context</code> instance.</li> </ul>"},{"location":"concepts/fundamentals/components_in_python/#slotfunc","title":"<code>SlotFunc</code>","text":"<p>When rendering components with slots in <code>render</code> or <code>render_to_response</code>, you can pass either a string or a function.</p> <p>The function has following signature:</p> <pre><code>def render_func(\n   context: Context,\n   data: Dict[str, Any],\n   slot_ref: SlotRef,\n) -&gt; str | SafeString:\n    return nodelist.render(ctx)\n</code></pre> <ul> <li><code>context</code> - Django's Context available to the Slot Node.</li> <li><code>data</code> - Data passed to the <code>{% slot %}</code> tag. See Scoped Slots.</li> <li><code>slot_ref</code> - The default slot content. See Accessing original content of slots.</li> <li>NOTE: The slot is lazily evaluated. To render the slot, convert it to string with <code>str(slot_ref)</code>.</li> </ul> <p>Example:</p> <pre><code>def footer_slot(ctx, data, slot_ref):\n   return f\"\"\"\n      SLOT_DATA: {data['abc']}\n      ORIGINAL: {slot_ref}\n   \"\"\"\n\nMyComponent.render_to_response(\n    slots={\n        \"footer\": footer_slot,\n   },\n)\n</code></pre>"},{"location":"concepts/fundamentals/components_in_python/#response-class-of-render_to_response","title":"Response class of <code>render_to_response</code>","text":"<p>While <code>render</code> method returns a plain string, <code>render_to_response</code> wraps the rendered content in a \"Response\" class. By default, this is <code>django.http.HttpResponse</code>.</p> <p>If you want to use a different Response class in <code>render_to_response</code>, set the <code>Component.response_class</code> attribute:</p> <pre><code>class MyResponse(HttpResponse):\n    def __init__(self, *args, **kwargs) -&gt; None:\n        super().__init__(*args, **kwargs)\n        # Configure response\n        self.headers = ...\n        self.status = ...\n\nclass SimpleComponent(Component):\n    response_class = MyResponse\n    template: types.django_html = \"HELLO\"\n\nresponse = SimpleComponent.render_to_response()\nassert isinstance(response, MyResponse)\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/","title":"Defining HTML / JS / CSS files","text":"<p>As you could have seen in the tutorial, there's multiple ways how you can associate HTML / JS / CSS with a component:</p> <ul> <li>You can set <code>Component.template</code>,   <code>Component.css</code> and   <code>Component.js</code> to define the main HTML / CSS / JS for a component   as inlined code.</li> <li>You can set <code>Component.template_file</code>,   <code>Component.css_file</code> and   <code>Component.js_file</code> to define the main HTML / CSS / JS   for a component in separate files.</li> <li>You can link additional CSS / JS files using   <code>Component.Media.js</code>   and <code>Component.Media.css</code>.</li> </ul> <p>Warning</p> <p>You cannot use both inlined code and separate file for a single language type:</p> <ul> <li>You can only either set <code>Component.template</code> or <code>Component.template_file</code></li> <li>You can only either set <code>Component.css</code> or <code>Component.css_file</code></li> <li>You can only either set <code>Component.js</code> or <code>Component.js_file</code></li> </ul> <p>However, you can freely mix these for different languages:</p> <pre><code>class MyTable(Component):\n    template: types.django_html = \"\"\"\n      &lt;div class=\"welcome\"&gt;\n        Hi there!\n      &lt;/div&gt;\n    \"\"\"\n    js_file = \"my_table.js\"\n    css_file = \"my_table.css\"\n</code></pre> <p>Note</p> <p>django-component's management of files is inspired by Django's <code>Media</code> class.</p> <p>To be familiar with how Django handles static files, we recommend reading also:</p> <ul> <li>How to manage static files (e.g. images, JavaScript, CSS)</li> </ul>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#defining-file-paths-relative-to-component","title":"Defining file paths relative to component","text":"<p>As seen in the getting started example, to associate HTML / JS / CSS files with a component, you can set them as <code>Component.template_file</code>, <code>Component.js_file</code> and <code>Component.css_file</code> respectively:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"template.html\"\n    css_file = \"style.css\"\n    js_file = \"script.js\"\n</code></pre> <p>In the example above, we defined the files relative to the directory where the component file is defined.</p> <p>Alternatively, you can specify the file paths relative to the directories set in <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code>.</p> <p>If you specify the paths relative to component's directory, django-componenents does the conversion automatically for you.</p> <p>Thus, assuming that <code>COMPONENTS.dirs</code> contains path <code>[project root]/components</code>, the example above is the same as writing:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar/template.html\"\n    css_file = \"calendar/style.css\"\n    js_file = \"calendar/script.js\"\n</code></pre> <p>Important</p> <p>File path resolution in-depth</p> <p>At component class creation, django-components checks all file paths defined on the component (e.g. <code>Component.template_file</code>).</p> <p>For each file path, it checks if the file path is relative to the component's directory. And such file exists, the component's file path is re-written to be defined relative to a first matching directory in <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code>.</p> <p>Example:</p> [root]/components/mytable/mytable.py<pre><code>class MyTable(Component):\n    template_file = \"mytable.html\"\n</code></pre> <ol> <li>Component <code>MyTable</code> is defined in file <code>[root]/components/mytable/mytable.py</code>.</li> <li>The component's directory is thus <code>[root]/components/mytable/</code>.</li> <li>Because <code>MyTable.template_file</code> is <code>mytable.html</code>, django-components tries to     resolve it as <code>[root]/components/mytable/mytable.html</code>.</li> <li>django-components checks the filesystem. If there's no such file, nothing happens.</li> <li>If there IS such file, django-components tries to rewrite the path.</li> <li>django-components searches <code>COMPONENTS.dirs</code> and <code>COMPONENTS.app_dirs</code> for a first     directory that contains <code>[root]/components/mytable/mytable.html</code>.</li> <li>It comes across <code>[root]/components/</code>, which DOES contain the path to <code>mytable.html</code>.</li> <li>Thus, it rewrites <code>template_file</code> from <code>mytable.html</code> to <code>mytable/mytable.html</code>.</li> </ol> <p>NOTE: In case of ambiguity, the preference goes to resolving the files relative to the component's directory.</p>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#defining-additional-js-and-css-files","title":"Defining additional JS and CSS files","text":"<p>Each component can have only a single template, and single main JS and CSS. However, you can define additional JS or CSS using the nested <code>Component.Media</code> class.</p> <p>This <code>Media</code> class behaves similarly to Django's Media class:</p> <ul> <li>Paths are generally handled as static file paths, and resolved URLs are rendered to HTML with   <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A path that starts with <code>http</code>, <code>https</code>, or <code>/</code> is considered a URL, skipping the static file resolution.   This path is still rendered to HTML with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A <code>SafeString</code>,   or a function (with <code>__html__</code> method) is considered an already-formatted HTML tag, skipping both static file   resolution and rendering with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>You can set <code>extend</code> to configure     whether to inherit JS / CSS from parent components. See     Controlling Media Inheritance.</li> </ul> <p>However, there's a few differences from Django's Media class:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list,    or (CSS-only) a dictonary (See <code>ComponentMediaInput</code>).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>,    <code>SafeString</code>, or a function    (See <code>ComponentMediaInputPath</code>).</li> </ol> <pre><code>class MyTable(Component):\n    class Media:\n        js = [\n            \"path/to/script.js\",\n            \"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\",  # AlpineJS\n        ]\n        css = {\n            \"all\": [\n                \"path/to/style.css\",\n                \"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\",  # TailwindCSS\n            ],\n            \"print\": [\"path/to/style2.css\"],\n        }\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#configuring-css-media-types","title":"Configuring CSS Media Types","text":"<p>You can define which stylesheets will be associated with which CSS Media types. You do so by defining CSS files as a dictionary.</p> <p>See the corresponding Django Documentation.</p> <p>Again, you can set either a single file or a list of files per media type:</p> <pre><code>class MyComponent(Component):\n    class Media:\n        css = {\n            \"all\": \"path/to/style1.css\",\n            \"print\": [\"path/to/style2.css\", \"path/to/style3.css\"],\n        }\n</code></pre> <p>Note</p> <p>When you define CSS as a string or a list, the <code>all</code> media type is implied.</p> <p>So these two examples are the same:</p> <pre><code>class MyComponent(Component):\n    class Media:\n        css = \"path/to/style1.css\"\n</code></pre> <pre><code>class MyComponent(Component):\n    class Media:\n        css = {\n            \"all\": [\"path/to/style1.css\"],\n        }\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#supported-types-for-file-paths","title":"Supported types for file paths","text":"<p>File paths can be any of:</p> <ul> <li><code>str</code></li> <li><code>bytes</code></li> <li><code>PathLike</code> (<code>__fspath__</code> method)</li> <li><code>SafeData</code> (<code>__html__</code> method)</li> <li><code>Callable</code> that returns any of the above, evaluated at class creation (<code>__new__</code>)</li> </ul> <p>See <code>ComponentMediaInputPath</code>.</p> <pre><code>from pathlib import Path\n\nfrom django.utils.safestring import mark_safe\n\nclass SimpleComponent(Component):\n    class Media:\n        css = [\n            mark_safe('&lt;link href=\"/static/calendar/style1.css\" rel=\"stylesheet\" /&gt;'),\n            Path(\"calendar/style1.css\"),\n            \"calendar/style2.css\",\n            b\"calendar/style3.css\",\n            lambda: \"calendar/style4.css\",\n        ]\n        js = [\n            mark_safe('&lt;script src=\"/static/calendar/script1.js\"&gt;&lt;/script&gt;'),\n            Path(\"calendar/script1.js\"),\n            \"calendar/script2.js\",\n            b\"calendar/script3.js\",\n            lambda: \"calendar/script4.js\",\n        ]\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#paths-as-objects","title":"Paths as objects","text":"<p>In the example above, you can see that when we used Django's <code>mark_safe()</code> to mark a string as a <code>SafeString</code>, we had to define the full <code>&lt;script&gt;</code>/<code>&lt;link&gt;</code> tag.</p> <p>This is an extension of Django's Paths as objects feature, where \"safe\" strings are taken as is, and accessed only at render time.</p> <p>Because of that, the paths defined as \"safe\" strings are NEVER resolved, neither relative to component's directory, nor relative to <code>COMPONENTS.dirs</code>.</p> <p>\"Safe\" strings can be used to lazily resolve a path, or to customize the <code>&lt;script&gt;</code> or <code>&lt;link&gt;</code> tag for individual paths:</p> <p>In the example below, we make use of \"safe\" strings to add <code>type=\"module\"</code> to the script tag that will fetch <code>calendar/script2.js</code>. In this case, we implemented a \"safe\" string by defining a <code>__html__</code> method.</p> <pre><code>class ModuleJsPath:\n    def __init__(self, static_path: str) -&gt; None:\n        self.static_path = static_path\n\n    def __html__(self):\n        full_path = static(self.static_path)\n        return format_html(\n            f'&lt;script type=\"module\" src=\"{full_path}\"&gt;&lt;/script&gt;'\n        )\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar/template.html\"\n\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n\n    class Media:\n        css = \"calendar/style1.css\"\n        js = [\n            # &lt;script&gt; tag constructed by Media class\n            \"calendar/script1.js\",\n            # Custom &lt;script&gt; tag\n            ModuleJsPath(\"calendar/script2.js\"),\n        ]\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#customize-how-paths-are-rendered-into-html-tags","title":"Customize how paths are rendered into HTML tags","text":"<p>Sometimes you may need to change how all CSS <code>&lt;link&gt;</code> or JS <code>&lt;script&gt;</code> tags are rendered for a given component. You can achieve this by providing your own subclass of Django's <code>Media</code> class to component's <code>media_class</code> attribute.</p> <p>Normally, the JS and CSS paths are passed to <code>Media</code> class, which decides how the paths are resolved and how the <code>&lt;link&gt;</code> and <code>&lt;script&gt;</code> tags are constructed.</p> <p>To change how the tags are constructed, you can override the <code>Media.render_js</code> and <code>Media.render_css</code> methods:</p> <pre><code>from django.forms.widgets import Media\nfrom django_components import Component, register\n\nclass MyMedia(Media):\n    # Same as original Media.render_js, except\n    # the `&lt;script&gt;` tag has also `type=\"module\"`\n    def render_js(self):\n        tags = []\n        for path in self._js:\n            if hasattr(path, \"__html__\"):\n                tag = path.__html__()\n            else:\n                tag = format_html(\n                    '&lt;script type=\"module\" src=\"{}\"&gt;&lt;/script&gt;',\n                    self.absolute_path(path)\n                )\n        return tags\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar/template.html\"\n    css_file = \"calendar/style.css\"\n    js_file = \"calendar/script.js\"\n\n    class Media:\n        css = \"calendar/style1.css\"\n        js = \"calendar/script2.js\"\n\n    # Override the behavior of Media class\n    media_class = MyMedia\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#accessing-components-html-js-css","title":"Accessing component's HTML / JS / CSS","text":"<p>Component's HTML / CSS / JS is resolved and loaded lazily.</p> <p>This means that, when you specify any of <code>template_file</code>, <code>js_file</code>, <code>css_file</code>, or <code>Media.js/css</code>, these file paths will be resolved only once you either:</p> <ol> <li> <p>Access any of the following attributes on the component:</p> <ul> <li><code>media</code>,  <code>template</code>,  <code>template_file</code>,  <code>js</code>,  <code>js_file</code>,  <code>css</code>,  <code>css_file</code></li> </ul> </li> <li> <p>Render the component.</p> </li> </ol> <p>Once the component's media files have been loaded once, they will remain in-memory on the Component class:</p> <ul> <li>HTML from <code>Component.template_file</code>   will be available under <code>Component.template</code></li> <li>CSS from <code>Component.css_file</code>   will be available under <code>Component.css</code></li> <li>JS from <code>Component.js_file</code>   will be available under <code>Component.js</code></li> </ul> <p>Thus, whether you define HTML via <code>Component.template_file</code> or <code>Component.template</code>, you can always access the HTML content under <code>Component.template</code>. And the same applies for JS and CSS.</p> <p>Example:</p> <pre><code># When we create Calendar component, the files like `calendar/template.html`\n# are not yet loaded!\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar/template.html\"\n    css_file = \"calendar/style.css\"\n    js_file = \"calendar/script.js\"\n\n    class Media:\n        css = \"calendar/style1.css\"\n        js = \"calendar/script2.js\"\n\n# It's only at this moment that django-components reads the files like `calendar/template.html`\nprint(Calendar.css)\n# Output:\n# .calendar {\n#   width: 200px;\n#   background: pink;\n# }\n</code></pre> <p>Warning</p> <p>Do NOT modify HTML / CSS / JS after it has been loaded</p> <p>django-components assumes that the component's media files like <code>js_file</code> or <code>Media.js/css</code> are static.</p> <p>If you need to dynamically change these media files, consider instead defining multiple Components.</p> <p>Modifying these files AFTER the component has been loaded at best does nothing. However, this is an untested behavior, which may lead to unexpected errors.</p>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#accessing-components-media-files","title":"Accessing component's Media files","text":"<p>To access the files that you defined under <code>Component.Media</code>, use <code>Component.media</code> (lowercase). This is consistent behavior with Django's Media class.</p> <pre><code>class MyComponent(Component):\n    class Media:\n        js = \"path/to/script.js\"\n        css = \"path/to/style.css\"\n\nprint(MyComponent.media)\n# Output:\n# &lt;script src=\"/static/path/to/script.js\"&gt;&lt;/script&gt;\n# &lt;link href=\"/static/path/to/style.css\" media=\"all\" rel=\"stylesheet\"&gt;\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#componentmedia-vs-componentmedia","title":"<code>Component.Media</code> vs <code>Component.media</code>","text":"<p>When working with component media files, there are a few important concepts to understand:</p> <ul> <li> <p><code>Component.Media</code></p> <ul> <li>Is the \"raw\" media definition, or the input, which holds only the component's own media definition</li> <li>This class is NOT instantiated, it merely holds the JS / CSS files.</li> </ul> </li> <li> <p><code>Component.media</code></p> <ul> <li>Returns all resolved media files, including those inherited from parent components</li> <li>Is an instance of <code>Component.media_class</code></li> </ul> </li> </ul> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass ChildComponent(ParentComponent):\n    class Media:\n        js = [\"child.js\"]\n\n# Access only this component's media\nprint(ChildComponent.Media.js)  # [\"child.js\"]\n\n# Access all inherited media\nprint(ChildComponent.media._js)  # [\"parent.js\", \"child.js\"]\n</code></pre> <p>Note</p> <p>You should not manually modify <code>Component.media</code> or <code>Component.Media</code> after the component has been resolved, as this may lead to unexpected behavior.</p> <p>If you want to modify the class that is instantiated for <code>Component.media</code>, you can configure <code>Component.media_class</code> (See example).</p>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#controlling-media-inheritance","title":"Controlling Media Inheritance","text":"<p>By default, the media files are inherited from the parent component.</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"parent.js\", \"script.js\"]\n</code></pre> <p>You can set the component NOT to inherit from the parent component by setting the <code>extend</code> attribute to <code>False</code>:</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        extend = False  # Don't inherit parent media\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"script.js\"]\n</code></pre> <p>Alternatively, you can specify which components to inherit from. In such case, the media files are inherited ONLY from the specified components, and NOT from the original parent components:</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        # Only inherit from these, ignoring the files from the parent\n        extend = [OtherComponent1, OtherComponent2]\n\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"script.js\", \"other1.js\", \"other2.js\"]\n</code></pre> <p>Info</p> <p>The <code>extend</code> behaves consistently with Django's Media class, with one exception:</p> <ul> <li>When you set <code>extend</code> to a list, the list is expected to contain Component classes (or other classes that have a nested <code>Media</code> class).</li> </ul>"},{"location":"concepts/fundamentals/html_attributes/","title":"HTML attributes","text":"<p>New in version 0.74:</p> <p>You can use the <code>html_attrs</code> tag to render HTML attributes, given a dictionary of values.</p> <p>So if you have a template:</p> <pre><code>&lt;div class=\"{{ classes }}\" data-id=\"{{ my_id }}\"&gt;\n&lt;/div&gt;\n</code></pre> <p>You can simplify it with <code>html_attrs</code> tag:</p> <pre><code>&lt;div {% html_attrs attrs %}&gt;\n&lt;/div&gt;\n</code></pre> <p>where <code>attrs</code> is:</p> <pre><code>attrs = {\n    \"class\": classes,\n    \"data-id\": my_id,\n}\n</code></pre> <p>This feature is inspired by <code>merge_attrs</code> tag of django-web-components and \"fallthrough attributes\" feature of Vue.</p>"},{"location":"concepts/fundamentals/html_attributes/#removing-atttributes","title":"Removing atttributes","text":"<p>Attributes that are set to <code>None</code> or <code>False</code> are NOT rendered.</p> <p>So given this input:</p> <pre><code>attrs = {\n    \"class\": \"text-green\",\n    \"required\": False,\n    \"data-id\": None,\n}\n</code></pre> <p>And template:</p> <pre><code>&lt;div {% html_attrs attrs %}&gt;\n&lt;/div&gt;\n</code></pre> <p>Then this renders:</p> <pre><code>&lt;div class=\"text-green\"&gt;&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/html_attributes/#boolean-attributes","title":"Boolean attributes","text":"<p>In HTML, boolean attributes are usually rendered with no value. Consider the example below where the first button is disabled and the second is not:</p> <pre><code>&lt;button disabled&gt;Click me!&lt;/button&gt; &lt;button&gt;Click me!&lt;/button&gt;\n</code></pre> <p>HTML rendering with <code>html_attrs</code> tag or <code>attributes_to_string</code> works the same way, where <code>key=True</code> is rendered simply as <code>key</code>, and <code>key=False</code> is not render at all.</p> <p>So given this input:</p> <pre><code>attrs = {\n    \"disabled\": True,\n    \"autofocus\": False,\n}\n</code></pre> <p>And template:</p> <pre><code>&lt;div {% html_attrs attrs %}&gt;\n&lt;/div&gt;\n</code></pre> <p>Then this renders:</p> <pre><code>&lt;div disabled&gt;&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/html_attributes/#default-attributes","title":"Default attributes","text":"<p>Sometimes you may want to specify default values for attributes. You can pass a second argument (or kwarg <code>defaults</code>) to set the defaults.</p> <pre><code>&lt;div {% html_attrs attrs defaults %}&gt;\n    ...\n&lt;/div&gt;\n</code></pre> <p>In the example above, if <code>attrs</code> contains e.g. the <code>class</code> key, <code>html_attrs</code> will render:</p> <p><code>class=\"{{ attrs.class }}\"</code></p> <p>Otherwise, <code>html_attrs</code> will render:</p> <p><code>class=\"{{ defaults.class }}\"</code></p>"},{"location":"concepts/fundamentals/html_attributes/#appending-attributes","title":"Appending attributes","text":"<p>For the <code>class</code> HTML attribute, it's common that we want to join multiple values, instead of overriding them. For example, if you're authoring a component, you may want to ensure that the component will ALWAYS have a specific class. Yet, you may want to allow users of your component to supply their own classes.</p> <p>We can achieve this by adding extra kwargs. These values will be appended, instead of overwriting the previous value.</p> <p>So if we have a variable <code>attrs</code>:</p> <pre><code>attrs = {\n    \"class\": \"my-class pa-4\",\n}\n</code></pre> <p>And on <code>html_attrs</code> tag, we set the key <code>class</code>:</p> <pre><code>&lt;div {% html_attrs attrs class=\"some-class\" %}&gt;\n&lt;/div&gt;\n</code></pre> <p>Then these will be merged and rendered as:</p> <pre><code>&lt;div data-value=\"my-class pa-4 some-class\"&gt;&lt;/div&gt;\n</code></pre> <p>To simplify merging of variables, you can supply the same key multiple times, and these will be all joined together:</p> <pre><code>{# my_var = \"class-from-var text-red\" #}\n&lt;div {% html_attrs attrs class=\"some-class another-class\" class=my_var %}&gt;\n&lt;/div&gt;\n</code></pre> <p>Renders:</p> <pre><code>&lt;div\n  data-value=\"my-class pa-4 some-class another-class class-from-var text-red\"\n&gt;&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/html_attributes/#rules-for-html_attrs","title":"Rules for <code>html_attrs</code>","text":"<ol> <li>Both <code>attrs</code> and <code>defaults</code> can be passed as positional args</li> </ol> <p><code>{% html_attrs attrs defaults key=val %}</code></p> <p>or as kwargs</p> <p><code>{% html_attrs key=val defaults=defaults attrs=attrs %}</code></p> <ol> <li> <p>Both <code>attrs</code> and <code>defaults</code> are optional (can be omitted)</p> </li> <li> <p>Both <code>attrs</code> and <code>defaults</code> are dictionaries, and we can define them the same way we define dictionaries for the <code>component</code> tag. So either as <code>attrs=attrs</code> or <code>attrs:key=value</code>.</p> </li> <li> <p>All other kwargs are appended and can be repeated.</p> </li> </ol>"},{"location":"concepts/fundamentals/html_attributes/#examples-for-html_attrs","title":"Examples for <code>html_attrs</code>","text":"<p>Assuming that:</p> <pre><code>class_from_var = \"from-var\"\n\nattrs = {\n    \"class\": \"from-attrs\",\n    \"type\": \"submit\",\n}\n\ndefaults = {\n    \"class\": \"from-defaults\",\n    \"role\": \"button\",\n}\n</code></pre> <p>Then:</p> <ul> <li>Empty tag  <code>{% html_attr %}</code></li> </ul> <p>renders (empty string):  <code></code></p> <ul> <li>Only kwargs  <code>{% html_attr class=\"some-class\" class=class_from_var data-id=\"123\" %}</code></li> </ul> <p>renders:  <code>class=\"some-class from-var\" data-id=\"123\"</code></p> <ul> <li>Only attrs  <code>{% html_attr attrs %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs\" type=\"submit\"</code></p> <ul> <li>Attrs as kwarg  <code>{% html_attr attrs=attrs %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs\" type=\"submit\"</code></p> <ul> <li>Only defaults (as kwarg)  <code>{% html_attr defaults=defaults %}</code></li> </ul> <p>renders:  <code>class=\"from-defaults\" role=\"button\"</code></p> <ul> <li>Attrs using the <code>prefix:key=value</code> construct  <code>{% html_attr attrs:class=\"from-attrs\" attrs:type=\"submit\" %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs\" type=\"submit\"</code></p> <ul> <li>Defaults using the <code>prefix:key=value</code> construct  <code>{% html_attr defaults:class=\"from-defaults\" %}</code></li> </ul> <p>renders:  <code>class=\"from-defaults\" role=\"button\"</code></p> <ul> <li>All together (1) - attrs and defaults as positional args:  <code>{% html_attrs attrs defaults class=\"added_class\" class=class_from_var data-id=123 %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs added_class from-var\" type=\"submit\" role=\"button\" data-id=123</code></p> <ul> <li>All together (2) - attrs and defaults as kwargs args:  <code>{% html_attrs class=\"added_class\" class=class_from_var data-id=123 attrs=attrs defaults=defaults %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs added_class from-var\" type=\"submit\" role=\"button\" data-id=123</code></p> <ul> <li>All together (3) - mixed:  <code>{% html_attrs attrs defaults:class=\"default-class\" class=\"added_class\" class=class_from_var data-id=123 %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs added_class from-var\" type=\"submit\" data-id=123</code></p>"},{"location":"concepts/fundamentals/html_attributes/#full-example-for-html_attrs","title":"Full example for <code>html_attrs</code>","text":"<pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template: t.django_html = \"\"\"\n        &lt;div\n            {% html_attrs attrs\n                defaults:class=\"pa-4 text-red\"\n                class=\"my-comp-date\"\n                class=class_from_var\n                data-id=\"123\"\n            %}\n        &gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self, date: Date, attrs: dict):\n        return {\n            \"date\": date,\n            \"attrs\": attrs,\n            \"class_from_var\": \"extra-class\"\n        }\n\n@register(\"parent\")\nclass Parent(Component):\n    template: t.django_html = \"\"\"\n        {% component \"my_comp\"\n            date=date\n            attrs:class=\"pa-0 border-solid border-red\"\n            attrs:data-json=json_data\n            attrs:@click=\"(e) =&gt; onClick(e, 'from_parent')\"\n        / %}\n    \"\"\"\n\n    def get_context_data(self, date: Date):\n        return {\n            \"date\": datetime.now(),\n            \"json_data\": json.dumps({\"value\": 456})\n        }\n</code></pre> <p>Note: For readability, we've split the tags across multiple lines.</p> <p>Inside <code>MyComp</code>, we defined a default attribute</p> <p><code>defaults:class=\"pa-4 text-red\"</code></p> <p>So if <code>attrs</code> includes key <code>class</code>, the default above will be ignored.</p> <p><code>MyComp</code> also defines <code>class</code> key twice. It means that whether the <code>class</code> attribute is taken from <code>attrs</code> or <code>defaults</code>, the two <code>class</code> values will be appended to it.</p> <p>So by default, <code>MyComp</code> renders:</p> <pre><code>&lt;div class=\"pa-4 text-red my-comp-date extra-class\" data-id=\"123\"&gt;...&lt;/div&gt;\n</code></pre> <p>Next, let's consider what will be rendered when we call <code>MyComp</code> from <code>Parent</code> component.</p> <p><code>MyComp</code> accepts a <code>attrs</code> dictionary, that is passed to <code>html_attrs</code>, so the contents of that dictionary are rendered as the HTML attributes.</p> <p>In <code>Parent</code>, we make use of passing dictionary key-value pairs as kwargs to define individual attributes as if they were regular kwargs.</p> <p>So all kwargs that start with <code>attrs:</code> will be collected into an <code>attrs</code> dict.</p> <pre><code>    attrs:class=\"pa-0 border-solid border-red\"\n    attrs:data-json=json_data\n    attrs:@click=\"(e) =&gt; onClick(e, 'from_parent')\"\n</code></pre> <p>And <code>get_context_data</code> of <code>MyComp</code> will receive <code>attrs</code> input with following keys:</p> <pre><code>attrs = {\n    \"class\": \"pa-0 border-solid\",\n    \"data-json\": '{\"value\": 456}',\n    \"@click\": \"(e) =&gt; onClick(e, 'from_parent')\",\n}\n</code></pre> <p><code>attrs[\"class\"]</code> overrides the default value for <code>class</code>, whereas other keys will be merged.</p> <p>So in the end <code>MyComp</code> will render:</p> <pre><code>&lt;div\n  class=\"pa-0 border-solid my-comp-date extra-class\"\n  data-id=\"123\"\n  data-json='{\"value\": 456}'\n  @click=\"(e) =&gt; onClick(e, 'from_parent')\"\n&gt;\n  ...\n&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/html_attributes/#rendering-html-attributes-outside-of-templates","title":"Rendering HTML attributes outside of templates","text":"<p>If you need to use serialize HTML attributes outside of Django template and the <code>html_attrs</code> tag, you can use <code>attributes_to_string</code>:</p> <pre><code>from django_components.attributes import attributes_to_string\n\nattrs = {\n    \"class\": \"my-class text-red pa-4\",\n    \"data-id\": 123,\n    \"required\": True,\n    \"disabled\": False,\n    \"ignored-attr\": None,\n}\n\nattributes_to_string(attrs)\n# 'class=\"my-class text-red pa-4\" data-id=\"123\" required'\n</code></pre>"},{"location":"concepts/fundamentals/http_request/","title":"HTTP Request","text":"<p>The most common use of django-components is to render HTML for a given request. As such, there are a few features that are dependent on the request object.</p>"},{"location":"concepts/fundamentals/http_request/#passing-and-accessing-httprequest","title":"Passing and accessing HttpRequest","text":"<p>In regular Django templates, the request object is available only within the <code>RequestContext</code>.</p> <p>In Components, you can either use <code>RequestContext</code>, or pass the <code>request</code> object explicitly to <code>Component.render()</code> and <code>Component.render_to_response()</code>.</p> <p>When a component is nested in another, the child component uses parent's <code>request</code> object.</p> <p>You can access the request object under <code>Component.request</code>:</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        return {\n            'user_id': self.request.GET['user_id'],\n        }\n\n# \u2705 With request\nMyComponent.render(request=request)\nMyComponent.render(context=RequestContext(request, {}))\n\n# \u274c Without request\nMyComponent.render()\nMyComponent.render(context=Context({}))\n</code></pre>"},{"location":"concepts/fundamentals/http_request/#context-processors","title":"Context Processors","text":"<p>Components support Django's context processors.</p> <p>In regular Django templates, the context processors are applied only when the template is rendered with <code>RequestContext</code>.</p> <p>Components allow you to pass the <code>request</code> object explicitly. Thus, the context processors are applied to components either when:</p> <ul> <li>The component is rendered with <code>RequestContext</code> (Regular Django behavior)</li> <li>The component is rendered with a regular <code>Context</code> (or none), but you set the <code>request</code> kwarg     of <code>Component.render()</code>.</li> <li>The component is nested in another component that matches one of the two conditions above.</li> </ul> <pre><code># \u274c No context processors\nrendered = MyComponent.render()\nrendered = MyComponent.render(Context({}))\n\n# \u2705 With context processors\nrendered = MyComponent.render(request=request)\nrendered = MyComponent.render(Context({}), request=request)\nrendered = MyComponent.render(RequestContext(request, {}))\n</code></pre> <p>When a component is rendered within a template with <code>{% component %}</code> tag, context processors are available depending on whether the template is rendered with <code>RequestContext</code> or not.</p> <pre><code>template = Template(\"\"\"\n&lt;div&gt;\n  {% component \"MyComponent\" / %}\n&lt;/div&gt;\n\"\"\")\n\n# \u274c No context processors\nrendered = template.render(Context({}))\n\n# \u2705 With context processors\nrendered = template.render(RequestContext(request, {}))\n</code></pre>"},{"location":"concepts/fundamentals/http_request/#accessing-context-processors-data","title":"Accessing context processors data","text":"<p>The data from context processors is automatically available within the component's template.</p> <pre><code>class MyComponent(Component):\n    template = \"\"\"\n        &lt;div&gt;\n            {{ csrf_token }}\n        &lt;/div&gt;\n    \"\"\"\n\nMyComponent.render(request=request)\n</code></pre> <p>You can also access the context processors data from within <code>get_context_data()</code> and other methods under <code>Component.context_processors_data</code>.</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        csrf_token = self.context_processors_data['csrf_token']\n        return {\n            'csrf_token': csrf_token,\n        }\n</code></pre>"},{"location":"concepts/fundamentals/single_file_components/","title":"Single-file components","text":"<p>Components can be defined in a single file, which is useful for small components. To do this, you can use the <code>template</code>, <code>js</code>, and <code>css</code> class attributes instead of the <code>template_file</code>, <code>js_file</code>,  and <code>css_file</code>.</p> <p>For example, here's the calendar component from the Getting started tutorial, defined in a single file:</p> [project root]/components/calendar.py<pre><code>from django_components import Component, register, types\n\n@register(\"calendar\")\nclass Calendar(Component):\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n\n    template: types.django_html = \"\"\"\n        &lt;div class=\"calendar\"&gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css: types.css = \"\"\"\n        .calendar {\n            width: 200px;\n            background: pink;\n        }\n        .calendar span {\n            font-weight: bold;\n        }\n    \"\"\"\n\n    js: types.js = \"\"\"\n        (function(){\n            if (document.querySelector(\".calendar\")) {\n                document.querySelector(\".calendar\").onclick = () =&gt; {\n                    alert(\"Clicked calendar!\");\n                };\n            }\n        })()\n    \"\"\"\n</code></pre> <p>This makes it easy to create small components without having to create a separate template, CSS, and JS file.</p> <p>To add syntax highlighting to these snippets, head over to Syntax highlighting.</p>"},{"location":"concepts/fundamentals/slots/","title":"Slots","text":"<p>New in version 0.26:</p> <ul> <li>The <code>slot</code> tag now serves only to declare new slots inside the component template.</li> <li>To override the content of a declared slot, use the newly introduced <code>fill</code> tag instead.</li> <li>Whereas unfilled slots used to raise a warning, filling a slot is now optional by default.</li> <li>To indicate that a slot must be filled, the new <code>required</code> option should be added at the end of the <code>slot</code> tag.</li> </ul> <p>Components support something called 'slots'. When a component is used inside another template, slots allow the parent template to override specific parts of the child component by passing in different content. This mechanism makes components more reusable and composable. This behavior is similar to slots in Vue.</p> <p>In the example below we introduce two block tags that work hand in hand to make this work. These are...</p> <ul> <li><code>{% slot &lt;name&gt; %}</code>/<code>{% endslot %}</code>: Declares a new slot in the component template.</li> <li><code>{% fill &lt;name&gt; %}</code>/<code>{% endfill %}</code>: (Used inside a <code>{% component %}</code> tag pair.) Fills a declared slot with the specified content.</li> </ul> <p>Let's update our calendar component to support more customization. We'll add <code>slot</code> tag pairs to its template, template.html.</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"header\" %}Calendar header{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"body\" %}Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>When using the component, you specify which slots you want to fill and where you want to use the defaults from the template. It looks like this:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"body\" %}\n        Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>Since the 'header' fill is unspecified, it's taken from the base template. If you put this in a template, and pass in <code>date=2020-06-06</code>, this is what gets rendered:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        Calendar header\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        Can you believe it's already &lt;span&gt;2020-06-06&lt;/span&gt;??\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/slots/#named-slots","title":"Named slots","text":"<p>As seen in the previouse section, you can use <code>{% fill slot_name %}</code> to insert content into a specific slot.</p> <p>You can define fills for multiple slot simply by defining them all within the <code>{% component %} {% endcomponent %}</code> tags:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"header\" %}\n        Hi this is header!\n    {% endfill %}\n    {% fill \"body\" %}\n        Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>You can also use <code>{% for %}</code>, <code>{% with %}</code>, or other non-component tags (even <code>{% include %}</code>) to construct the <code>{% fill %}</code> tags, as long as these other tags do not leave any text behind!</p> <pre><code>{% component \"table\" %}\n  {% for slot_name in slots %}\n    {% fill name=slot_name %}\n      {{ slot_name }}\n    {% endfill %}\n  {% endfor %}\n\n  {% with slot_name=\"abc\" %}\n    {% fill name=slot_name %}\n      {{ slot_name }}\n    {% endfill %}\n  {% endwith %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#default-slot","title":"Default slot","text":"<p>Added in version 0.28</p> <p>As you can see, component slots lets you write reusable containers that you fill in when you use a component. This makes for highly reusable components that can be used in different circumstances.</p> <p>It can become tedious to use <code>fill</code> tags everywhere, especially when you're using a component that declares only one slot. To make things easier, <code>slot</code> tags can be marked with an optional keyword: <code>default</code>.</p> <p>When added to the tag (as shown below), this option lets you pass filling content directly in the body of a <code>component</code> tag pair \u2013 without using a <code>fill</code> tag. Choose carefully, though: a component template may contain at most one slot that is marked as <code>default</code>. The <code>default</code> option can be combined with other slot options, e.g. <code>required</code>.</p> <p>Here's the same example as before, except with default slots and implicit filling.</p> <p>The template:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"header\" %}Calendar header{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"body\" default %}Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>Including the component (notice how the <code>fill</code> tag is omitted):</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n{% endcomponent %}\n</code></pre> <p>The rendered result (exactly the same as before):</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n  &lt;div class=\"header\"&gt;Calendar header&lt;/div&gt;\n  &lt;div class=\"body\"&gt;Can you believe it's already &lt;span&gt;2020-06-06&lt;/span&gt;??&lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>You may be tempted to combine implicit fills with explicit <code>fill</code> tags. This will not work. The following component template will raise an error when rendered.</p> <pre><code>{# DON'T DO THIS #}\n{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"header\" %}Totally new header!{% endfill %}\n    Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n{% endcomponent %}\n</code></pre> <p>Instead, you can use a named fill with name <code>default</code> to target the default fill:</p> <pre><code>{# THIS WORKS #}\n{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"header\" %}Totally new header!{% endfill %}\n    {% fill \"default\" %}\n        Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>NOTE: If you doubly-fill a slot, that is, that both <code>{% fill \"default\" %}</code> and <code>{% fill \"header\" %}</code> would point to the same slot, this will raise an error when rendered.</p>"},{"location":"concepts/fundamentals/slots/#accessing-default-slot-in-python","title":"Accessing default slot in Python","text":"<p>Since the default slot is stored under the slot name <code>default</code>, you can access the default slot like so:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        default_slot = self.input.slots[\"default\"]\n        return {\n            \"default_slot\": default_slot,\n        }\n</code></pre>"},{"location":"concepts/fundamentals/slots/#render-fill-in-multiple-places","title":"Render fill in multiple places","text":"<p>Added in version 0.70</p> <p>You can render the same content in multiple places by defining multiple slots with identical names:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"image\" %}Image here{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"image\" %}Image here{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>So if used like:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"image\" %}\n        &lt;img src=\"...\" /&gt;\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>This renders:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        &lt;img src=\"...\" /&gt;\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        &lt;img src=\"...\" /&gt;\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/slots/#default-and-required-slots","title":"Default and required slots","text":"<p>If you use a slot multiple times, you can still mark the slot as <code>default</code> or <code>required</code>. For that, you must mark each slot individually, e.g.:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"image\" default required %}Image here{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"image\" default required %}Image here{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>Which you can then use as regular default slot:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    &lt;img src=\"...\" /&gt;\n{% endcomponent %}\n</code></pre> <p>Since each slot is tagged individually, you can have multiple slots with the same name but different conditions.</p> <p>E.g. in this example, we have a component that renders a user avatar - a small circular image with a profile picture or name initials.</p> <p>If the component is given <code>image_src</code> or <code>name_initials</code> variables, the <code>image</code> slot is optional. But if neither of those are provided, you MUST fill the <code>image</code> slot.</p> <pre><code>&lt;div class=\"avatar\"&gt;\n    {% if image_src %}\n        {% slot \"image\" default %}\n            &lt;img src=\"{{ image_src }}\" /&gt;\n        {% endslot %}\n    {% elif name_initials %}\n        {% slot \"image\" default %}\n            &lt;div style=\"\n                border-radius: 25px;\n                width: 50px;\n                height: 50px;\n                background: blue;\n            \"&gt;\n                {{ name_initials }}\n            &lt;/div&gt;\n        {% endslot %}\n    {% else %}\n        {% slot \"image\" default required / %}\n    {% endif %}\n&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/slots/#accessing-original-content-of-slots","title":"Accessing original content of slots","text":"<p>Added in version 0.26</p> <p>NOTE: In version 0.77, the syntax was changed from</p> <pre><code>{% fill \"my_slot\" as \"alias\" %} {{ alias.default }}\n</code></pre> <p>to</p> <pre><code>{% fill \"my_slot\" default=\"slot_default\" %} {{ slot_default }}\n</code></pre> <p>Sometimes you may want to keep the original slot, but only wrap or prepend/append content to it. To do so, you can access the default slot via the <code>default</code> kwarg.</p> <p>Similarly to the <code>data</code> attribute, you specify the variable name through which the default slot will be made available.</p> <p>For instance, let's say you're filling a slot called 'body'. To render the original slot, assign it to a variable using the <code>'default'</code> keyword. You then render this variable to insert the default content:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"body\" default=\"body_default\" %}\n        {{ body_default }}. Have a great day!\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>This produces:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        Calendar header\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        Today's date is &lt;span&gt;2020-06-06&lt;/span&gt;. Have a great day!\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>To access the original content of a default slot, set the name to <code>default</code>:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"default\" default=\"slot_default\" %}\n        {{ slot_default }}. Have a great day!\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#conditional-slots","title":"Conditional slots","text":"<p>Added in version 0.26.</p> <p>NOTE: In version 0.70, <code>{% if_filled %}</code> tags were replaced with <code>{{ component_vars.is_filled }}</code> variables. If your slot name contained special characters, see the section Accessing <code>is_filled</code> of slot names with special characters.</p> <p>In certain circumstances, you may want the behavior of slot filling to depend on whether or not a particular slot is filled.</p> <p>For example, suppose we have the following component template:</p> <pre><code>&lt;div class=\"frontmatter-component\"&gt;\n    &lt;div class=\"title\"&gt;\n        {% slot \"title\" %}Title{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"subtitle\"&gt;\n        {% slot \"subtitle\" %}{# Optional subtitle #}{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>By default the slot named 'subtitle' is empty. Yet when the component is used without explicit fills, the div containing the slot is still rendered, as shown below:</p> <pre><code>&lt;div class=\"frontmatter-component\"&gt;\n  &lt;div class=\"title\"&gt;Title&lt;/div&gt;\n  &lt;div class=\"subtitle\"&gt;&lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>This may not be what you want. What if instead the outer 'subtitle' div should only be included when the inner slot is in fact filled?</p> <p>The answer is to use the <code>{{ component_vars.is_filled.&lt;name&gt; }}</code> variable. You can use this together with Django's <code>{% if/elif/else/endif %}</code> tags to define a block whose contents will be rendered only if the component slot with the corresponding 'name' is filled.</p> <p>This is what our example looks like with <code>component_vars.is_filled</code>.</p> <pre><code>&lt;div class=\"frontmatter-component\"&gt;\n    &lt;div class=\"title\"&gt;\n        {% slot \"title\" %}Title{% endslot %}\n    &lt;/div&gt;\n    {% if component_vars.is_filled.subtitle %}\n    &lt;div class=\"subtitle\"&gt;\n        {% slot \"subtitle\" %}{# Optional subtitle #}{% endslot %}\n    &lt;/div&gt;\n    {% endif %}\n&lt;/div&gt;\n</code></pre> <p>Here's our example with more complex branching.</p> <pre><code>&lt;div class=\"frontmatter-component\"&gt;\n    &lt;div class=\"title\"&gt;\n        {% slot \"title\" %}Title{% endslot %}\n    &lt;/div&gt;\n    {% if component_vars.is_filled.subtitle %}\n    &lt;div class=\"subtitle\"&gt;\n        {% slot \"subtitle\" %}{# Optional subtitle #}{% endslot %}\n    &lt;/div&gt;\n    {% elif component_vars.is_filled.title %}\n        ...\n    {% elif component_vars.is_filled.&lt;name&gt; %}\n        ...\n    {% endif %}\n&lt;/div&gt;\n</code></pre> <p>Sometimes you're not interested in whether a slot is filled, but rather that it isn't. To negate the meaning of <code>component_vars.is_filled</code>, simply treat it as boolean and negate it with <code>not</code>:</p> <pre><code>{% if not component_vars.is_filled.subtitle %}\n&lt;div class=\"subtitle\"&gt;\n    {% slot \"subtitle\" / %}\n&lt;/div&gt;\n{% endif %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#accessing-is_filled-of-slot-names-with-special-characters","title":"Accessing <code>is_filled</code> of slot names with special characters","text":"<p>To be able to access a slot name via <code>component_vars.is_filled</code>, the slot name needs to be composed of only alphanumeric characters and underscores (e.g. <code>this__isvalid_123</code>).</p> <p>However, you can still define slots with other special characters. In such case, the slot name in <code>component_vars.is_filled</code> is modified to replace all invalid characters into <code>_</code>.</p> <p>So a slot named <code>\"my super-slot :)\"</code> will be available as <code>component_vars.is_filled.my_super_slot___</code>.</p> <p>Same applies when you are accessing <code>is_filled</code> from within the Python, e.g.:</p> <pre><code>class MyTable(Component):\n    def on_render_before(self, context, template) -&gt; None:\n        # \u2705 Works\n        if self.is_filled[\"my_super_slot___\"]:\n            # Do something\n\n        # \u274c Does not work\n        if self.is_filled[\"my super-slot :)\"]:\n            # Do something\n</code></pre>"},{"location":"concepts/fundamentals/slots/#conditional-fills","title":"Conditional fills","text":"<p>Similarly, you can use <code>{% if %}</code> and <code>{% for %}</code> when defining the <code>{% fill %}</code> tags, to conditionally fill the slots when using the componnet:</p> <p>In the example below, the <code>{% fill \"footer\" %}</code> fill is used only if the condition is true. If falsy, the fill is ignored, and so the <code>my_table</code> component will use its default content for the <code>footer</code> slot.</p> <pre><code>{% component \"my_table\" %}\n    {% if editable %}\n        {% fill \"footer\" %}\n            &lt;input name=\"name\" /&gt;\n        {% endfill %}\n    {% endif %}\n{% endcomponent %}\n</code></pre> <p>You can even combine <code>{% if %}</code> and <code>{% for %}</code>:</p> <pre><code>{% component \"my_table\" %}\n    {% for header in headers %}\n        {% if header != \"hyperlink\" %}\n            {# Generate fill name like `header.my_column` #}\n            {% fill name=\"header.\"|add:header\" %}\n                &lt;b&gt;{{ header }}&lt;/b&gt;\n            {% endfill %}\n        {% endif %}\n    {% endfor %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#scoped-slots","title":"Scoped slots","text":"<p>Added in version 0.76:</p> <p>Consider a component with slot(s). This component may do some processing on the inputs, and then use the processed variable in the slot's default template:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        &lt;div&gt;\n            {% slot \"content\" default %}\n                input: {{ input }}\n            {% endslot %}\n        &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self, input):\n        processed_input = do_something(input)\n        return {\"input\": processed_input}\n</code></pre> <p>You may want to design a component so that users of your component can still access the <code>input</code> variable, so they don't have to recompute it.</p> <p>This behavior is called \"scoped slots\". This is inspired by Vue scoped slots and scoped slots of django-web-components.</p> <p>Using scoped slots consists of two steps:</p> <ol> <li>Passing data to <code>slot</code> tag</li> <li>Accessing data in <code>fill</code> tag</li> </ol>"},{"location":"concepts/fundamentals/slots/#passing-data-to-slots","title":"Passing data to slots","text":"<p>To pass the data to the <code>slot</code> tag, simply pass them as keyword attributes (<code>key=value</code>):</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        &lt;div&gt;\n            {% slot \"content\" default input=input %}\n                input: {{ input }}\n            {% endslot %}\n        &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self, input):\n        processed_input = do_something(input)\n        return {\n            \"input\": processed_input,\n        }\n</code></pre>"},{"location":"concepts/fundamentals/slots/#accessing-slot-data-in-fill","title":"Accessing slot data in fill","text":"<p>Next, we head over to where we define a fill for this slot. Here, to access the slot data we set the <code>data</code> attribute to the name of the variable through which we want to access the slot data. In the example below, we set it to <code>data</code>:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"content\" data=\"slot_data\" %}\n        {{ slot_data.input }}\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>To access slot data on a default slot, you have to explictly define the <code>{% fill %}</code> tags.</p> <p>So this works:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"content\" data=\"slot_data\" %}\n        {{ slot_data.input }}\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>While this does not:</p> <pre><code>{% component \"my_comp\" data=\"data\" %}\n    {{ data.input }}\n{% endcomponent %}\n</code></pre> <p>Note: You cannot set the <code>data</code> attribute and <code>default</code> attribute) to the same name. This raises an error:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"content\" data=\"slot_var\" default=\"slot_var\" %}\n        {{ slot_var.input }}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#slot-data-of-default-slots","title":"Slot data of default slots","text":"<p>To access data of a default slot, you can specify <code>{% fill name=\"default\" %}</code>:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"default\" data=\"slot_data\" %}\n        {{ slot_data.input }}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#dynamic-slots-and-fills","title":"Dynamic slots and fills","text":"<p>Until now, we were declaring slot and fill names statically, as a string literal, e.g.</p> <pre><code>{% slot \"content\" / %}\n</code></pre> <p>However, sometimes you may want to generate slots based on the given input. One example of this is a table component like that of Vuetify, which creates a header and an item slots for each user-defined column.</p> <p>In django_components you can achieve the same, simply by using a variable (or a template expression) instead of a string literal:</p> <pre><code>&lt;table&gt;\n  &lt;tr&gt;\n    {% for header in headers %}\n      &lt;th&gt;\n        {% slot \"header-{{ header.key }}\" value=header.title %}\n          {{ header.title }}\n        {% endslot %}\n      &lt;/th&gt;\n    {% endfor %}\n  &lt;/tr&gt;\n&lt;/table&gt;\n</code></pre> <p>When using the component, you can either set the fill explicitly:</p> <pre><code>{% component \"table\" headers=headers items=items %}\n  {% fill \"header-name\" data=\"data\" %}\n    &lt;b&gt;{{ data.value }}&lt;/b&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <p>Or also use a variable:</p> <pre><code>{% component \"table\" headers=headers items=items %}\n  {# Make only the active column bold #}\n  {% fill \"header-{{ active_header_name }}\" data=\"data\" %}\n    &lt;b&gt;{{ data.value }}&lt;/b&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <p>NOTE: It's better to use static slot names whenever possible for clarity. The dynamic slot names should be reserved for advanced use only.</p> <p>Lastly, in rare cases, you can also pass the slot name via the spread operator. This is possible, because the slot name argument is actually a shortcut for a <code>name</code> keyword argument.</p> <p>So this:</p> <pre><code>{% slot \"content\" / %}\n</code></pre> <p>is the same as:</p> <pre><code>{% slot name=\"content\" / %}\n</code></pre> <p>So it's possible to define a <code>name</code> key on a dictionary, and then spread that onto the slot tag:</p> <pre><code>{# slot_props = {\"name\": \"content\"} #}\n{% slot ...slot_props / %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#pass-through-all-the-slots","title":"Pass through all the slots","text":"<p>You can dynamically pass all slots to a child component. This is similar to passing all slots in Vue:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"slots\": self.input.slots,\n        }\n\n    template = \"\"\"\n    &lt;div&gt;\n      {% component \"child\" %}\n        {% for slot_name in slots %}\n          {% fill name=slot_name data=\"data\" %}\n            {% slot name=slot_name ...data / %}\n          {% endfill %}\n        {% endfor %}\n      {% endcomponent %}\n    &lt;/div&gt;\n    \"\"\"\n</code></pre>"},{"location":"concepts/fundamentals/subclassing_components/","title":"Subclassing components","text":"<p>In larger projects, you might need to write multiple components with similar behavior. In such cases, you can extract shared behavior into a standalone component class to keep things DRY.</p> <p>When subclassing a component, there's a couple of things to keep in mind:</p>"},{"location":"concepts/fundamentals/subclassing_components/#template-js-and-css-inheritance","title":"Template, JS, and CSS Inheritance","text":"<p>When it comes to the pairs:</p> <ul> <li><code>Component.template</code>/<code>Component.template_file</code></li> <li><code>Component.js</code>/<code>Component.js_file</code></li> <li><code>Component.css</code>/<code>Component.css_file</code></li> </ul> <p>inheritance follows these rules:</p> <ul> <li>If a child component class defines either member of a pair (e.g., either <code>template</code> or <code>template_file</code>), it takes precedence and the parent's definition is ignored completely.</li> <li>For example, if a child component defines <code>template_file</code>, the parent's <code>template</code> or <code>template_file</code> will be ignored.</li> <li>This applies independently to each pair - you can inherit the JS while overriding the template, for instance.</li> </ul> <p>For example:</p> <pre><code>class BaseCard(Component):\n    template = \"\"\"\n        &lt;div class=\"card\"&gt;\n            &lt;div class=\"card-content\"&gt;{{ content }}&lt;/div&gt;\n        &lt;/div&gt;\n    \"\"\"\n    css = \"\"\"\n        .card {\n            border: 1px solid gray;\n        }\n    \"\"\"\n    js = \"\"\"console.log('Base card loaded');\"\"\"\n\n# This class overrides parent's template, but inherits CSS and JS\nclass SpecialCard(BaseCard):\n    template = \"\"\"\n        &lt;div class=\"card special\"&gt;\n            &lt;div class=\"card-content\"&gt;\u2728 {{ content }} \u2728&lt;/div&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n# This class overrides parent's template and CSS, but inherits JS\nclass CustomCard(BaseCard):\n    template_file = \"custom_card.html\"\n    css = \"\"\"\n        .card {\n            border: 2px solid gold;\n        }\n    \"\"\"\n</code></pre>"},{"location":"concepts/fundamentals/subclassing_components/#media-class-inheritance","title":"Media Class Inheritance","text":"<p>The <code>Component.Media</code> nested class follows Django's media inheritance rules:</p> <ul> <li>If both parent and child define a <code>Media</code> class, the child's media will automatically include both its own and the parent's JS and CSS files.</li> <li>This behavior can be configured using the <code>extend</code> attribute in the Media class, similar to Django's forms.   Read more on this in Controlling Media Inheritance.</li> </ul> <p>For example:</p> <pre><code>class BaseModal(Component):\n    template = \"&lt;div&gt;Modal content&lt;/div&gt;\"\n\n    class Media:\n        css = [\"base_modal.css\"]\n        js = [\"base_modal.js\"]  # Contains core modal functionality\n\nclass FancyModal(BaseModal):\n    class Media:\n        # Will include both base_modal.css/js AND fancy_modal.css/js\n        css = [\"fancy_modal.css\"]  # Additional styling\n        js = [\"fancy_modal.js\"]    # Additional animations\n\nclass SimpleModal(BaseModal):\n    class Media:\n        extend = False  # Don't inherit parent's media\n        css = [\"simple_modal.css\"]  # Only this CSS will be included\n        js = [\"simple_modal.js\"]    # Only this JS will be included\n</code></pre>"},{"location":"concepts/fundamentals/subclassing_components/#regular-python-inheritance","title":"Regular Python Inheritance","text":"<p>All other attributes and methods (including the <code>Component.View</code> class and its methods) follow standard Python inheritance rules.</p> <p>For example:</p> <pre><code>class BaseForm(Component):\n    template = \"\"\"\n        &lt;form&gt;\n            {{ form_content }}\n            &lt;button type=\"submit\"&gt;\n                {{ submit_text }}\n            &lt;/button&gt;\n        &lt;/form&gt;\n    \"\"\"\n\n    def get_context_data(self, **kwargs):\n        return {\n            \"form_content\": self.get_form_content(),\n            \"submit_text\": \"Submit\"\n        }\n\n    def get_form_content(self):\n        return \"&lt;input type='text' name='data'&gt;\"\n\nclass ContactForm(BaseForm):\n    # Extend parent's \"context\"\n    # but override \"submit_text\"\n    def get_context_data(self, **kwargs):\n        context = super().get_context_data(**kwargs)\n        context[\"submit_text\"] = \"Send Message\"  \n        return context\n\n    # Completely override parent's get_form_content\n    def get_form_content(self):\n        return \"\"\"\n            &lt;input type='text' name='name' placeholder='Your Name'&gt;\n            &lt;input type='email' name='email' placeholder='Your Email'&gt;\n            &lt;textarea name='message' placeholder='Your Message'&gt;&lt;/textarea&gt;\n        \"\"\"\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/","title":"Template tag syntax","text":"<p>All template tags in django_component, like <code>{% component %}</code> or <code>{% slot %}</code>, and so on, support extra syntax that makes it possible to write components like in Vue or React (JSX).</p>"},{"location":"concepts/fundamentals/template_tag_syntax/#self-closing-tags","title":"Self-closing tags","text":"<p>When you have a tag like <code>{% component %}</code> or <code>{% slot %}</code>, but it has no content, you can simply append a forward slash <code>/</code> at the end, instead of writing out the closing tags like <code>{% endcomponent %}</code> or <code>{% endslot %}</code>:</p> <p>So this:</p> <pre><code>{% component \"button\" %}{% endcomponent %}\n</code></pre> <p>becomes</p> <pre><code>{% component \"button\" / %}\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/#special-characters","title":"Special characters","text":"<p>New in version 0.71:</p> <p>Keyword arguments can contain special characters <code># @ . - _</code>, so keywords like so are still valid:</p> <pre><code>&lt;body&gt;\n    {% component \"calendar\" my-date=\"2015-06-19\" @click.native=do_something #some_id=True / %}\n&lt;/body&gt;\n</code></pre> <p>These can then be accessed inside <code>get_context_data</code> so:</p> <pre><code>@register(\"calendar\")\nclass Calendar(Component):\n    # Since # . @ - are not valid identifiers, we have to\n    # use `**kwargs` so the method can accept these args.\n    def get_context_data(self, **kwargs):\n        return {\n            \"date\": kwargs[\"my-date\"],\n            \"id\": kwargs[\"#some_id\"],\n            \"on_click\": kwargs[\"@click.native\"]\n        }\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/#spread-operator","title":"Spread operator","text":"<p>New in version 0.93:</p> <p>Instead of passing keyword arguments one-by-one:</p> <pre><code>{% component \"calendar\" title=\"How to abc\" date=\"2015-06-19\" author=\"John Wick\" / %}\n</code></pre> <p>You can use a spread operator <code>...dict</code> to apply key-value pairs from a dictionary:</p> <pre><code>post_data = {\n    \"title\": \"How to...\",\n    \"date\": \"2015-06-19\",\n    \"author\": \"John Wick\",\n}\n</code></pre> <pre><code>{% component \"calendar\" ...post_data / %}\n</code></pre> <p>This behaves similar to JSX's spread operator or Vue's <code>v-bind</code>.</p> <p>Spread operators are treated as keyword arguments, which means that:</p> <ol> <li>Spread operators must come after positional arguments.</li> <li>You cannot use spread operators for positional-only arguments.</li> </ol> <p>Other than that, you can use spread operators multiple times, and even put keyword arguments in-between or after them:</p> <pre><code>{% component \"calendar\" ...post_data id=post.id ...extra / %}\n</code></pre> <p>In a case of conflicts, the values added later (right-most) overwrite previous values.</p>"},{"location":"concepts/fundamentals/template_tag_syntax/#use-template-tags-inside-component-inputs","title":"Use template tags inside component inputs","text":"<p>New in version 0.93</p> <p>When passing data around, sometimes you may need to do light transformations, like negating booleans or filtering lists.</p> <p>Normally, what you would have to do is to define ALL the variables inside <code>get_context_data()</code>. But this can get messy if your components contain a lot of logic.</p> <pre><code>@register(\"calendar\")\nclass Calendar(Component):\n    def get_context_data(self, id: str, editable: bool):\n        return {\n            \"editable\": editable,\n            \"readonly\": not editable,\n            \"input_id\": f\"input-{id}\",\n            \"icon_id\": f\"icon-{id}\",\n            ...\n        }\n</code></pre> <p>Instead, template tags in django_components (<code>{% component %}</code>, <code>{% slot %}</code>, <code>{% provide %}</code>, etc) allow you to treat literal string values as templates:</p> <pre><code>{% component 'blog_post'\n  \"As positional arg {# yay #}\"\n  title=\"{{ person.first_name }} {{ person.last_name }}\"\n  id=\"{% random_int 10 20 %}\"\n  readonly=\"{{ editable|not }}\"\n  author=\"John Wick {# TODO: parametrize #}\"\n/ %}\n</code></pre> <p>In the example above:</p> <ul> <li>Component <code>test</code> receives a positional argument with value <code>\"As positional arg \"</code>. The comment is omitted.</li> <li>Kwarg <code>title</code> is passed as a string, e.g. <code>John Doe</code></li> <li>Kwarg <code>id</code> is passed as <code>int</code>, e.g. <code>15</code></li> <li>Kwarg <code>readonly</code> is passed as <code>bool</code>, e.g. <code>False</code></li> <li>Kwarg <code>author</code> is passed as a string, e.g. <code>John Wick</code> (Comment omitted)</li> </ul> <p>This is inspired by django-cotton.</p>"},{"location":"concepts/fundamentals/template_tag_syntax/#passing-data-as-string-vs-original-values","title":"Passing data as string vs original values","text":"<p>Sometimes you may want to use the template tags to transform or generate the data that is then passed to the component.</p> <p>The data doesn't necessarily have to be strings. In the example above, the kwarg <code>id</code> was passed as an integer, NOT a string.</p> <p>Although the string literals for components inputs are treated as regular Django templates, there is one special case:</p> <p>When the string literal contains only a single template tag, with no extra text, then the value is passed as the original type instead of a string.</p> <p>Here, <code>page</code> is an integer:</p> <pre><code>{% component 'blog_post' page=\"{% random_int 10 20 %}\" / %}\n</code></pre> <p>Here, <code>page</code> is a string:</p> <pre><code>{% component 'blog_post' page=\" {% random_int 10 20 %} \" / %}\n</code></pre> <p>And same applies to the <code>{{ }}</code> variable tags:</p> <p>Here, <code>items</code> is a list:</p> <pre><code>{% component 'cat_list' items=\"{{ cats|slice:':2' }}\" / %}\n</code></pre> <p>Here, <code>items</code> is a string:</p> <pre><code>{% component 'cat_list' items=\"{{ cats|slice:':2' }} See more\" / %}\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/#evaluating-python-expressions-in-template","title":"Evaluating Python expressions in template","text":"<p>You can even go a step further and have a similar experience to Vue or React, where you can evaluate arbitrary code expressions:</p> <pre><code>&lt;MyForm value={isEnabled ? inputValue : null} /&gt;\n</code></pre> <p>Similar is possible with <code>django-expr</code>, which adds an <code>expr</code> tag and filter that you can use to evaluate Python expressions from within the template:</p> <pre><code>{% component \"my_form\"\n  value=\"{% expr 'input_value if is_enabled else None' %}\"\n/ %}\n</code></pre> <p>Note: Never use this feature to mix business logic and template logic. Business logic should still be in the view!</p>"},{"location":"concepts/fundamentals/template_tag_syntax/#pass-dictonary-by-its-key-value-pairs","title":"Pass dictonary by its key-value pairs","text":"<p>New in version 0.74:</p> <p>Sometimes, a component may expect a dictionary as one of its inputs.</p> <p>Most commonly, this happens when a component accepts a dictionary of HTML attributes (usually called <code>attrs</code>) to pass to the underlying template.</p> <p>In such cases, we may want to define some HTML attributes statically, and other dynamically. But for that, we need to define this dictionary on Python side:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        {% component \"other\" attrs=attrs / %}\n    \"\"\"\n\n    def get_context_data(self, some_id: str):\n        attrs = {\n            \"class\": \"pa-4 flex\",\n            \"data-some-id\": some_id,\n            \"@click.stop\": \"onClickHandler\",\n        }\n        return {\"attrs\": attrs}\n</code></pre> <p>But as you can see in the case above, the event handler <code>@click.stop</code> and styling <code>pa-4 flex</code> are disconnected from the template. If the component grew in size and we moved the HTML to a separate file, we would have hard time reasoning about the component's template.</p> <p>Luckily, there's a better way.</p> <p>When we want to pass a dictionary to a component, we can define individual key-value pairs as component kwargs, so we can keep all the relevant information in the template. For that, we prefix the key with the name of the dict and <code>:</code>. So key <code>class</code> of input <code>attrs</code> becomes <code>attrs:class</code>. And our example becomes:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        {% component \"other\"\n            attrs:class=\"pa-4 flex\"\n            attrs:data-some-id=some_id\n            attrs:@click.stop=\"onClickHandler\"\n        / %}\n    \"\"\"\n\n    def get_context_data(self, some_id: str):\n        return {\"some_id\": some_id}\n</code></pre> <p>Sweet! Now all the relevant HTML is inside the template, and we can move it to a separate file with confidence:</p> <pre><code>{% component \"other\"\n    attrs:class=\"pa-4 flex\"\n    attrs:data-some-id=some_id\n    attrs:@click.stop=\"onClickHandler\"\n/ %}\n</code></pre> <p>Note: It is NOT possible to define nested dictionaries, so <code>attrs:my_key:two=2</code> would be interpreted as:</p> <pre><code>{\"attrs\": {\"my_key:two\": 2}}\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/#multiline-tags","title":"Multiline tags","text":"<p>By default, Django expects a template tag to be defined on a single line.</p> <p>However, this can become unwieldy if you have a component with a lot of inputs:</p> <pre><code>{% component \"card\" title=\"Joanne Arc\" subtitle=\"Head of Kitty Relations\" date_last_active=\"2024-09-03\" ... %}\n</code></pre> <p>Instead, when you install django_components, it automatically configures Django to suport multi-line tags.</p> <p>So we can rewrite the above as:</p> <pre><code>{% component \"card\"\n    title=\"Joanne Arc\"\n    subtitle=\"Head of Kitty Relations\"\n    date_last_active=\"2024-09-03\"\n    ...\n%}\n</code></pre> <p>Much better!</p> <p>To disable this behavior, set <code>COMPONENTS.multiline_tag</code> to <code>False</code></p>"},{"location":"getting_started/adding_js_and_css/","title":"Adding JS and CSS","text":"<p>Next we will add CSS and JavaScript to our template.</p> <p>Info</p> <p>In django-components, using JS and CSS is as simple as defining them on the Component class. You don't have to insert the <code>&lt;script&gt;</code> and <code>&lt;link&gt;</code> tags into the HTML manually.</p> <p>Behind the scenes, django-components keeps track of which components use which JS and CSS files. Thus, when a component is rendered on the page, the page will contain only the JS and CSS used by the components, and nothing more!</p>"},{"location":"getting_started/adding_js_and_css/#1-update-project-structure","title":"1. Update project structure","text":"<p>Start by creating empty <code>calendar.js</code> and <code>calendar.css</code> files:</p> <pre><code>sampleproject/\n\u251c\u2500\u2500 calendarapp/\n\u251c\u2500\u2500 components/\n\u2502   \u2514\u2500\u2500 calendar/\n\u2502       \u251c\u2500\u2500 calendar.py\n\u2502       \u251c\u2500\u2500 calendar.js       \ud83c\udd95\n\u2502       \u251c\u2500\u2500 calendar.css      \ud83c\udd95\n\u2502       \u2514\u2500\u2500 calendar.html\n\u251c\u2500\u2500 sampleproject/\n\u251c\u2500\u2500 manage.py\n\u2514\u2500\u2500 requirements.txt\n</code></pre>"},{"location":"getting_started/adding_js_and_css/#2-write-css","title":"2. Write CSS","text":"<p>Inside <code>calendar.css</code>, write:</p> [project root]/components/calendar/calendar.css<pre><code>.calendar {\n  width: 200px;\n  background: pink;\n}\n.calendar span {\n  font-weight: bold;\n}\n</code></pre> <p>Be sure to prefix your rules with unique CSS class like <code>calendar</code>, so the CSS doesn't clash with other rules.</p> <p>Note</p> <p>Soon, django-components will automatically scope your CSS by default, so you won't have to worry about CSS class clashes.</p> <p>This CSS will be inserted into the page as an inlined <code>&lt;style&gt;</code> tag, at the position defined by <code>{% component_css_dependencies %}</code>, or at the end of the inside the <code>&lt;head&gt;</code> tag (See JS and CSS output locations).</p> <p>So in your HTML, you may see something like this:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n    &lt;style&gt;\n      .calendar {\n        width: 200px;\n        background: pink;\n      }\n      .calendar span {\n        font-weight: bold;\n      }\n    &lt;/style&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    ...\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre>"},{"location":"getting_started/adding_js_and_css/#3-write-js","title":"3. Write JS","text":"<p>Next we write a JavaScript file that specifies how to interact with this component.</p> <p>You are free to use any javascript framework you want.</p> [project root]/components/calendar/calendar.js<pre><code>(function () {\n  document.querySelector(\".calendar\").onclick = () =&gt; {\n    alert(\"Clicked calendar!\");\n  };\n})();\n</code></pre> <p>A good way to make sure the JS of this component doesn't clash with other components is to define all JS code inside an anonymous self-invoking function (<code>(() =&gt; { ... })()</code>). This makes all variables defined only be defined inside this component and not affect other components.</p> <p>Note</p> <p>Soon, django-components will automatically wrap your JS in a self-invoking function by default (except for JS defined with <code>&lt;script type=\"module\"&gt;</code>).</p> <p>Similarly to CSS, JS will be inserted into the page as an inlined <code>&lt;script&gt;</code> tag, at the position defined by <code>{% component_js_dependencies %}</code>, or at the end of the inside the <code>&lt;body&gt;</code> tag (See JS and CSS output locations).</p> <p>So in your HTML, you may see something like this:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n  &lt;/head&gt;\n  &lt;body&gt;\n    ...\n    &lt;script&gt;\n      (function () {\n        document.querySelector(\".calendar\").onclick = () =&gt; {\n          alert(\"Clicked calendar!\");\n        };\n      })();\n    &lt;/script&gt;\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre>"},{"location":"getting_started/adding_js_and_css/#rules-of-js-execution","title":"Rules of JS execution","text":"<ol> <li> <p>JS is executed in the order in which the components are found in the HTML</p> <p>By default, the JS is inserted as a synchronous script (<code>&lt;script&gt; ... &lt;/script&gt;</code>)</p> <p>So if you define multiple components on the same page, their JS will be executed in the order in which the components are found in the HTML.</p> <p>So if we have a template like so:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component \"calendar\" / %}\n    {% component \"table\" / %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre> <p>Then the JS file of the component <code>calendar</code> will be executed first, and the JS file of component <code>table</code> will be executed second.</p> </li> <li> <p>JS will be executed only once, even if there is multiple instances of the same component</p> <p>In this case, the JS of <code>calendar</code> will STILL execute first (because it was found first), and will STILL execute only once, even though it's present twice:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component \"calendar\" / %}\n    {% component \"table\" / %}\n    {% component \"calendar\" / %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre> </li> </ol>"},{"location":"getting_started/adding_js_and_css/#4-link-js-and-css-to-a-component","title":"4. Link JS and CSS to a component","text":"<p>Finally, we return to our Python component in <code>calendar.py</code> to tie this together.</p> <p>To link JS and CSS defined in other files, use <code>js_file</code> and <code>css_file</code> attributes:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"   # &lt;--- new\n    css_file = \"calendar.css\"   # &lt;--- new\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>And that's it! If you were to embed this component in an HTML, django-components will automatically embed the associated JS and CSS.</p> <p>Note</p> <p>Similarly to the template file, the JS and CSS file paths can be either:</p> <ol> <li>Relative to the Python component file (as seen above),</li> <li>Relative to any of the component directories as defined by <code>COMPONENTS.dirs</code> and/or <code>COMPONENTS.app_dirs</code> (e.g. <code>[your apps]/components</code> dir and <code>[project root]/components</code>)</li> <li>Relative to any of the directories defined by <code>STATICFILES_DIRS</code>.</li> </ol>"},{"location":"getting_started/adding_js_and_css/#5-link-additional-js-and-css-to-a-component","title":"5. Link additional JS and CSS to a component","text":"<p>Your components may depend on third-party packages or styling, or other shared logic. To load these additional dependencies, you can use a nested <code>Media</code> class.</p> <p>This <code>Media</code> class behaves similarly to Django's Media class, with a few differences:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list, or (CSS-only) a dictonary (see below).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>, <code>SafeString</code>, or a function.</li> <li>If you set <code>Media.extend</code> to a list, it should be a list of <code>Component</code> classes.</li> </ol> <p>Learn more about using Media.</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    class Media:   # &lt;--- new\n        js = [\n            \"path/to/shared.js\",\n            \"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\",  # AlpineJS\n        ]\n        css = [\n            \"path/to/shared.css\",\n            \"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\",  # Tailwind\n        ]\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>Note</p> <p>Same as with the \"primary\" JS and CSS, the file paths files can be either:</p> <ol> <li>Relative to the Python component file (as seen above),</li> <li>Relative to any of the component directories as defined by <code>COMPONENTS.dirs</code> and/or <code>COMPONENTS.app_dirs</code> (e.g. <code>[your apps]/components</code> dir and <code>[project root]/components</code>)</li> </ol> <p>Info</p> <p>The <code>Media</code> nested class is shaped based on Django's Media class.</p> <p>As such, django-components allows multiple formats to define the nested Media class:</p> <pre><code># Single files\nclass Media:\n    js = \"calendar.js\"\n    css = \"calendar.css\"\n\n# Lists of files\nclass Media:\n    js = [\"calendar.js\", \"calendar2.js\"]\n    css = [\"calendar.css\", \"calendar2.css\"]\n\n# Dictionary of media types for CSS\nclass Media:\n    js = [\"calendar.js\", \"calendar2.js\"]\n    css = {\n      \"all\": [\"calendar.css\", \"calendar2.css\"],\n    }\n</code></pre> <p>If you define a list of JS files, they will be executed one-by-one, left-to-right.</p>"},{"location":"getting_started/adding_js_and_css/#rules-of-execution-of-scripts-in-mediajs","title":"Rules of execution of scripts in <code>Media.js</code>","text":"<p>The scripts defined in <code>Media.js</code> still follow the rules outlined above:</p> <ol> <li>JS is executed in the order in which the components are found in the HTML.</li> <li>JS will be executed only once, even if there is multiple instances of the same component.</li> </ol> <p>Additionally to <code>Media.js</code> applies that:</p> <ol> <li>JS in <code>Media.js</code> is executed before the component's primary JS.</li> <li>JS in <code>Media.js</code> is executed in the same order as it was defined.</li> <li>If there is multiple components that specify the same JS path or URL in <code>Media.js</code>,    this JS will be still loaded and executed only once.</li> </ol> <p>Putting all of this together, our <code>Calendar</code> component above would render HTML like so:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n    &lt;!-- CSS from Media.css --&gt;\n    &lt;link href=\"/static/path/to/shared.css\" media=\"all\" rel=\"stylesheet\" /&gt;\n    &lt;link\n      href=\"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\"\n      media=\"all\"\n      rel=\"stylesheet\"\n    /&gt;\n    &lt;!-- CSS from Component.css_file --&gt;\n    &lt;style&gt;\n      .calendar {\n        width: 200px;\n        background: pink;\n      }\n      .calendar span {\n        font-weight: bold;\n      }\n    &lt;/style&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    ...\n    &lt;!-- JS from Media.js --&gt;\n    &lt;script src=\"/static/path/to/shared.js\"&gt;&lt;/script&gt;\n    &lt;script src=\"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\"&gt;&lt;/script&gt;\n    &lt;!-- JS from Component.js_file --&gt;\n    &lt;script&gt;\n      (function () {\n        document.querySelector(\".calendar\").onclick = () =&gt; {\n          alert(\"Clicked calendar!\");\n        };\n      })();\n    &lt;/script&gt;\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre> <p>Now that we have a fully-defined component, next let's use it in a Django template \u27a1\ufe0f.</p>"},{"location":"getting_started/adding_slots/","title":"Adding slots","text":"<p>Our calendar component's looking great! But we just got a new assignment from our colleague - The calendar date needs to be shown on 3 different pages:</p> <ol> <li>On one page, it needs to be shown as is</li> <li>On the second, the date needs to be bold</li> <li>On the third, the date needs to be in italics</li> </ol> <p>As a reminder, this is what the component's template looks like:</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>There's many ways we could approach this:</p> <ul> <li>Expose the date in a slot</li> <li>Style <code>.calendar &gt; span</code> differently on different pages</li> <li>Pass a variable to the component that decides how the date is rendered</li> <li>Create a new component</li> </ul> <p>First two options are more flexible, because the custom styling is not baked into a component's implementation. And for the sake of demonstration, we'll solve this challenge with slots.</p>"},{"location":"getting_started/adding_slots/#1-what-are-slots","title":"1. What are slots","text":"<p>Components support something called Slots.</p> <p>When a component is used inside another template, slots allow the parent template to override specific parts of the child component by passing in different content.</p> <p>This mechanism makes components more reusable and composable.</p> <p>This behavior is similar to slots in Vue.</p> <p>In the example below we introduce two tags that work hand in hand to make this work. These are...</p> <ul> <li><code>{% slot &lt;name&gt; %}</code>/<code>{% endslot %}</code>: Declares a new slot in the component template.</li> <li><code>{% fill &lt;name&gt; %}</code>/<code>{% endfill %}</code>: (Used inside a <code>{% component %}</code>   tag pair.) Fills a declared slot with the specified content.</li> </ul>"},{"location":"getting_started/adding_slots/#2-add-a-slot-tag","title":"2. Add a slot tag","text":"<p>Let's update our calendar component to support more customization. We'll add <code>{% slot %}</code> tag to the template:</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is\n  {% slot \"date\" default %}  {# &lt;--- new #}\n    &lt;span&gt;{{ date }}&lt;/span&gt;\n  {% endslot %}\n&lt;/div&gt;\n</code></pre> <p>Notice that:</p> <ol> <li> <p>We named the slot <code>date</code> - so we can fill this slot by using <code>{% fill \"date\" %}</code></p> </li> <li> <p>We also made it the default slot.</p> </li> <li> <p>We placed our original implementation inside the <code>{% slot %}</code>    tag - this is what will be rendered when the slot is NOT overriden.</p> </li> </ol>"},{"location":"getting_started/adding_slots/#3-add-fill-tag","title":"3. Add fill tag","text":"<p>Now we can use <code>{% fill %}</code> tags inside the <code>{% component %}</code> tags to override the <code>date</code> slot to generate the bold and italics variants:</p> <pre><code>{# Default #}\n{% component \"calendar\" date=\"2024-12-13\" / %}\n\n{# Bold #}\n{% component \"calendar\" date=\"2024-12-13\" %}\n  &lt;b&gt; 2024-12-13 &lt;/b&gt;\n{% endcomponent %}\n\n{# Italics #}\n{% component \"calendar\" date=\"2024-12-13\" %}\n  &lt;i&gt; 2024-12-13 &lt;/i&gt;\n{% endcomponent %}\n</code></pre> <p>Which will render as:</p> <pre><code>&lt;!-- Default --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;2024-12-13&lt;/span&gt;\n&lt;/div&gt;\n\n&lt;!-- Bold --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;b&gt;2024-12-13&lt;/b&gt;\n&lt;/div&gt;\n\n&lt;!-- Italics --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;i&gt;2024-12-13&lt;/i&gt;\n&lt;/div&gt;\n</code></pre> <p>Info</p> <p>Since we used the <code>default</code> flag on <code>{% slot \"date\" %}</code> inside our calendar component, we can target the <code>date</code> component in multiple ways:</p> <ol> <li> <p>Explicitly by it's name     <pre><code>{% component \"calendar\" date=\"2024-12-13\" %}\n  {% fill \"date\" %}\n    &lt;i&gt; 2024-12-13 &lt;/i&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre></p> </li> <li> <p>Implicitly as the default slot (Omitting the     <code>{% fill %}</code> tag)     <pre><code>{% component \"calendar\" date=\"2024-12-13\" %}\n  &lt;i&gt; 2024-12-13 &lt;/i&gt;\n{% endcomponent %}\n</code></pre></p> </li> <li> <p>Explicitly as the default slot (Setting fill name to <code>default</code>)     <pre><code>{% component \"calendar\" date=\"2024-12-13\" %}\n  {% fill \"default\" %}\n    &lt;i&gt; 2024-12-13 &lt;/i&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre></p> </li> </ol>"},{"location":"getting_started/adding_slots/#5-wait-theres-a-bug","title":"5. Wait, there's a bug","text":"<p>There is a mistake in our code! <code>2024-12-13</code> is Friday, so that's fine. But if we updated the to <code>2024-12-14</code>, which is Saturday, our template from previous step would render this:</p> <pre><code>&lt;!-- Default --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;2024-12-16&lt;/span&gt;\n&lt;/div&gt;\n\n&lt;!-- Bold --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;b&gt;2024-12-14&lt;/b&gt;\n&lt;/div&gt;\n\n&lt;!-- Italics --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;i&gt;2024-12-14&lt;/i&gt;\n&lt;/div&gt;\n</code></pre> <p>The first instance rendered <code>2024-12-16</code>, while the rest rendered <code>2024-12-14</code>!</p> <p>Why? Remember that in the <code>get_context_data()</code> method of our Calendar component, we pre-process the date. If the date falls on Saturday or Sunday, we shift it to next Monday:</p> [project root]/components/calendar/calendar.py<pre><code>from datetime import date\n\nfrom django_components import Component, register\n\n# If date is Sat or Sun, shift it to next Mon, so the date is always workweek.\ndef to_workweek_date(d: date):\n    ...\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    ...\n    def get_context_data(self, date: date, extra_class: str | None = None):\n        workweek_date = to_workweek_date(date)\n        return {\n            \"date\": workweek_date,\n            \"extra_class\": extra_class,\n        }\n</code></pre> <p>And the issue is that in our template, we used the <code>date</code> value that we used as input, which is NOT the same as the <code>date</code> variable used inside Calendar's template.</p>"},{"location":"getting_started/adding_slots/#5-adding-data-to-slots","title":"5. Adding data to slots","text":"<p>We want to use the same <code>date</code> variable that's used inside Calendar's template.</p> <p>Luckily, django-components allows passing data to the slot, also known as Scoped slots.</p> <p>This consists of two steps:</p> <ol> <li>Pass the <code>date</code> variable to the <code>{% slot %}</code> tag</li> <li>Access the <code>date</code> variable in the <code>{% fill %}</code>    tag by using the special <code>data</code> kwarg</li> </ol> <p>Let's update the Calendar's template:</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is\n  {% slot \"date\" default date=date %}  {# &lt;--- changed #}\n    &lt;span&gt;{{ date }}&lt;/span&gt;\n  {% endslot %}\n&lt;/div&gt;\n</code></pre> <p>Info</p> <p>The <code>{% slot %}</code> tag has one special kwarg, <code>name</code>. When you write</p> <pre><code>{% slot \"date\" / %}\n</code></pre> <p>It's the same as:</p> <pre><code>{% slot name=\"date\" / %}\n</code></pre> <p>Other than the <code>name</code> kwarg, you can pass any extra kwargs to the <code>{% slot %}</code> tag, and these will be exposed as the slot's data.</p> <pre><code>{% slot name=\"date\" kwarg1=123 kwarg2=\"text\" kwarg3=my_var / %}\n</code></pre>"},{"location":"getting_started/adding_slots/#6-accessing-slot-data-in-fills","title":"6. Accessing slot data in fills","text":"<p>Now, on the <code>{% fill %}</code> tags, we can use the <code>data</code> kwarg to specify the variable under which the slot data will be available.</p> <p>The variable from the <code>data</code> kwarg contains all the extra kwargs passed to the <code>{% slot %}</code> tag.</p> <p>So if we set <code>data=\"slot_data\"</code>, then we can access the date variable under <code>slot_data.date</code>:</p> <pre><code>{# Default #}\n{% component \"calendar\" date=\"2024-12-13\" / %}\n\n{# Bold #}\n{% component \"calendar\" date=\"2024-12-13\" %}\n  {% fill \"date\" data=\"slot_data\" %}\n    &lt;b&gt; {{ slot_data.date }} &lt;/b&gt;\n  {% endfill %}\n{% endcomponent %}\n\n{# Italics #}\n{% component \"calendar\" date=\"2024-12-13\" %}\n  {% fill \"date\" data=\"slot_data\" %}\n    &lt;i&gt; {{ slot_data.date }} &lt;/i&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <p>By using the <code>date</code> variable from the slot, we'll render the correct date each time:</p> <pre><code>&lt;!-- Default --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;2024-12-16&lt;/span&gt;\n&lt;/div&gt;\n\n&lt;!-- Bold --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;b&gt;2024-12-16&lt;/b&gt;\n&lt;/div&gt;\n\n&lt;!-- Italics --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;i&gt;2024-12-16&lt;/i&gt;\n&lt;/div&gt;\n</code></pre> <p>Info</p> <p>When to use slots vs variables?</p> <p>Generally, slots are more flexible - you can access the slot data, even the original slot content. Thus, slots behave more like functions that render content based on their context.</p> <p>On the other hand, variables are static - the variable you pass to a component is what will be used.</p> <p>Moreover, slots are treated as part of the template - for example the CSS scoping (work in progress) is applied to the slot content too.</p>"},{"location":"getting_started/components_in_templates/","title":"Components in templates","text":"<p>By the end of this section, we want to be able to use our components in Django templates like so:</p> <pre><code>{% load component_tags %}\n&lt;!DOCTYPE html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    &lt;title&gt;My example calendar&lt;/title&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component \"calendar\" / %}\n  &lt;/body&gt;\n&lt;html&gt;\n</code></pre>"},{"location":"getting_started/components_in_templates/#1-register-component","title":"1. Register component","text":"<p>First, however, we need to register our component class with <code>ComponentRegistry</code>.</p> <p>To register a component with a <code>ComponentRegistry</code>, we will use the <code>@register</code> decorator, and give it a name under which the component will be accessible from within the template:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register  # &lt;--- new\n\n@register(\"calendar\")  # &lt;--- new\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>This will register the component to the default registry. Default registry is loaded into the template by calling <code>{% load component_tags %}</code> inside the template.</p> <p>Info</p> <p>Why do we have to register components?</p> <p>We want to use our component as a template tag (<code>{% ... %}</code>) in Django template.</p> <p>In Django, template tags are managed by the <code>Library</code> instances. Whenever you include <code>{% load xxx %}</code> in your template, you are loading a <code>Library</code> instance into your template.</p> <p><code>ComponentRegistry</code> acts like a router and connects the registered components with the associated <code>Library</code>.</p> <p>That way, when you include <code>{% load component_tags %}</code> in your template, you are able to \"call\" components like <code>{% component \"calendar\" / %}</code>.</p> <p><code>ComponentRegistries</code> also make it possible to group and share components as standalone packages. Learn more here.</p> <p>Note</p> <p>You can create custom <code>ComponentRegistry</code> instances, which will use different <code>Library</code> instances. In that case you will have to load different libraries depending on which components you want to use:</p> <p>Example 1 - Using component defined in the default registry <pre><code>{% load component_tags %}\n&lt;div&gt;\n  {% component \"calendar\" / %}\n&lt;/div&gt;\n</code></pre></p> <p>Example 2 - Using component defined in a custom registry <pre><code>{% load my_custom_tags %}\n&lt;div&gt;\n  {% my_component \"table\" / %}\n&lt;/div&gt;\n</code></pre></p> <p>Note that, because the tag name <code>component</code> is use by the default ComponentRegistry, the custom registry was configured to use the tag <code>my_component</code> instead. Read more here</p>"},{"location":"getting_started/components_in_templates/#2-load-and-use-the-component-in-template","title":"2. Load and use the component in template","text":"<p>The component is now registered under the name <code>calendar</code>. All that remains to do is to load and render the component inside a template:</p> <pre><code>{% load component_tags %}  {# Load the default registry #}\n&lt;!DOCTYPE html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    &lt;title&gt;My example calendar&lt;/title&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component \"calendar\" / %}  {# Render the component #}\n  &lt;/body&gt;\n&lt;html&gt;\n</code></pre> <p>Info</p> <p>Component tags should end with <code>/</code> if they do not contain any Slot fills. But you can also use <code>{% endcomponent %}</code> instead:</p> <pre><code>{% component \"calendar\" %}{% endcomponent %}\n</code></pre> <p>We defined the Calendar's template as</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>and the variable <code>date</code> as <code>\"1970-01-01\"</code>.</p> <p>Thus, the final output will look something like this:</p> <pre><code>&lt;!DOCTYPE html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    &lt;title&gt;My example calendar&lt;/title&gt;\n    &lt;style&gt;\n      .calendar {\n        width: 200px;\n        background: pink;\n      }\n      .calendar span {\n        font-weight: bold;\n      }\n    &lt;/style&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    &lt;div class=\"calendar\"&gt;\n      Today's date is &lt;span&gt;1970-01-01&lt;/span&gt;\n    &lt;/div&gt;\n    &lt;script&gt;\n      (function () {\n        document.querySelector(\".calendar\").onclick = () =&gt; {\n          alert(\"Clicked calendar!\");\n        };\n      })();\n    &lt;/script&gt;\n  &lt;/body&gt;\n&lt;html&gt;\n</code></pre> <p>This makes it possible to organize your front-end around reusable components, instead of relying on template tags and keeping your CSS and Javascript in the static directory.</p> <p>Info</p> <p>Remember that you can use <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code> to change where the <code>&lt;script&gt;</code> and <code>&lt;style&gt;</code> tags will be rendered (See JS and CSS output locations).</p> <p>Info</p> <p>How does django-components pick up registered components?</p> <p>Notice that it was enough to add <code>@register</code> to the component. We didn't need to import the component file anywhere to execute it.</p> <p>This is because django-components automatically imports all Python files found in the component directories during an event called Autodiscovery.</p> <p>So with Autodiscovery, it's the same as if you manually imported the component files on the <code>ready()</code> hook:</p> <pre><code>class MyApp(AppConfig):\n    default_auto_field = \"django.db.models.BigAutoField\"\n    name = \"myapp\"\n\n    def ready(self):\n        import myapp.components.calendar\n        import myapp.components.table\n        ...\n</code></pre> <p>You can now render the components in templates!</p> <p>Currently our component always renders the same content. Let's parametrise it, so that our Calendar component is configurable from within the template \u27a1\ufe0f</p>"},{"location":"getting_started/parametrising_components/","title":"Parametrising components","text":"<p>So far, our Calendar component will always render the date <code>1970-01-01</code>. Let's make it more useful and flexible by being able to pass in custom date.</p> <p>What we want is to be able to use the Calendar component within the template like so:</p> <pre><code>{% component \"calendar\" date=\"2024-12-13\" extra_class=\"text-red\" / %}\n</code></pre>"},{"location":"getting_started/parametrising_components/#1-understading-component-inputs","title":"1. Understading component inputs","text":"<p>In section Create your first component, we defined the <code>get_context_data()</code> method that defines what variables will be available within the template:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    ...\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>What we didn't say is that <code>get_context_data()</code> actually receives the args and kwargs that were passed to a component.</p> <p>So if we call a component with a <code>date</code> and <code>extra_class</code> keywords:</p> <pre><code>{% component \"calendar\" date=\"2024-12-13\" extra_class=\"text-red\" / %}\n</code></pre> <p>This is the same as calling:</p> <pre><code>Calendar.get_context_data(date=\"2024-12-13\", extra_class=\"text-red\")\n</code></pre> <p>And same applies to positional arguments, or mixing args and kwargs, where:</p> <pre><code>{% component \"calendar\" \"2024-12-13\" extra_class=\"text-red\" / %}\n</code></pre> <p>is same as</p> <pre><code>Calendar.get_context_data(\"2024-12-13\", extra_class=\"text-red\")\n</code></pre>"},{"location":"getting_started/parametrising_components/#2-define-inputs-for-get_context_data","title":"2. Define inputs for <code>get_context_data</code>","text":"<p>Let's put this to test. We want to pass <code>date</code> and <code>extra_class</code> kwargs to the component. And so, we can write the <code>get_context_data()</code> method such that it expects those parameters:</p> [project root]/components/calendar/calendar.py<pre><code>from datetime import date\n\nfrom django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    ...\n    def get_context_data(self, date: date, extra_class: str | None = None):\n        return {\n            \"date\": date,\n            \"extra_class\": extra_class,\n        }\n</code></pre> <p>Info</p> <p>Since <code>get_context_data()</code> is just a regular Python function, type hints annotations work the same way as anywhere else.</p> <p>Warning</p> <p>Since <code>get_context_data()</code> is just a regular Python function, it will raise TypeError if it receives incorrect parameters.</p> <p>Since <code>extra_class</code> is optional in the function signature, it's optional also in the template. So both following calls are valid:</p> <pre><code>{% component \"calendar\" \"2024-12-13\" / %}\n{% component \"calendar\" \"2024-12-13\" extra_class=\"text-red\" / %}\n</code></pre> <p>However, <code>date</code> is required. Thus we MUST provide it. Same with regular Python functions, <code>date</code> can be set either as positional or keyword argument. But either way it MUST be set:</p> <pre><code>\u2705\n{% component \"calendar\" \"2024-12-13\" / %}\n{% component \"calendar\" extra_class=\"text-red\" date=\"2024-12-13\" / %}\n\n\u274c\n{% component \"calendar\" extra_class=\"text-red\" / %}\n</code></pre>"},{"location":"getting_started/parametrising_components/#3-process-inputs-in-get_context_data","title":"3. Process inputs in <code>get_context_data</code>","text":"<p>The <code>get_context_data()</code> method is powerful, because it allows us to decouple component inputs from the template variables. In other words, we can pre-process the component inputs, and massage them into a shape that's most appropriate for what the template needs. And it also allows us to pass in static data into the template.</p> <p>Imagine our component receives data from the database that looks like below (taken from Django).</p> <pre><code>cities = [\n    {\"name\": \"Mumbai\", \"population\": \"19,000,000\", \"country\": \"India\"},\n    {\"name\": \"Calcutta\", \"population\": \"15,000,000\", \"country\": \"India\"},\n    {\"name\": \"New York\", \"population\": \"20,000,000\", \"country\": \"USA\"},\n    {\"name\": \"Chicago\", \"population\": \"7,000,000\", \"country\": \"USA\"},\n    {\"name\": \"Tokyo\", \"population\": \"33,000,000\", \"country\": \"Japan\"},\n]\n</code></pre> <p>We need to group the list items by size into following buckets by population:</p> <ul> <li>0-10,000,000</li> <li>10,000,001-20,000,000</li> <li>20,000,001-30,000,000</li> <li>+30,000,001</li> </ul> <p>So we want to end up with following data:</p> <pre><code>cities_by_pop = [\n    {\n      \"name\": \"0-10,000,000\",\n      \"items\": [\n          {\"name\": \"Chicago\", \"population\": \"7,000,000\", \"country\": \"USA\"},\n      ]\n    },\n    {\n      \"name\": \"10,000,001-20,000,000\",\n      \"items\": [\n          {\"name\": \"Calcutta\", \"population\": \"15,000,000\", \"country\": \"India\"},\n          {\"name\": \"Mumbai\", \"population\": \"19,000,000\", \"country\": \"India\"},\n          {\"name\": \"New York\", \"population\": \"20,000,000\", \"country\": \"USA\"},\n      ]\n    },\n    {\n      \"name\": \"30,000,001-40,000,000\",\n      \"items\": [\n          {\"name\": \"Tokyo\", \"population\": \"33,000,000\", \"country\": \"Japan\"},\n      ]\n    },\n]\n</code></pre> <p>Without the <code>get_context_data()</code> method, we'd have to either:</p> <ol> <li>Pre-process the data in Python before passing it to the components.</li> <li>Define a Django filter or template tag to take the data and process it on the spot.</li> </ol> <p>Instead, with <code>get_context_data()</code>, we can keep this transformation private to this component, and keep the rest of the codebase clean.</p> <pre><code>def group_by_pop(data):\n    ...\n\n@register(\"population_table\")\nclass PopulationTable(Component):\n    template_file = \"population_table.html\"\n\n    def get_context_data(self, data):\n        return {\n            \"data\": group_by_pop(data),\n        }\n</code></pre> <p>Similarly we can make use of <code>get_context_data()</code> to pre-process the date that was given to the component:</p> [project root]/components/calendar/calendar.py<pre><code>from datetime import date\n\nfrom django_components import Component, register\n\n# If date is Sat or Sun, shift it to next Mon, so the date is always workweek.\ndef to_workweek_date(d: date):\n    ...\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    ...\n    def get_context_data(self, date: date, extra_class: str | None = None):\n        workweek_date = to_workweek_date(date)  # &lt;--- new\n        return {\n            \"date\": workweek_date,  # &lt;--- changed\n            \"extra_class\": extra_class,\n        }\n</code></pre>"},{"location":"getting_started/parametrising_components/#4-pass-inputs-to-components","title":"4. Pass inputs to components","text":"<p>Once we're happy with <code>Calendar.get_contex_data()</code>, we can update our templates to use the parametrized version of the component:</p> <pre><code>&lt;div&gt;\n  {% component \"calendar\" date=\"2024-12-13\" / %}\n  {% component \"calendar\" date=\"1970-01-01\" / %}\n&lt;/div&gt;\n</code></pre> <p>Next, you will learn how to use slots give your components even more flexibility \u27a1\ufe0f</p>"},{"location":"getting_started/rendering_components/","title":"Rendering components","text":"<p>Our calendar component can accept and pre-process data, defines its own CSS and JS, and can be used in templates.</p> <p>...But how do we actually render the components into HTML?</p> <p>There's 3 ways to render a component:</p> <ul> <li>Render the template that contains the <code>{% component %}</code> tag</li> <li>Render the component directly with <code>Component.render()</code></li> <li>Render the component directly with <code>Component.render_to_response()</code></li> </ul> <p>As a reminder, this is what the calendar component looks like:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre>"},{"location":"getting_started/rendering_components/#1-render-the-template-that-contains-the-component-tag","title":"1. Render the template that contains the <code>{% component %}</code> tag","text":"<p>If you have embedded the component in a Django template using the <code>{% component %}</code> tag:</p> [project root]/templates/my_template.html<pre><code>{% load component_tags %}\n&lt;div&gt;\n  {% component \"calendar\" date=\"2024-12-13\" / %}\n&lt;/div&gt;\n</code></pre> <p>You can simply render the template with the Django tooling:</p>"},{"location":"getting_started/rendering_components/#with-djangoshortcutsrender","title":"With <code>django.shortcuts.render()</code>","text":"<pre><code>from django.shortcuts import render\n\ncontext = {\"date\": \"2024-12-13\"}\nrendered_template = render(request, \"my_template.html\", context)\n</code></pre>"},{"location":"getting_started/rendering_components/#with-templaterender","title":"With <code>Template.render()</code>","text":"<p>Either loading the template with <code>get_template()</code>:</p> <pre><code>from django.template.loader import get_template\n\ntemplate = get_template(\"my_template.html\")\ncontext = {\"date\": \"2024-12-13\"}\nrendered_template = template.render(context)\n</code></pre> <p>Or creating a new <code>Template</code> instance:</p> <pre><code>from django.template import Template\n\ntemplate = Template(\"\"\"\n{% load component_tags %}\n&lt;div&gt;\n  {% component \"calendar\" date=\"2024-12-13\" / %}\n&lt;/div&gt;\n\"\"\")\nrendered_template = template.render()\n</code></pre>"},{"location":"getting_started/rendering_components/#2-render-the-component-directly-with-componentrender","title":"2. Render the component directly with <code>Component.render()</code>","text":"<p>You can also render the component directly with <code>Component.render()</code>, without wrapping the component in a template.</p> <pre><code>from components.calendar import Calendar\n\ncalendar = Calendar\nrendered_component = calendar.render()\n</code></pre> <p>You can pass args, kwargs, slots, and more, to the component:</p> <pre><code>from components.calendar import Calendar\n\ncalendar = Calendar\nrendered_component = calendar.render(\n    args=[\"2024-12-13\"],\n    kwargs={\n        \"extra_class\": \"my-class\"\n    },\n    slots={\n        \"date\": \"&lt;b&gt;2024-12-13&lt;/b&gt;\"\n    },\n)\n</code></pre> <p>Info</p> <p>Among other, you can pass also the <code>request</code> object to the <code>render</code> method:</p> <pre><code>from components.calendar import Calendar\n\ncalendar = Calendar\nrendered_component = calendar.render(request=request)\n</code></pre> <p>The <code>request</code> object is required for some of the component's features, like using Django's context processors.</p>"},{"location":"getting_started/rendering_components/#3-render-the-component-directly-with-componentrender_to_response","title":"3. Render the component directly with <code>Component.render_to_response()</code>","text":"<p>A common pattern in Django is to render the component and then return the resulting HTML as a response to an HTTP request.</p> <p>For this, you can use the <code>Component.render_to_response()</code> convenience method.</p> <p><code>render_to_response()</code> accepts the same args, kwargs, slots, and more, as <code>Component.render()</code>, but wraps the result in an <code>HttpResponse</code>.</p> <pre><code>from components.calendar import Calendar\n\ndef my_view(request):\n    response = Calendar.render_to_response(\n        args=[\"2024-12-13\"],\n        kwargs={\n            \"extra_class\": \"my-class\"\n        },\n        slots={\n            \"date\": \"&lt;b&gt;2024-12-13&lt;/b&gt;\"\n        },\n        request=request,\n    )\n    return response\n</code></pre> <p>Info</p> <p>Response class of <code>render_to_response</code></p> <p>While <code>render</code> method returns a plain string, <code>render_to_response</code> wraps the rendered content in a \"Response\" class. By default, this is <code>django.http.HttpResponse</code>.</p> <p>If you want to use a different Response class in <code>render_to_response</code>, set the <code>Component.response_class</code> attribute:</p> <pre><code>class MyCustomResponse(HttpResponse):\n    def __init__(self, *args, **kwargs) -&gt; None:\n        super().__init__(*args, **kwargs)\n        # Configure response\n        self.headers = ...\n        self.status = ...\n\nclass SimpleComponent(Component):\n    response_class = MyCustomResponse\n</code></pre>"},{"location":"getting_started/your_first_component/","title":"Create your first component","text":"<p>A component in django-components can be as simple as a Django template and Python code to declare the component:</p> calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n</code></pre> <p>Or a combination of Django template, Python, CSS, and Javascript:</p> calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> calendar.css<pre><code>.calendar {\n  width: 200px;\n  background: pink;\n}\n</code></pre> calendar.js<pre><code>document.querySelector(\".calendar\").onclick = function () {\n  alert(\"Clicked calendar!\");\n};\n</code></pre> calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n</code></pre> <p>Alternatively, you can \"inline\" HTML, JS, and CSS right into the component class:</p> <pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template = \"\"\"\n      &lt;div class=\"calendar\"&gt;\n        Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n      &lt;/div&gt;\n    \"\"\"\n\n    css = \"\"\"\n      .calendar {\n        width: 200px;\n        background: pink;\n      }\n    \"\"\"\n\n    js = \"\"\"\n      document.querySelector(\".calendar\").onclick = function () {\n        alert(\"Clicked calendar!\");\n      };\n    \"\"\"\n</code></pre> <p>Note</p> <p>If you \"inline\" the HTML, JS and CSS code into the Python class, you can set up syntax highlighting for better experience. However, autocompletion / intellisense does not work with syntax highlighting.</p> <p>We'll start by creating a component that defines only a Django template:</p>"},{"location":"getting_started/your_first_component/#1-create-project-structure","title":"1. Create project structure","text":"<p>Start by creating empty <code>calendar.py</code> and <code>calendar.html</code> files:</p> <pre><code>sampleproject/\n\u251c\u2500\u2500 calendarapp/\n\u251c\u2500\u2500 components/             \ud83c\udd95\n\u2502   \u2514\u2500\u2500 calendar/           \ud83c\udd95\n\u2502       \u251c\u2500\u2500 calendar.py     \ud83c\udd95\n\u2502       \u2514\u2500\u2500 calendar.html   \ud83c\udd95\n\u251c\u2500\u2500 sampleproject/\n\u251c\u2500\u2500 manage.py\n\u2514\u2500\u2500 requirements.txt\n</code></pre>"},{"location":"getting_started/your_first_component/#2-write-django-template","title":"2. Write Django template","text":"<p>Inside <code>calendar.html</code>, write:</p> [project root]/components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>In this example we've defined one template variable <code>date</code>. You can use any and as many variables as you like. These variables will be defined in the Python file in <code>get_context_data()</code> when creating an instance of this component.</p> <p>Note</p> <p>The template will be rendered with whatever template backend you've specified in your Django settings file.</p> <p>Currently django-components supports only the default <code>\"django.template.backends.django.DjangoTemplates\"</code> template backend!</p>"},{"location":"getting_started/your_first_component/#3-create-new-component-in-python","title":"3. Create new Component in Python","text":"<p>In <code>calendar.py</code>, create a subclass of Component to create a new component.</p> <p>To link the HTML template with our component, set <code>template_file</code> to the name of the HTML file.</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n</code></pre> <p>Note</p> <p>The path to the template file can be either:</p> <ol> <li>Relative to the component's python file (as seen above),</li> <li>Relative to any of the component directories as defined by <code>COMPONENTS.dirs</code> and/or <code>COMPONENTS.app_dirs</code> (e.g. <code>[your apps]/components</code> dir and <code>[project root]/components</code>)</li> </ol>"},{"location":"getting_started/your_first_component/#4-define-the-template-variables","title":"4. Define the template variables","text":"<p>In <code>calendar.html</code>, we've used the variable <code>date</code>. So we need to define it for the template to work.</p> <p>This is done using <code>Component.get_context_data()</code>. It's a function that returns a dictionary. The entries in this dictionary will become available within the template as variables, e.g. as <code>{{ date }}</code>.</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>Now, when we render the component with <code>Component.render()</code> method:</p> <pre><code>Calendar.render()\n</code></pre> <p>It will output</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;1970-01-01&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>And voil\u00e1!! We've created our first component.</p> <p>Next, let's add JS and CSS to this component \u27a1\ufe0f.</p>"},{"location":"guides/devguides/dependency_mgmt/","title":"JS and CSS rendering","text":"<p>Aim of this doc is to share the intuition on how we manage the JS and CSS (\"dependencies\") associated with components, and how we render them.</p>"},{"location":"guides/devguides/dependency_mgmt/#starting-conditions","title":"Starting conditions","text":"<ol> <li> <p>First of all, when we consider a component, it has two kind of dependencies - the \"inlined\" JS and CSS, and additional linked JS and CSS via <code>Media.js/css</code>:</p> <pre><code>from django_components import Component, types\n\nclass MyTable(Component):\n    # Inlined JS\n    js: types.js = \"\"\"\n      console.log(123);\n    \"\"\"\n\n    # Inlined CSS\n    css: types.css = \"\"\"\n      .my-table {\n        color: red;\n      }\n    \"\"\"\n\n    # Linked JS / CSS\n    class Media:\n        js = [\n            \"script-one.js\",  # STATIC file relative to component file\n            \"/script-two.js\", # URL path\n            \"https://example.com/script-three.js\", # URL\n        ]\n\n        css = [\n            \"style-one.css\",  # STATIC file relative to component file\n            \"/style-two.css\", # URL path\n            \"https://example.com/style-three.css\", # URL\n        ]\n</code></pre> </li> <li> <p>Second thing to keep in mind is that all component's are eventually rendered into a string. And so, if we want to associate extra info with a rendered component, it has to be serialized to a string.</p> <p>This is because a component may be embedded in a Django Template with the <code>{% component %}</code> tag, which, when rendered, is turned into a string:</p> <pre><code>template = Template(\"\"\"\n  {% load component_tags %}\n  &lt;div&gt;\n    {% component \"my_table\" / %}\n  &lt;/div&gt;\n\"\"\")\n\nhtml_str = template.render(Context({}))\n</code></pre> <p>And for this reason, we take the same approach also when we render a component with <code>Component.render()</code> - It returns a string.</p> </li> <li> <p>Thirdly, we also want to add support for JS / CSS variables. That is, that a variable defined on the component would be somehow accessible from within the JS script / CSS style.</p> <p>A simple approach to this would be to modify the inlined JS / CSS directly, and insert them for each component. But if you had extremely large JS / CSS, and e.g. only a single JS / CSS variable that you want to insert, it would be wasteful to create a copy of the JS / CSS scripts for each component instance.</p> <p>So instead, a preferred approach here is to defined and insert the inlined JS / CSS only once, and have some kind of mechanism on how we make correct the JS / CSS variables available only to the correct components.</p> </li> <li> <p>Last important thing is that we want the JS / CSS dependencies to work also with HTML fragments.</p> <p>So normally, e.g. when a user hits URL of a web page, the server renders full HTML document, with <code>&lt;!doctype&gt;</code>, <code>&lt;html&gt;</code>, <code>&lt;head&gt;</code>, and <code>&lt;body&gt;</code>. In such case, we know about ALL JS and CSS dependencies at render time, so we can e.g. insert them into <code>&lt;head&gt;</code> and <code>&lt;body&gt;</code> ourselves.</p> <p>However this renders only the initial state. HTML fragments is a common pattern where interactivity is added to the web page by fetching and replacing bits of HTML on the main HTML document after some user action.</p> <p>In the case of HTML fragments, the HTML is NOT a proper document, but only the HTML that will be inserted somewhere into the DOM.</p> <p>The challenge here is that Django template for the HTML fragment MAY contain components, and these components MAY have inlined or linked JS and CSS.</p> <pre><code>def fragment_view(request):\n    template = Template(\"\"\"\n      {% load component_tags %}\n      &lt;div&gt;\n        {% component \"my_table\" / %}\n      &lt;/div&gt;\n    \"\"\")\n\n    fragment_str = template.render(Context({}))\n    return HttpResponse(fragment_str, status=200)\n</code></pre> <p>User may use different libraries to fetch and insert the HTML fragments (e.g. HTMX, AlpineJS, ...). From our perspective, the only thing that we can reliably say is that we expect that the HTML fragment WILL be eventually inserted into the DOM.</p> <p>So to include the corresponding JS and CSS, a simple approach could be to append them to the HTML as <code>&lt;style&gt;</code> and <code>&lt;script&gt;</code>, e.g.:</p> <pre><code>&lt;!-- Original content --&gt;\n&lt;div&gt;...&lt;/div&gt;\n&lt;!-- Associated CSS files --&gt;\n&lt;link href=\"http://...\" /&gt;\n&lt;style&gt;\n  .my-class {\n    color: red;\n  }\n&lt;/style&gt;\n&lt;!-- Associated JS files --&gt;\n&lt;script src=\"http://...\"&gt;&lt;/script&gt;\n&lt;script&gt;\n  console.log(123);\n&lt;/script&gt;\n</code></pre> <p>But this has a number of issues:</p> <ul> <li>The JS scripts would run for each instance of the component.</li> <li>Bloating of the HTML file, as each inlined JS or CSS would be included fully for each component.</li> <li>While this sound OK, this could really bloat the HTML files if we used a UI component library for the basic building blocks like buttons, lists, cards, etc.</li> </ul> </li> </ol>"},{"location":"guides/devguides/dependency_mgmt/#flow","title":"Flow","text":"<p>So the solution should address all the points above. To achieve that, we manage the JS / CSS dependencies ourselves in the browser. So when a full HTML document is loaded, we keep track of which JS and CSS have been loaded. And when an HTML fragment is inserted, we check which JS / CSS dependencies it has, and load only those that have NOT been loaded yet.</p> <p>This is how we achieve that:</p> <ol> <li> <p>When a component is rendered, it inserts an HTML comment containing metadata about the rendered component.</p> <p>So a template like this</p> <pre><code>{% load component_tags %}\n&lt;div&gt;\n  {% component \"my_table\" / %}\n&lt;/div&gt;\n{% component \"button\" %}\n  Click me!\n{% endcomponent %}\n</code></pre> <p>May actually render:</p> <pre><code>&lt;div&gt;\n  &lt;!-- _RENDERED \"my_table_10bc2c,c020ad\" --&gt;\n  &lt;table&gt;\n    ...\n  &lt;/table&gt;\n&lt;/div&gt;\n&lt;!-- _RENDERED \"button_309dcf,31c0da\" --&gt;\n&lt;button&gt;Click me!&lt;/button&gt;\n</code></pre> <p>Each <code>&lt;!-- _RENDERED --&gt;</code> comment includes comma-separated data - a unique hash for the component class, e.g. <code>my_table_10bc2c</code>, and the component ID, e.g. <code>c020ad</code>.</p> <p>This way, we or the user can freely pass the rendered around or transform it, treating it as a string to add / remove / replace bits. As long as the <code>&lt;!-- _RENDERED --&gt;</code> comments remain in the rendered string, we will be able to deduce which JS and CSS dependencies the component needs.</p> </li> <li> <p>Post-process the rendered HTML, extracting the <code>&lt;!-- _RENDERED --&gt;</code> comments, and instead inserting the corresponding JS and CSS dependencies.</p> <p>If we dealt only with JS, then we could get away with processing the <code>&lt;!-- _RENDERED --&gt;</code> comments on the client (browser). However, the CSS needs to be processed still on the server, so the browser receives CSS styles already inserted as <code>&lt;style&gt;</code> or <code>&lt;link&gt;</code> HTML tags. Because if we do not do that, we get a flash of unstyled content, as there will be a delay between when the HTML page loaded and when the CSS was fetched and loaded.</p> <p>So, assuming that a user has already rendered their template, which still contains <code>&lt;!-- _RENDERED --&gt;</code> comments, we need to extract and process these comments.</p> <p>There's multiple ways to achieve this:</p> <ul> <li> <p>The approach recommended to the users is to use the <code>ComponentDependencyMiddleware</code> middleware, which scans all outgoing HTML, and post-processes the <code>&lt;!-- _RENDERED --&gt;</code> comments.</p> </li> <li> <p>If users are using <code>Component.render()</code> or <code>Component.render_to_response()</code>, these post-process the <code>&lt;!-- _RENDERED --&gt;</code> comments by default.</p> </li> <li> <p>NOTE: Users are able to opt out of the post-processing by setting <code>render_dependencies=False</code>.</p> </li> <li> <p>For advanced use cases, users may use <code>render_dependencies()</code> directly. This is the function that both <code>ComponentDependencyMiddleware</code> and <code>Component.render()</code> call internally.</p> </li> </ul> <p><code>render_dependencies()</code>, whether called directly, via middleware or other way, does the following:</p> <ol> <li> <p>Find all <code>&lt;!-- _RENDERED --&gt;</code> comments, and for each comment:</p> </li> <li> <p>Look up the corresponding component class.</p> </li> <li> <p>Get the component's inlined JS / CSS from <code>Component.js/css</code>, and linked JS / CSS from <code>Component.Media.js/css</code>.</p> </li> <li> <p>Generate JS script that loads the JS / CSS dependencies.</p> </li> <li> <p>Insert the JS scripts either at the end of <code>&lt;body&gt;</code>, or in place of <code>{% component_dependencies %}</code> / <code>{% component_js_dependencies %}</code> tags.</p> </li> <li> <p>To avoid the flash of unstyled content, we need place the styles into the HTML instead of dynamically loading them from within a JS script. The CSS is placed either at the end of <code>&lt;head&gt;</code>, or in place of <code>{% component_dependencies %}</code> / <code>{% component_css_dependencies %}</code></p> </li> <li> <p>We cache the component's inlined JS and CSS, so they can be fetched via an URL, so the inlined JS / CSS an be treated the same way as the JS / CSS dependencies set in <code>Component.Media.js/css</code>.</p> <ul> <li>NOTE: While this is currently not entirely necessary, it opens up the doors for allowing plugins to post-process the inlined JS and CSS. Because after it has been post-processed, we need to store it somewhere.</li> </ul> </li> </ol> </li> <li> <p>Server returns the post-processed HTML.</p> </li> <li> <p>In the browser, the generated JS script from step 2.4 is executed. It goes through all JS and CSS dependencies it was given. If some JS / CSS was already loaded, it is NOT fetched again. Otherwise it generates the corresponding <code>&lt;script&gt;</code> or <code>&lt;link&gt;</code> HTML tags to load the JS / CSS dependencies.</p> <p>In the browser, the \"dependency manager JS\" may look like this:</p> <pre><code>// Load JS or CSS script if not loaded already\nComponents.loadJs('&lt;script src=\"/abc/xyz/script.js\"&gt;');\nComponents.loadCss('&lt;link href=\"/abc/xyz/style.css\"&gt;');\n\n// Or mark one as already-loaded, so it is ignored when\n// we call `loadJs`\nComponents.markScriptLoaded(\"js\", \"/abc/def\");\n</code></pre> <p>Note that <code>loadJs() / loadCss()</code> receive whole <code>&lt;script&gt; / &lt;link&gt;</code> tags, not just the URL. This is because when Django's <code>Media</code> class renders JS and CSS, it formats it as <code>&lt;script&gt;</code> and <code>&lt;link&gt;</code> tags. And we allow users to modify how the JS and CSS should be rendered into the <code>&lt;script&gt;</code> and <code>&lt;link&gt;</code> tags.</p> <p>So, if users decided to add an extra attribute to their <code>&lt;script&gt;</code> tags, e.g. <code>&lt;script defer src=\"http://...\"&gt;&lt;/script&gt;</code>, then this way we make sure that the <code>defer</code> attribute will be present on the <code>&lt;script&gt;</code> tag when it is inserted into the DOM at the time of loading the JS script.</p> </li> <li> <p>To be able to fetch component's inlined JS and CSS, django-components adds a URL path under:</p> <p><code>/components/cache/&lt;str:comp_cls_hash&gt;.&lt;str:script_type&gt;/</code></p> <p>E.g. <code>/components/cache/my_table_10bc2c.js/</code></p> <p>This endpoint takes the component's unique hash, e.g. <code>my_table_10bc2c</code>, and looks up the component's inlined JS or CSS.</p> </li> </ol> <p>Thus, with this approach, we ensure that:</p> <ol> <li>All JS / CSS dependencies are loaded / executed only once.</li> <li>The approach is compatible with HTML fragments</li> <li>The approach is compatible with JS / CSS variables.</li> <li>Inlined JS / CSS may be post-processed by plugins</li> </ol>"},{"location":"guides/devguides/slot_rendering/","title":"Slot rendering","text":"<p>This doc serves as a primer on how component slots and fills are resolved.</p>"},{"location":"guides/devguides/slot_rendering/#flow","title":"Flow","text":"<ol> <li> <p>Imagine you have a template. Some kind of text, maybe HTML:    <pre><code>| ------\n| ---------\n| ----\n| -------\n</code></pre></p> </li> <li> <p>The template may contain some vars, tags, etc    <pre><code>| -- {{ my_var }} --\n| ---------\n| ----\n| -------\n</code></pre></p> </li> <li> <p>The template also contains some slots, etc    <pre><code>| -- {{ my_var }} --\n| ---------\n| -- {% slot \"myslot\" %} ---\n| -- {% endslot %} ---\n| ----\n| -- {% slot \"myslot2\" %} ---\n| -- {% endslot %} ---\n| -------\n</code></pre></p> </li> <li> <p>Slots may be nested    <pre><code>| -- {{ my_var }} --\n| -- ABC\n| -- {% slot \"myslot\" %} ---\n| ----- DEF {{ my_var }}\n| ----- {% slot \"myslot_inner\" %}\n| -------- GHI {{ my_var }}\n| ----- {% endslot %}\n| -- {% endslot %} ---\n| ----\n| -- {% slot \"myslot2\" %} ---\n| ---- JKL {{ my_var }}\n| -- {% endslot %} ---\n| -------\n</code></pre></p> </li> <li> <p>Some slots may be inside fills for other components    <pre><code>| -- {{ my_var }} --\n| -- ABC\n| -- {% slot \"myslot\" %}---\n| ----- DEF {{ my_var }}\n| ----- {% slot \"myslot_inner\" %}\n| -------- GHI {{ my_var }}\n| ----- {% endslot %}\n| -- {% endslot %} ---\n| ------\n| -- {% component \"mycomp\" %} ---\n| ---- {% slot \"myslot\" %} ---\n| ------- JKL {{ my_var }}\n| ------- {% slot \"myslot_inner\" %}\n| ---------- MNO {{ my_var }}\n| ------- {% endslot %}\n| ---- {% endslot %} ---\n| -- {% endcomponent %} ---\n| ----\n| -- {% slot \"myslot2\" %} ---\n| ---- PQR {{ my_var }}\n| -- {% endslot %} ---\n| -------\n</code></pre></p> </li> <li> <p>The names of the slots and fills may be defined using variables    <pre><code>| -- {% slot slot_name %} ---\n| ---- STU {{ my_var }}\n| -- {% endslot %} ---\n| -------\n</code></pre></p> </li> <li> <p>The slot and fill names may be defined using for loops or other variables defined within the template (e.g. <code>{% with %}</code> tag or <code>{% ... as var %}</code> syntax)    <pre><code>| -- {% for slot_name in slots %} ---\n| ---- {% slot slot_name %} ---\n| ------ STU {{ slot_name }}\n| ---- {% endslot %} ---\n| -- {% endfor %} ---\n| -------\n</code></pre></p> </li> <li> <p>Variables for names and for loops allow us implement \"passthrough slots\" - that is, taking all slots that our component received, and passing them to a child component, dynamically.    <pre><code>| -- {% component \"mycomp\" %} ---\n| ---- {% for slot_name in slots %} ---\n| ------ {% fill slot_name %} ---\n| -------- {% slot slot_name %} ---\n| ---------- XYZ {{ slot_name }}\n| --------- {% endslot %}\n| ------- {% endfill %}\n| ---- {% endfor %} ---\n| -- {% endcomponent %} ---\n| ----\n</code></pre></p> </li> <li> <p>Putting that all together, a document may look like this:    <pre><code>| -- {{ my_var }} --\n| -- ABC\n| -- {% slot \"myslot\" %}---\n| ----- DEF {{ my_var }}\n| ----- {% slot \"myslot_inner\" %}\n| -------- GHI {{ my_var }}\n| ----- {% endslot %}\n| -- {% endslot %} ---\n| ------\n| -- {% component \"mycomp\" %} ---\n| ---- {% slot \"myslot\" %} ---\n| ------- JKL {{ my_var }}\n| ------- {% slot \"myslot_inner\" %}\n| ---------- MNO {{ my_var }}\n| ------- {% endslot %}\n| ---- {% endslot %} ---\n| -- {% endcomponent %} ---\n| ----\n| -- {% slot \"myslot2\" %} ---\n| ---- PQR {{ my_var }}\n| -- {% endslot %} ---\n| -------\n| -- {% for slot_name in slots %} ---\n| ---- {% component \"mycomp\" %} ---\n| ------- {% slot slot_name %}\n| ---------- STU {{ slot_name }}\n| ------- {% endslot %}\n| ---- {% endcomponent %} ---\n| -- {% endfor %} ---\n| ----\n| -- {% component \"mycomp\" %} ---\n| ---- {% for slot_name in slots %} ---\n| ------ {% fill slot_name %} ---\n| -------- {% slot slot_name %} ---\n| ---------- XYZ {{ slot_name }}\n| --------- {% endslot %}\n| ------- {% endfill %}\n| ---- {% endfor %} ---\n| -- {% endcomponent %} ---\n| -------\n</code></pre></p> </li> <li> <p>Given the above, we want to render the slots with <code>{% fill %}</code> tag that were defined OUTSIDE of this template. How do I do that?</p> <p>NOTE: Before v0.110, slots were resolved statically, by walking down the Django Template and Nodes. However, this did not allow for using for loops or other variables defined in the template.</p> <p>Currently, this consists of 2 steps:</p> <ol> <li> <p>If a component is rendered within a template using <code>{% component %}</code> tag, determine the given <code>{% fill %}</code> tags in the component's body (the content in between <code>{% component %}</code> and <code>{% endcomponent %}</code>).</p> <p>After this step, we know about all the fills that were passed to the component.</p> </li> <li> <p>Then we simply render the template as usual. And then we reach the <code>{% slot %}</code> tag, we search the context for the available fills.</p> <ul> <li>If there IS a fill with the same name as the slot, we render the fill.</li> <li>If the slot is marked <code>default</code>, and there is a fill named <code>default</code>, then we render that.</li> <li>Otherwise, we render the slot's default content.</li> </ul> </li> </ol> </li> <li> <p>Obtaining the fills from <code>{% fill %}</code>.</p> <p>When a component is rendered with <code>{% component %}</code> tag, and it has some content in between <code>{% component %}</code> and <code>{% endcomponent %}</code>, we want to figure out if that content is a default slot (no <code>{% fill %}</code> used), or if there is a collection of named <code>{% fill %}</code> tags:</p> <p>Default slot:</p> <pre><code>| -- {% component \"mycomp\" %} ---\n| ---- STU {{ slot_name }}\n| -- {% endcomponent %} ---\n</code></pre> <p>Named slots:</p> <pre><code>| -- {% component \"mycomp\" %} ---\n| ---- {% fill \"slot_a\" %}\n| ------ STU\n| ---- {% endslot %}\n| ---- {% fill \"slot_b\" %}\n| ------ XYZ\n| ---- {% endslot %}\n| -- {% endcomponent %} ---\n</code></pre> <p>To respect any forloops or other variables defined within the template to which the fills may have access, we:</p> <ol> <li>Render the content between <code>{% component %}</code> and <code>{% endcomponent %}</code> using the context    outside of the component.</li> <li>When we reach a <code>{% fill %}</code> tag, we capture any variables that were created between    the <code>{% component %}</code> and <code>{% fill %}</code> tags.</li> <li>When we reach <code>{% fill %}</code> tag, we do not continue rendering deeper. Instead we    make a record that we found the fill tag with given name, kwargs, etc.</li> <li>After the rendering is done, we check if we've encountered any fills.    If yes, we expect only named fills. If no, we assume that the the component's body    is a default slot.</li> <li>Lastly we process the found fills, and make them available to the context, so any    slots inside the component may access these fills.</li> </ol> </li> <li> <p>Rendering slots</p> <p>Slot rendering works similarly to collecting fills, in a sense that we do not search for the slots ahead of the time, but instead let Django handle the rendering of the template, and we step in only when Django come across as <code>{% slot %}</code> tag.</p> <p>When we reach a slot tag, we search the context for the available fills.</p> <ul> <li>If there IS a fill with the same name as the slot, we render the fill.</li> <li>If the slot is marked <code>default</code>, and there is a fill named <code>default</code>, then we render that.</li> <li>Otherwise, we render the slot's default content.</li> </ul> </li> </ol>"},{"location":"guides/devguides/slot_rendering/#using-the-correct-context-in-slotfill-tags","title":"Using the correct context in {% slot/fill %} tags","text":"<p>In previous section, we said that the <code>{% fill %}</code> tags should be already rendered by the time they are inserted into the <code>{% slot %}</code> tags.</p> <p>This is not quite true. To help you understand, consider this complex case:</p> <pre><code>| -- {% for var in [1, 2, 3] %} ---\n| ---- {% component \"mycomp2\" %} ---\n| ------ {% fill \"first\" %}\n| ------- STU {{ my_var }}\n| -------     {{ var }}\n| ------ {% endfill %}\n| ------ {% fill \"second\" %}\n| -------- {% component var=var my_var=my_var %}\n| ---------- VWX {{ my_var }}\n| -------- {% endcomponent %}\n| ------ {% endfill %}\n| ---- {% endcomponent %} ---\n| -- {% endfor %} ---\n| -------\n</code></pre> <p>We want the forloop variables to be available inside the <code>{% fill %}</code> tags. Because of that, however, we CANNOT render the fills/slots in advance.</p> <p>Instead, our solution is closer to how Vue handles slots. In Vue, slots are effectively functions that accept a context variables and render some content.</p> <p>While we do not wrap the logic in a function, we do PREPARE IN ADVANCE: 1. The content that should be rendered for each slot 2. The context variables from <code>get_context_data()</code></p> <p>Thus, once we reach the <code>{% slot %}</code> node, in it's <code>render()</code> method, we access the data above, and, depending on the <code>context_behavior</code> setting, include the current context or not. For more info, see <code>SlotNode.render()</code>.</p>"},{"location":"guides/devguides/slots_and_blocks/","title":"Using slot and block tags","text":"<ol> <li> <p>First let's clarify how <code>include</code> and <code>extends</code> tags work inside components.</p> <p>When component template includes <code>include</code> or <code>extends</code> tags, it's as if the \"included\" template was inlined. So if the \"included\" template contains <code>slot</code> tags, then the component uses those slots.</p> <p>If you have a template <code>abc.html</code>: <pre><code>&lt;div&gt;\n  hello\n  {% slot \"body\" %}{% endslot %}\n&lt;/div&gt;\n</code></pre></p> <p>And components that make use of <code>abc.html</code> via <code>include</code> or <code>extends</code>: <pre><code>from django_components import Component, register\n\n@register(\"my_comp_extends\")\nclass MyCompWithExtends(Component):\n    template = \"\"\"{% extends \"abc.html\" %}\"\"\"\n\n@register(\"my_comp_include\")\nclass MyCompWithInclude(Component):\n    template = \"\"\"{% include \"abc.html\" %}\"\"\"\n</code></pre></p> <p>Then you can set slot fill for the slot imported via <code>include/extends</code>:</p> <pre><code>{% component \"my_comp_extends\" %}\n    {% fill \"body\" %}\n        123\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>And it will render: <pre><code>&lt;div&gt;\n  hello\n  123\n&lt;/div&gt;\n</code></pre></p> </li> <li> <p>Slot and block</p> <p>If you have a template <code>abc.html</code> like so:</p> <pre><code>&lt;div&gt;\n  hello\n  {% block inner %}\n    1\n    {% slot \"body\" %}\n      2\n    {% endslot %}\n  {% endblock %}\n&lt;/div&gt;\n</code></pre> <p>and component <code>my_comp</code>:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template_file = \"abc.html\"\n</code></pre> <p>Then:</p> <ol> <li> <p>Since the <code>block</code> wasn't overriden, you can use the <code>body</code> slot:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"body\" %}\n        XYZ\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>And we get:</p> <pre><code>&lt;div&gt;hello 1 XYZ&lt;/div&gt;\n</code></pre> </li> <li> <p><code>blocks</code> CANNOT be overriden through the <code>component</code> tag, so something like this:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"body\" %}\n        XYZ\n    {% endfill %}\n{% endcomponent %}\n{% block \"inner\" %}\n    456\n{% endblock %}\n</code></pre> <p>Will still render the component content just the same:</p> <pre><code>&lt;div&gt;hello 1 XYZ&lt;/div&gt;\n</code></pre> </li> <li> <p>You CAN override the <code>block</code> tags of <code>abc.html</code> if the component template     uses <code>extends</code>. In that case, just as you would expect, the <code>block inner</code> inside     <code>abc.html</code> will render <code>OVERRIDEN</code>:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        {% extends \"abc.html\" %}\n        {% block inner %}\n          OVERRIDEN\n        {% endblock %}\n    \"\"\"\n</code></pre> </li> <li> <p>This is where it gets interesting (but still intuitive). You can insert even     new <code>slots</code> inside these \"overriding\" blocks:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n      {% extends \"abc.html\" %}\n\n      {% load component_tags %}\n      {% block \"inner\" %}\n        OVERRIDEN\n        {% slot \"new_slot\" %}\n          hello\n        {% endslot %}\n      {% endblock %}\n    \"\"\"\n</code></pre> <p>And you can then pass fill for this <code>new_slot</code> when rendering the component:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"new_slot\" %}\n        XYZ\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>NOTE: Currently you can supply fills for both <code>new_slot</code> and <code>body</code> slots, and you will not get an error for an invalid/unknown slot name. But since <code>body</code> slot is not rendered, it just won't do anything. So this renders the same as above:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"new_slot\" %}\n        XYZ\n    {% endfill %}\n    {% fill \"body\" %}\n        www\n    {% endfill %}\n{% endcomponent %}\n</code></pre> </li> </ol> </li> </ol>"},{"location":"guides/other/troubleshooting/","title":"Troubleshooting","text":"<p>As larger projects get more complex, it can be hard to debug issues. Django Components provides a number of tools and approaches that can help you with that.</p>"},{"location":"guides/other/troubleshooting/#component-and-slot-highlighting","title":"Component and slot highlighting","text":"<p>Django Components provides a visual debugging feature that helps you understand the structure and boundaries of your components and slots. When enabled, it adds a colored border and a label around each component and slot on your rendered page.</p> <p>To enable component and slot highlighting, set <code>debug_highlight_components</code> and/or <code>debug_highlight_slots</code> to <code>True</code> in your <code>settings.py</code> file:</p> <pre><code>from django_components import ComponentsSettings\n\nCOMPONENTS = ComponentsSettings(\n    debug_highlight_components=True,\n    debug_highlight_slots=True,\n)\n</code></pre> <p>Components will be highlighted with a blue border and label:</p> <p></p> <p>While the slots will be highlighted with a red border and label:</p> <p></p> <p>Warning</p> <p>Use this feature ONLY in during development. Do NOT use it in production.</p>"},{"location":"guides/other/troubleshooting/#component-path-in-errors","title":"Component path in errors","text":"<p>When an error occurs, the error message will show the path to the component that caused the error. E.g.</p> <pre><code>KeyError: \"An error occured while rendering components MyPage &gt; MyLayout &gt; MyComponent &gt; Childomponent(slot:content)\n</code></pre> <p>The error message contains also the slot paths, so if you have a template like this:</p> <pre><code>{% component \"my_page\" %}\n    {% slot \"content\" %}\n        {% component \"table\" %}\n            {% slot \"header\" %}\n                {% component \"table_header\" %}\n                    ...  {# ERROR HERE #}\n                {% endcomponent %}\n            {% endslot %}\n        {% endcomponent %}\n    {% endslot %}\n{% endcomponent %}\n</code></pre> <p>Then the error message will show the path to the component that caused the error:</p> <pre><code>KeyError: \"An error occured while rendering components my_page &gt; layout &gt; layout(slot:content) &gt; my_page(slot:content) &gt; table &gt; table(slot:header) &gt; table_header &gt; table_header(slot:content)\n</code></pre>"},{"location":"guides/other/troubleshooting/#debug-and-trace-logging","title":"Debug and trace logging","text":"<p>Django components supports logging with Django.</p> <p>To configure logging for Django components, set the <code>django_components</code> logger in <code>LOGGING</code> in <code>settings.py</code> (below).</p> <p>Also see the <code>settings.py</code> file in sampleproject for a real-life example.</p> <pre><code>import logging\nimport sys\n\nLOGGING = {\n    'version': 1,\n    'disable_existing_loggers': False,\n    \"handlers\": {\n        \"console\": {\n            'class': 'logging.StreamHandler',\n            'stream': sys.stdout,\n        },\n    },\n    \"loggers\": {\n        \"django_components\": {\n            \"level\": logging.DEBUG,\n            \"handlers\": [\"console\"],\n        },\n    },\n}\n</code></pre> <p>Info</p> <p>To set TRACE level, set <code>\"level\"</code> to <code>5</code>:</p> <pre><code>LOGGING = {\n    \"loggers\": {\n        \"django_components\": {\n            \"level\": 5,\n            \"handlers\": [\"console\"],\n        },\n    },\n}\n</code></pre>"},{"location":"guides/other/troubleshooting/#logger-levels","title":"Logger levels","text":"<p>As of v0.126, django-components primarily uses these logger levels:</p> <ul> <li><code>DEBUG</code>: Report on loading associated HTML / JS / CSS files, autodiscovery, etc.</li> <li><code>TRACE</code>: Detailed interaction of components and slots. Logs when template tags,   components, and slots are started / ended rendering, and when a slot is filled.</li> </ul>"},{"location":"guides/other/troubleshooting/#slot-origin","title":"Slot origin","text":"<p>When you pass a slot fill to a Component, the component and slot names is remebered on the slot object.</p> <p>Thus, you can check where a slot was filled from by printing it out:</p> <pre><code>class MyComponent(Component):\n    def on_render_before(self):\n        print(self.input.slots)\n</code></pre> <p>might print:</p> <pre><code>{\n    'content': &lt;Slot component_name='layout' slot_name='content'&gt;,\n    'header': &lt;Slot component_name='my_page' slot_name='header'&gt;,\n    'left_panel': &lt;Slot component_name='layout' slot_name='left_panel'&gt;,\n}\n</code></pre>"},{"location":"guides/other/troubleshooting/#agentic-debugging","title":"Agentic debugging","text":"<p>All the features above make django-components to work really well with coding AI agents like Github Copilot or CursorAI.</p> <p>To debug component rendering with LLMs, you want to provide the LLM with:</p> <ol> <li>The components source code</li> <li>The rendered output</li> <li>As much additional context as possible</li> </ol> <p>Your codebase already contains the components source code, but not the latter two.</p>"},{"location":"guides/other/troubleshooting/#providing-rendered-output","title":"Providing rendered output","text":"<p>To provide the LLM with the rendered output, you can simply export the rendered output to a file.</p> <pre><code>rendered = ProjectPage.render(...)\nwith open(\"result.html\", \"w\") as f:\n    f.write(rendered)\n</code></pre> <p>If you're using <code>render_to_response</code>, access the output from the <code>HttpResponse</code> object:</p> <pre><code>response = ProjectPage.render_to_response(...)\nwith open(\"result.html\", \"wb\") as f:\n    f.write(response.content)\n</code></pre>"},{"location":"guides/other/troubleshooting/#providing-contextual-logs","title":"Providing contextual logs","text":"<p>Next, we provide the agent with info on HOW we got the result that we have. We do so by providing the agent with the trace-level logs.</p> <p>In your <code>settings.py</code>, configure the trace-level logs to be written to the <code>django_components.log</code> file:</p> <pre><code>LOGGING = {\n    \"version\": 1,\n    \"disable_existing_loggers\": False,\n    \"handlers\": {\n        \"file\": {\n            \"class\": \"logging.FileHandler\",\n            \"filename\": \"django_components.log\",\n            \"mode\": \"w\",  # Overwrite the file each time\n        },\n    },\n    \"loggers\": {\n        \"django_components\": {\n            \"level\": 5,\n            \"handlers\": [\"file\"],\n        },\n    },\n}\n</code></pre>"},{"location":"guides/other/troubleshooting/#prompting-the-agent","title":"Prompting the agent","text":"<p>Now, you can prompt the agent and include the trace log and the rendered output to guide the agent with debugging.</p> <p>I have a django-components (DJC) project. DJC is like if Vue or React component-based web development but made for Django ecosystem.</p> <p>In the view <code>project_view</code>, I am rendering the <code>ProjectPage</code> component. However, the output is not as expected. The output is missing the tabs.</p> <p>You have access to the full log trace in <code>django_components.log</code>.</p> <p>You can also see the rendered output in <code>result.html</code>.</p> <p>With this information, help me debug the issue.</p> <p>First, tell me what kind of info you would be looking for in the logs, and why (how it relates to understanding the cause of the bug).</p> <p>Then tell me if that info was there, and what the implications are.</p> <p>Finally, tell me what you would do to fix the issue.</p>"},{"location":"guides/setup/caching/","title":"Caching","text":"<p>This page describes the kinds of assets that django-components caches and how to configure the cache backends.</p>"},{"location":"guides/setup/caching/#components-js-and-css-files","title":"Component's JS and CSS files","text":"<p>django-components caches the JS and CSS files associated with your components. This enables components to be rendered as HTML fragments and still having the associated JS and CSS files loaded with them.</p> <p>This includes:</p> <ul> <li>Inlined JS/CSS defined via <code>Component.js</code> and <code>Component.css</code></li> <li>JS/CSS variables generated from <code>get_js_data()</code> and <code>get_css_data()</code></li> </ul> <p>By default, django-components uses Django's local memory cache backend to store these assets. You can configure it to use any of your Django cache backends by setting the <code>COMPONENTS.cache</code> option in your settings:</p> <pre><code>COMPONENTS = {\n    # Name of the cache backend to use\n    \"cache\": \"my-cache-backend\",\n}\n</code></pre> <p>The value should be the name of one of your configured cache backends from Django's <code>CACHES</code> setting.</p> <p>For example, to use Redis for caching component assets:</p> <pre><code>CACHES = {\n    \"default\": {\n        \"BACKEND\": \"django.core.cache.backends.locmem.LocMemCache\",\n    },\n    \"component-media\": {\n        \"BACKEND\": \"django.core.cache.backends.redis.RedisCache\",\n        \"LOCATION\": \"redis://127.0.0.1:6379/1\",\n    }\n}\n\nCOMPONENTS = {\n    # Use the Redis cache backend\n    \"cache\": \"component-media\",\n}\n</code></pre> <p>See <code>COMPONENTS.cache</code> for more details about this setting.</p>"},{"location":"guides/setup/development_server/","title":"Development server","text":""},{"location":"guides/setup/development_server/#reload-dev-server-on-component-file-changes","title":"Reload dev server on component file changes","text":"<p>This is relevant if you are using the project structure as shown in our examples, where HTML, JS, CSS and Python are in separate files and nested in a directory.</p> <pre><code>sampleproject/\n\u251c\u2500\u2500 components/\n\u2502   \u2514\u2500\u2500 calendar/\n\u2502       \u251c\u2500\u2500 calendar.py\n\u2502       \u2514\u2500\u2500 calendar.html\n\u2502       \u2514\u2500\u2500 calendar.css\n\u2502       \u2514\u2500\u2500 calendar.js\n\u251c\u2500\u2500 sampleproject/\n\u251c\u2500\u2500 manage.py\n\u2514\u2500\u2500 requirements.txt\n</code></pre> <p>In this case you may notice that when you are running a development server, the server sometimes does not reload when you change component files.</p> <p>From relevant StackOverflow thread:</p> <p>TL;DR is that the server won't reload if it thinks the changed file is in a templates directory, or in a nested sub directory of a templates directory. This is by design.</p> <p>To make the dev server reload on all component files, set <code>reload_on_file_change</code> to <code>True</code>. This configures Django to watch for component files too.</p> <p>Warning</p> <p>This setting should be enabled only for the dev environment!</p>"},{"location":"guides/setup/syntax_highlight/","title":"Syntax highlighting","text":""},{"location":"guides/setup/syntax_highlight/#vscode","title":"VSCode","text":"<ol> <li> <p>First install Python Inline Source Syntax Highlighting extension, it will give you syntax highlighting for the template, CSS, and JS.</p> </li> <li> <p>Next, in your component, set typings of <code>Component.template/css/js</code> to <code>types.django_html</code>, <code>types.css</code>, and <code>types.js</code> respectively. The extension will recognize these and will activate syntax highlighting.</p> </li> </ol> [project root]/components/calendar.py<pre><code># In a file called [project root]/components/calendar.py\nfrom django_components import Component, register, types\n\n@register(\"calendar\")\nclass Calendar(Component):\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n\n    template: types.django_html = \"\"\"\n        &lt;div class=\"calendar-component\"&gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css: types.css = \"\"\"\n        .calendar-component {\n            width: 200px;\n            background: pink;\n        }\n        .calendar-component span {\n            font-weight: bold;\n        }\n    \"\"\"\n\n    js: types.js = \"\"\"\n        (function(){\n            if (document.querySelector(\".calendar-component\")) {\n                document.querySelector(\".calendar-component\").onclick = function(){ alert(\"Clicked calendar!\"); };\n            }\n        })()\n    \"\"\"\n</code></pre>"},{"location":"guides/setup/syntax_highlight/#pycharm-or-other-jetbrains-ides","title":"Pycharm (or other Jetbrains IDEs)","text":"<p>With PyCharm (or any other editor from Jetbrains), you don't need to use <code>types.django_html</code>, <code>types.css</code>, <code>types.js</code> since Pycharm uses language injections. You only need to write the comments <code># language=&lt;lang&gt;</code> above the variables.</p> <pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n\n    # language=HTML\n    template= \"\"\"\n        &lt;div class=\"calendar-component\"&gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    # language=CSS\n    css = \"\"\"\n        .calendar-component {\n            width: 200px;\n            background: pink;\n        }\n        .calendar-component span {\n            font-weight: bold;\n        }\n    \"\"\"\n\n    # language=JS\n    js = \"\"\"\n        (function(){\n            if (document.querySelector(\".calendar-component\")) {\n                document.querySelector(\".calendar-component\").onclick = function(){ alert(\"Clicked calendar!\"); };\n            }\n        })()\n    \"\"\"\n</code></pre>"},{"location":"guides/setup/syntax_highlight/#pygments","title":"Pygments","text":"<p>Pygments is a syntax highlighting library written in Python. It's also what's used by this documentation site (mkdocs-material) to highlight code blocks.</p> <p>To write code blocks with syntax highlighting, you need to install the <code>pygments-djc</code> package.</p> <pre><code>pip install pygments-djc\n</code></pre> <p>And then initialize it by importing <code>pygments_djc</code>:</p> <pre><code>import pygments_djc\n</code></pre> <p>Now you can write code blocks with syntax highlighting.</p> <pre><code>\\```djc_py\nfrom django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template= \"\"\"\n        &lt;div class=\"calendar-component\"&gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css = \"\"\"\n        .calendar-component {\n            width: 200px;\n            background: pink;\n        }\n        .calendar-component span {\n            font-weight: bold;\n        }\n    \"\"\"\n\\```\n</code></pre>"},{"location":"overview/code_of_conduct/","title":"Contributor Covenant Code of Conduct","text":""},{"location":"overview/code_of_conduct/#our-pledge","title":"Our Pledge","text":"<p>In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.</p>"},{"location":"overview/code_of_conduct/#our-standards","title":"Our Standards","text":"<p>Examples of behavior that contributes to creating a positive environment include:</p> <ul> <li>Using welcoming and inclusive language</li> <li>Being respectful of differing viewpoints and experiences</li> <li>Gracefully accepting constructive criticism</li> <li>Focusing on what is best for the community</li> <li>Showing empathy towards other community members</li> </ul> <p>Examples of unacceptable behavior by participants include:</p> <ul> <li>The use of sexualized language or imagery and unwelcome sexual attention or  advances</li> <li>Trolling, insulting/derogatory comments, and personal or political attacks</li> <li>Public or private harassment</li> <li>Publishing others' private information, such as a physical or electronic  address, without explicit permission</li> <li>Other conduct which could reasonably be considered inappropriate in a  professional setting</li> </ul>"},{"location":"overview/code_of_conduct/#our-responsibilities","title":"Our Responsibilities","text":"<p>Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.</p> <p>Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.</p>"},{"location":"overview/code_of_conduct/#scope","title":"Scope","text":"<p>This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.</p>"},{"location":"overview/code_of_conduct/#enforcement","title":"Enforcement","text":"<p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at emil@emilstenstrom.se. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.</p> <p>Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.</p>"},{"location":"overview/code_of_conduct/#attribution","title":"Attribution","text":"<p>This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html</p> <p>For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq</p>"},{"location":"overview/community/","title":"Community","text":""},{"location":"overview/community/#community-questions","title":"Community questions","text":"<p>The best place to ask questions is in our Github Discussion board.</p> <p>Please, before opening a new discussion, check if similar discussion wasn't opened already.</p>"},{"location":"overview/community/#community-examples","title":"Community examples","text":"<p>One of our goals with <code>django-components</code> is to make it easy to share components between projects (see how to package components). If you have a set of components that you think would be useful to others, please open a pull request to add them to the list below.</p> <ul> <li> <p>django-htmx-components: A set of components for use with htmx. Try out the live demo.</p> </li> <li> <p>djc-heroicons: A component that renders icons from Heroicons.com.</p> </li> </ul>"},{"location":"overview/compatibility/","title":"Compatibility","text":"<p>Django-components supports all supported combinations versions of Django and Python.</p> Python version Django version 3.8 4.2 3.9 4.2 3.10 4.2, 5.0, 5.1 3.11 4.2, 5.0, 5.1 3.12 4.2, 5.0, 5.1 3.13 5.1"},{"location":"overview/contributing/","title":"Contributing","text":""},{"location":"overview/contributing/#bug-reports","title":"Bug reports","text":"<p>If you find a bug, please open an issue with detailed description of what happened.</p>"},{"location":"overview/contributing/#bug-fixes","title":"Bug fixes","text":"<p>If you found a fix for a bug or typo, go ahead and open a PR with a fix. We'll help you out with the rest!</p>"},{"location":"overview/contributing/#feature-requests","title":"Feature requests","text":"<p>For feature requests or suggestions, please open either a discussion or an issue.</p>"},{"location":"overview/contributing/#getting-involved","title":"Getting involved","text":"<p>django_components is still under active development, and there's much to build, so come aboard!</p>"},{"location":"overview/contributing/#sponsoring","title":"Sponsoring","text":"<p>Another way you can get involved is by donating to the development of django_components.</p>"},{"location":"overview/development/","title":"Development","text":""},{"location":"overview/development/#install-locally-and-run-the-tests","title":"Install locally and run the tests","text":"<p>Start by forking the project by clicking the Fork button up in the right corner in the GitHub. This makes a copy of the repository in your own name. Now you can clone this repository locally and start adding features:</p> <pre><code>git clone https://github.com/&lt;your GitHub username&gt;/django-components.git\ncd django-components\n</code></pre> <p>To quickly run the tests install the local dependencies by running:</p> <pre><code>pip install -r requirements-dev.txt\n</code></pre> <p>You also have to install this local django-components version. Use <code>-e</code> for editable mode so you don't have to re-install after every change:</p> <pre><code>pip install -e .\n</code></pre> <p>Now you can run the tests to make sure everything works as expected:</p> <pre><code>pytest\n</code></pre> <p>The library is also tested across many versions of Python and Django. To run tests that way:</p> <pre><code>pyenv install -s 3.8\npyenv install -s 3.9\npyenv install -s 3.10\npyenv install -s 3.11\npyenv install -s 3.12\npyenv install -s 3.13\npyenv local 3.8 3.9 3.10 3.11 3.12 3.13\ntox -p\n</code></pre> <p>To run tests for a specific Python version, use:</p> <pre><code>tox -e py38\n</code></pre> <p>NOTE: See the available environments in <code>tox.ini</code>.</p> <p>And to run only linters, use:</p> <pre><code>tox -e mypy,flake8,isort,black\n</code></pre>"},{"location":"overview/development/#running-playwright-tests","title":"Running Playwright tests","text":"<p>We use Playwright for end-to-end tests. You will therefore need to install Playwright to be able to run these tests.</p> <p>Luckily, Playwright makes it very easy:</p> <pre><code>pip install -r requirements-dev.txt\nplaywright install chromium --with-deps\n</code></pre> <p>After Playwright is ready, simply run the tests with <code>tox</code>:</p> <pre><code>tox\n</code></pre>"},{"location":"overview/development/#developing-against-live-django-app","title":"Developing against live Django app","text":"<p>How do you check that your changes to django-components project will work in an actual Django project?</p> <p>Use the sampleproject demo project to validate the changes:</p> <ol> <li> <p>Navigate to sampleproject directory:</p> <pre><code>cd sampleproject\n</code></pre> </li> <li> <p>Install dependencies from the requirements.txt file:</p> <pre><code>pip install -r requirements.txt\n</code></pre> </li> <li> <p>Link to your local version of django-components:</p> <pre><code>pip install -e ..\n</code></pre> <p>Note</p> <p>The path to the local version (in this case <code>..</code>) must point to the directory that has the <code>setup.py</code> file.</p> </li> <li> <p>Start Django server     <pre><code>python manage.py runserver\n</code></pre></p> </li> </ol> <p>Once the server is up, it should be available at http://127.0.0.1:8000.</p> <p>To display individual components, add them to the <code>urls.py</code>, like in the case of http://127.0.0.1:8000/greeting</p>"},{"location":"overview/development/#building-js-code","title":"Building JS code","text":"<p>django_components uses a bit of JS code to:</p> <ul> <li>Manage the loading of JS and CSS files used by the components</li> <li>Allow to pass data from Python to JS</li> </ul> <p>When you make changes to this JS code, you also need to compile it:</p> <ol> <li> <p>Make sure you are inside <code>src/django_components_js</code>:</p> <pre><code>cd src/django_components_js\n</code></pre> </li> <li> <p>Install the JS dependencies</p> <pre><code>npm install\n</code></pre> </li> <li> <p>Compile the JS/TS code:</p> <pre><code>python build.py\n</code></pre> <p>The script will combine all JS/TS code into a single <code>.js</code> file, minify it, and copy it to <code>django_components/static/django_components/django_components.min.js</code>.</p> </li> </ol>"},{"location":"overview/development/#packaging-and-publishing","title":"Packaging and publishing","text":"<p>To package the library into a distribution that can be published to PyPI, run:</p> <pre><code># Install pypa/build\npython -m pip install build --user\n# Build a binary wheel and a source tarball\npython -m build --sdist --wheel --outdir dist/ .\n</code></pre> <p>To publish the package to PyPI, use <code>twine</code> (See Python user guide):</p> <pre><code>twine upload --repository pypi dist/* -u __token__ -p &lt;PyPI_TOKEN&gt;\n</code></pre> <p>See the full workflow here.</p>"},{"location":"overview/development/#development-guides","title":"Development guides","text":"<p>Head over to Dev guides for a deep dive into how django_components' features are implemented.</p>"},{"location":"overview/installation/","title":"Installation","text":"<ol> <li> <p>Install <code>django_components</code> into your environment:</p> <pre><code>pip install django_components\n</code></pre> </li> <li> <p>Load <code>django_components</code> into Django by adding it into <code>INSTALLED_APPS</code> in in your settings file:</p> <pre><code>INSTALLED_APPS = [\n    ...,\n    'django_components',\n]\n</code></pre> </li> <li> <p><code>BASE_DIR</code> setting is required. Ensure that it is defined:</p> <pre><code>from pathlib import Path\n\nBASE_DIR = Path(__file__).resolve().parent.parent\n</code></pre> </li> <li> <p>Optional. Set <code>COMPONENTS.dirs</code>    and/or <code>COMPONENTS.app_dirs</code>    so django_components knows where to find component HTML, JS and CSS files:</p> <p>If <code>COMPONENTS.dirs</code> is omitted, django-components will by default look for a top-level <code>/components</code> directory, <code>{BASE_DIR}/components</code>.</p> <pre><code>from django_components import ComponentsSettings\n\nCOMPONENTS = ComponentsSettings(\n    dirs=[\n        ...,\n        Path(BASE_DIR) / \"components\",\n    ],\n)\n</code></pre> <p>In addition to <code>COMPONENTS.dirs</code>, django_components will also load components from app-level directories, such as <code>my-app/components/</code>. The directories within apps are configured with <code>COMPONENTS.app_dirs</code>, and the default is <code>[app]/components</code>.</p> <p>Note</p> <p>The input to <code>COMPONENTS.dirs</code> is the same as for <code>STATICFILES_DIRS</code>, and the paths must be full paths. See Django docs.</p> </li> <li> <p>Next, modify <code>TEMPLATES</code> section of settings.py as follows:</p> <ul> <li>Remove <code>'APP_DIRS': True,</code><ul> <li>NOTE: Instead of <code>APP_DIRS: True</code>, we will use   <code>django.template.loaders.app_directories.Loader</code>,   which has the same effect.</li> </ul> </li> <li>Add <code>loaders</code> to <code>OPTIONS</code> list and set it to following value:</li> </ul> <p>This allows Django to load component HTML files as Django templates.</p> <pre><code>TEMPLATES = [\n    {\n        ...,\n        'OPTIONS': {\n            'loaders':[(\n                'django.template.loaders.cached.Loader', [\n                    # Default Django loader\n                    'django.template.loaders.filesystem.Loader',\n                    # Including this is the same as APP_DIRS=True\n                    'django.template.loaders.app_directories.Loader',\n                    # Components loader\n                    'django_components.template_loader.Loader',\n                ]\n            )],\n        },\n    },\n]\n</code></pre> </li> </ol>"},{"location":"overview/installation/#adding-support-for-js-and-css","title":"Adding support for JS and CSS","text":"<p>If you want to use JS or CSS with components, you will need to:</p> <ol> <li> <p>Add <code>\"django_components.finders.ComponentsFileSystemFinder\"</code> to <code>STATICFILES_FINDERS</code> in your settings file.</p> <p>This allows Django to serve component JS and CSS as static files.</p> <pre><code>STATICFILES_FINDERS = [\n    # Default finders\n    \"django.contrib.staticfiles.finders.FileSystemFinder\",\n    \"django.contrib.staticfiles.finders.AppDirectoriesFinder\",\n    # Django components\n    \"django_components.finders.ComponentsFileSystemFinder\",\n]\n</code></pre> </li> <li> <p>Add <code>ComponentDependencyMiddleware</code>    to <code>MIDDLEWARE</code> setting.</p> <p>The middleware searches the outgoing HTML for all components that were rendered to generate the HTML, and adds the JS and CSS associated with those components.</p> <pre><code>MIDDLEWARE = [\n    ...\n    \"django_components.middleware.ComponentDependencyMiddleware\",\n]\n</code></pre> <p>Read more in Rendering JS/CSS dependencies.</p> </li> <li> <p>Add django-component's URL paths to your <code>urlpatterns</code>:</p> <pre><code>from django.urls import include, path\n\nurlpatterns = [\n    ...\n    path(\"\", include(\"django_components.urls\")),\n]\n</code></pre> </li> <li> <p>Optional. If you want to change where the JS and CSS is rendered, use     <code>{% component_js_dependencies %}</code>     and <code>{% component_css_dependencies %}</code>.</p> <p>By default, the JS <code>&lt;script&gt;</code> and CSS <code>&lt;link&gt;</code> tags are automatically inserted into the HTML (See JS and CSS output locations).</p> <pre><code>&lt;!doctype html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    ...\n    {% component_css_dependencies %}\n  &lt;/head&gt;\n  &lt;body&gt;\n    ...\n    {% component_js_dependencies %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre> </li> <li> <p>Optional. By default, components' JS and CSS files are cached in memory.</p> <p>If you want to change the cache backend, set the <code>COMPONENTS.cache</code> setting.</p> <p>Read more in Caching.</p> </li> </ol>"},{"location":"overview/installation/#optional","title":"Optional","text":""},{"location":"overview/installation/#builtin-template-tags","title":"Builtin template tags","text":"<p>To avoid loading the app in each template using <code>{% load component_tags %}</code>, you can add the tag as a 'builtin' in settings.py</p> <pre><code>TEMPLATES = [\n    {\n        ...,\n        'OPTIONS': {\n            'builtins': [\n                'django_components.templatetags.component_tags',\n            ]\n        },\n    },\n]\n</code></pre> <p>Now you're all set! Read on to find out how to build your first component.</p>"},{"location":"overview/license/","title":"License","text":"<p>MIT License</p> <p>Copyright (c) 2019 Emil Stenstr\u00f6m</p> <p>Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p> <p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p> <p>THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>"},{"location":"overview/performance/","title":"Performance","text":"<p>We track the performance of <code>django-components</code> using ASV.</p> <p>See the benchmarks dashboard.</p>"},{"location":"overview/security_notes/","title":"Security notes \ud83d\udea8","text":"<p>It is strongly recommended to read this section before using django-components in production.</p>"},{"location":"overview/security_notes/#static-files","title":"Static files","text":"<p>TL;DR: No action needed from v0.100 onwards. Before v0.100, use <code>safer_staticfiles</code> to avoid exposing backend logic.</p> <p>Components can be organized however you prefer. That said, our prefered way is to keep the files of a component close together by bundling them in the same directory.</p> <p>This means that files containing backend logic, such as Python modules and HTML templates, live in the same directory as static files, e.g. JS and CSS.</p> <p>From v0.100 onwards, we keep component files (as defined by <code>COMPONENTS.dirs</code> and <code>COMPONENTS.app_dirs</code>) separate from the rest of the static files (defined by <code>STATICFILES_DIRS</code>). That way, the Python and HTML files are NOT exposed by the server. Only the static JS, CSS, and other common formats.</p> <p>Note</p> <p>If you need to expose different file formats, you can configure these with <code>COMPONENTS.static_files_allowed</code> and <code>COMPONENTS.static_files_forbidden</code>.</p>"},{"location":"overview/security_notes/#static-files-prior-to-v0100","title":"Static files prior to v0.100","text":"<p>Prior to v0.100, if your were using django.contrib.staticfiles to collect static files, no distinction was made between the different kinds of files.</p> <p>As a result, your Python code and templates may inadvertently become available on your static file server. You probably don't want this, as parts of your backend logic will be exposed, posing a potential security vulnerability.</p> <p>From v0.27 until v0.100, django-components shipped with an additional installable app django_components.safer_staticfiles. It was a drop-in replacement for django.contrib.staticfiles. Its behavior is 100% identical except it ignores <code>.py</code> and <code>.html</code> files, meaning these will not end up on your static files server.</p> <p>To use it, add it to <code>INSTALLED_APPS</code> and remove django.contrib.staticfiles.</p> <pre><code>INSTALLED_APPS = [\n    # 'django.contrib.staticfiles',   # &lt;-- REMOVE\n    'django_components',\n    'django_components.safer_staticfiles'  # &lt;-- ADD\n]\n</code></pre> <p>If you are on an pre-v0.27 version of django-components, your alternatives are:</p> <ul> <li>a) passing <code>--ignore &lt;pattern&gt;</code> options to the collecstatic CLI command,</li> <li>b) defining a subclass of StaticFilesConfig.</li> </ul> <p>Both routes are described in the official docs of the staticfiles app.</p> <p>Note that <code>safer_staticfiles</code> excludes the <code>.py</code> and <code>.html</code> files for collectstatic command:</p> <pre><code>python manage.py collectstatic\n</code></pre> <p>but it is ignored on the development server:</p> <pre><code>python manage.py runserver\n</code></pre> <p>For a step-by-step guide on deploying production server with static files, see the demo project.</p> <p>See the older versions of the sampleproject for a setup with pre-v0.100 version.</p>"},{"location":"overview/welcome/","title":"Welcome to Django Components","text":"<p><code>django-components</code> combines Django's templating system with the modularity seen in modern frontend frameworks like Vue or React.</p> <p>With <code>django-components</code> you can support Django projects small and large without leaving the Django ecosystem.</p>"},{"location":"overview/welcome/#quickstart","title":"Quickstart","text":"<p>A component in django-components can be as simple as a Django template and Python code to declare the component:</p> components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n</code></pre> <p>Or a combination of Django template, Python, CSS, and Javascript:</p> components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> components/calendar/calendar.css<pre><code>.calendar {\n  width: 200px;\n  background: pink;\n}\n</code></pre> components/calendar/calendar.js<pre><code>document.querySelector(\".calendar\").onclick = () =&gt; {\n  alert(\"Clicked calendar!\");\n};\n</code></pre> components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    def get_context_data(self, date):\n        return {\"date\": date}\n</code></pre> <p>Use the component like this:</p> <pre><code>{% component \"calendar\" date=\"2024-11-06\" %}{% endcomponent %}\n</code></pre> <p>And this is what gets rendered:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n  Today's date is &lt;span&gt;2024-11-06&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>Read on to learn about all the exciting details and configuration possibilities!</p> <p>(If you instead prefer to jump right into the code, check out the example project)</p>"},{"location":"overview/welcome/#features","title":"Features","text":""},{"location":"overview/welcome/#modern-and-modular-ui","title":"Modern and modular UI","text":"<ul> <li>Create self-contained, reusable UI elements.</li> <li>Each component can include its own HTML, CSS, and JS, or additional third-party JS and CSS.</li> <li>HTML, CSS, and JS can be defined on the component class, or loaded from files.</li> </ul> <pre><code>from django_components import Component\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template = \"\"\"\n        &lt;div class=\"calendar\"&gt;\n            Today's date is\n            &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css = \"\"\"\n        .calendar {\n            width: 200px;\n            background: pink;\n        }\n    \"\"\"\n\n    js = \"\"\"\n        document.querySelector(\".calendar\")\n            .addEventListener(\"click\", () =&gt; {\n                alert(\"Clicked calendar!\");\n            });\n    \"\"\"\n\n    # Additional JS and CSS\n    class Media:\n        js = [\"https://cdn.jsdelivr.net/npm/htmx.org@2.1.1/dist/htmx.min.js\"]\n        css = [\"bootstrap/dist/css/bootstrap.min.css\"]\n\n    # Variables available in the template\n    def get_context_data(self, date):\n        return {\n            \"date\": date\n        }\n</code></pre>"},{"location":"overview/welcome/#composition-with-slots","title":"Composition with slots","text":"<ul> <li>Render components inside templates with <code>{% component %}</code> tag.</li> <li>Compose them with <code>{% slot %}</code> and <code>{% fill %}</code> tags.</li> <li>Vue-like slot system, including scoped slots.</li> </ul> <pre><code>{% component \"Layout\"\n    bookmarks=bookmarks\n    breadcrumbs=breadcrumbs\n%}\n    {% fill \"header\" %}\n        &lt;div class=\"flex justify-between gap-x-12\"&gt;\n            &lt;div class=\"prose\"&gt;\n                &lt;h3&gt;{{ project.name }}&lt;/h3&gt;\n            &lt;/div&gt;\n            &lt;div class=\"font-semibold text-gray-500\"&gt;\n                {{ project.start_date }} - {{ project.end_date }}\n            &lt;/div&gt;\n        &lt;/div&gt;\n    {% endfill %}\n\n    {# Access data passed to `{% slot %}` with `data` #}\n    {% fill \"tabs\" data=\"tabs_data\" %}\n        {% component \"TabItem\" header=\"Project Info\" %}\n            {% component \"ProjectInfo\"\n                project=project\n                project_tags=project_tags\n                attrs:class=\"py-5\"\n                attrs:width=tabs_data.width\n            / %}\n        {% endcomponent %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"overview/welcome/#extended-template-tags","title":"Extended template tags","text":"<p><code>django-components</code> extends Django's template tags syntax with:</p> <ul> <li>Literal lists and dictionaries in template tags</li> <li>Self-closing tags <code>{% mytag / %}</code></li> <li>Multi-line template tags</li> <li>Spread operator <code>...</code> to dynamically pass args or kwargs into the template tag</li> <li>Nested template tags like <code>\"{{ first_name }} {{ last_name }}\"</code></li> <li>Flat definition of dictionary keys <code>attr:key=val</code></li> </ul> <pre><code>{% component \"table\"\n    ...default_attrs\n    title=\"Friend list for {{ user.name }}\"\n    headers=[\"Name\", \"Age\", \"Email\"]\n    data=[\n        {\n            \"name\": \"John\"|upper,\n            \"age\": 30|add:1,\n            \"email\": \"john@example.com\",\n            \"hobbies\": [\"reading\"],\n        },\n        {\n            \"name\": \"Jane\"|upper,\n            \"age\": 25|add:1,\n            \"email\": \"jane@example.com\",\n            \"hobbies\": [\"reading\", \"coding\"],\n        },\n    ],\n    attrs:class=\"py-4 ma-2 border-2 border-gray-300 rounded-md\"\n/ %}\n</code></pre>"},{"location":"overview/welcome/#html-fragment-support","title":"HTML fragment support","text":"<p><code>django-components</code> makes intergration with HTMX, AlpineJS or jQuery easy by allowing components to be rendered as HTML fragments:</p> <ul> <li> <p>Components's JS and CSS is loaded automatically when the fragment is inserted into the DOM.</p> </li> <li> <p>Expose components as views with <code>get</code>, <code>post</code>, <code>put</code>, <code>patch</code>, <code>delete</code> methods</p> </li> </ul> <pre><code># components/calendar/calendar.py\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n\n    def get(self, request, *args, **kwargs):\n        page = request.GET.get(\"page\", 1)\n        return self.render_to_response(\n            kwargs={\n                \"page\": page,\n            }\n        )\n\n    def get_context_data(self, page):\n        return {\n            \"page\": page,\n        }\n\n# urls.py\npath(\"calendar/\", Calendar.as_view()),\n</code></pre>"},{"location":"overview/welcome/#type-hints","title":"Type hints","text":"<p>Opt-in to type hints by defining types for component's args, kwargs, slots, and more:</p> <pre><code>from typing import NotRequired, Tuple, TypedDict, SlotContent, SlotFunc\n\nButtonArgs = Tuple[int, str]\n\nclass ButtonKwargs(TypedDict):\n    variable: str\n    another: int\n    maybe_var: NotRequired[int] # May be omitted\n\nclass ButtonData(TypedDict):\n    variable: str\n\nclass ButtonSlots(TypedDict):\n    my_slot: NotRequired[SlotFunc]\n    another_slot: SlotContent\n\nButtonType = Component[ButtonArgs, ButtonKwargs, ButtonSlots, ButtonData, JsData, CssData]\n\nclass Button(ButtonType):\n    def get_context_data(self, *args, **kwargs):\n        self.input.args[0]  # int\n        self.input.kwargs[\"variable\"]  # str\n        self.input.slots[\"my_slot\"]  # SlotFunc[MySlotData]\n\n        return {}  # Error: Key \"variable\" is missing\n</code></pre> <p>When you then call <code>Button.render()</code> or <code>Button.render_to_response()</code>, you will get type hints:</p> <pre><code>Button.render(\n    # Error: First arg must be `int`, got `float`\n    args=(1.25, \"abc\"),\n    # Error: Key \"another\" is missing\n    kwargs={\n        \"variable\": \"text\",\n    },\n)\n</code></pre>"},{"location":"overview/welcome/#extensions","title":"Extensions","text":"<p>Django-components functionality can be extended with \"extensions\". Extensions allow for powerful customization and integrations. They can:</p> <ul> <li>Tap into lifecycle events, such as when a component is created, deleted, or registered.</li> <li>Add new attributes and methods to the components under an extension-specific nested class.</li> </ul> <p>Some of the planned extensions include:</p> <ul> <li>Caching</li> <li>AlpineJS integration</li> <li>Storybook integration</li> <li>Pydantic validation</li> <li>Component-level benchmarking with asv</li> </ul>"},{"location":"overview/welcome/#simple-testing","title":"Simple testing","text":"<ul> <li>Write tests for components with <code>@djc_test</code> decorator.</li> <li>The decorator manages global state, ensuring that tests don't leak.</li> <li>If using <code>pytest</code>, the decorator allows you to parametrize Django or Components settings.</li> <li>The decorator also serves as a stand-in for Django's <code>@override_settings</code>.</li> </ul> <pre><code>from djc_test import djc_test\n\nfrom components.my_component import MyTable\n\n@djc_test\ndef test_my_table():\n    rendered = MyTable.render(\n        kwargs={\n            \"title\": \"My table\",\n        },\n    )\n    assert rendered == \"&lt;table&gt;My table&lt;/table&gt;\"\n</code></pre>"},{"location":"overview/welcome/#handle-large-projects-with-ease","title":"Handle large projects with ease","text":"<ul> <li>Components can be infinitely nested.</li> <li>(Soon) Optimize performance with component-level caching</li> </ul>"},{"location":"overview/welcome/#debugging-features","title":"Debugging features","text":"<ul> <li>Visual component inspection: Highlight components and slots directly in your browser.</li> <li>Detailed tracing logs to supply AI-agents with context: The logs include component and slot names and IDs, and their position in the tree.</li> </ul>"},{"location":"overview/welcome/#sharing-components","title":"Sharing components","text":"<ul> <li>Install and use third-party components from PyPI</li> <li>Or publish your own \"component registry\"</li> <li> <p>Highly customizable - Choose how the components are called in the template (and more):</p> <pre><code>{% component \"calendar\" date=\"2024-11-06\" %}\n{% endcomponent %}\n\n{% calendar date=\"2024-11-06\" %}\n{% endcalendar %}\n</code></pre> </li> </ul>"},{"location":"overview/welcome/#other-features","title":"Other features","text":"<ul> <li>Vue-like provide / inject system</li> <li>Format HTML attributes with <code>{% html_attrs %}</code></li> </ul>"},{"location":"overview/welcome/#performance","title":"Performance","text":"<p>Our aim is to be at least as fast as Django templates.</p> <p>As of <code>0.130</code>, <code>django-components</code> is ~4x slower than Django templates.</p> Render time django 68.9\u00b10.6ms django-components 259\u00b14ms <p>See the full performance breakdown for more information.</p>"},{"location":"overview/welcome/#release-notes","title":"Release notes","text":"<p>Read the Release Notes to see the latest features and fixes.</p>"},{"location":"overview/welcome/#community-examples","title":"Community examples","text":"<p>One of our goals with <code>django-components</code> is to make it easy to share components between projects. Head over to the Community examples to see some examples.</p>"},{"location":"overview/welcome/#contributing-and-development","title":"Contributing and development","text":"<p>Get involved or sponsor this project - See here</p> <p>Running django-components locally for development - See here</p>"},{"location":"reference/api/","title":"API","text":""},{"location":"reference/api/#api","title":"API","text":""},{"location":"reference/api/#django_components.BaseNode","title":"BaseNode","text":"<pre><code>BaseNode(\n    params: List[TagAttr], flags: Optional[Dict[str, bool]] = None, nodelist: Optional[NodeList] = None, node_id: Optional[str] = None\n)\n</code></pre> <p>Bases: <code>django.template.base.Node</code></p> <p>See source code</p> <p>Node class for all django-components custom template tags.</p> <p>This class has a dual role:</p> <ol> <li> <p>It declares how a particular template tag should be parsed - By setting the    <code>tag</code>,    <code>end_tag</code>,    and <code>allowed_flags</code>    attributes:</p> <pre><code>class SlotNode(BaseNode):\n    tag = \"slot\"\n    end_tag = \"endslot\"\n    allowed_flags = [\"required\"]\n</code></pre> <p>This will allow the template tag <code>{% slot %}</code> to be used like this:</p> <pre><code>{% slot required %} ... {% endslot %}\n</code></pre> </li> <li> <p>The <code>render</code> method is     the actual implementation of the template tag.</p> <p>This is where the tag's logic is implemented:</p> <pre><code>class MyNode(BaseNode):\n    tag = \"mynode\"\n\n    def render(self, context: Context, name: str, **kwargs: Any) -&gt; str:\n        return f\"Hello, {name}!\"\n</code></pre> <p>This will allow the template tag <code>{% mynode %}</code> to be used like this:</p> <pre><code>{% mynode name=\"John\" %}\n</code></pre> </li> </ol> <p>The template tag accepts parameters as defined on the <code>render</code> method's signature.</p> <p>For more info, see <code>BaseNode.render()</code>.</p> <p>Methods:</p> <ul> <li> <code>parse</code>             \u2013              </li> <li> <code>register</code>             \u2013              </li> <li> <code>render</code>             \u2013              </li> <li> <code>unregister</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>active_flags</code>               (<code>List[str]</code>)           \u2013            </li> <li> <code>allowed_flags</code>               (<code>Optional[List[str]]</code>)           \u2013            </li> <li> <code>end_tag</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>flags</code>           \u2013            </li> <li> <code>node_id</code>           \u2013            </li> <li> <code>nodelist</code>           \u2013            </li> <li> <code>params</code>           \u2013            </li> <li> <code>tag</code>               (<code>str</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.BaseNode.active_flags","title":"active_flags  <code>property</code>","text":"<pre><code>active_flags: List[str]\n</code></pre> <p>See source code</p> <p>Flags that were set for this specific instance.</p>"},{"location":"reference/api/#django_components.BaseNode.allowed_flags","title":"allowed_flags  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>allowed_flags: Optional[List[str]] = None\n</code></pre> <p>See source code</p> <p>The allowed flags for this tag.</p> <p>E.g. <code>[\"required\"]</code> will allow this tag to be used like <code>{% slot required %}</code>.</p>"},{"location":"reference/api/#django_components.BaseNode.end_tag","title":"end_tag  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>end_tag: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The end tag name.</p> <p>E.g. <code>\"endcomponent\"</code> or <code>\"endslot\"</code> will make this class match template tags <code>{% endcomponent %}</code> or <code>{% endslot %}</code>.</p> <p>If not set, then this template tag has no end tag.</p> <p>So instead of <code>{% component %} ... {% endcomponent %}</code>, you'd use only <code>{% component %}</code>.</p>"},{"location":"reference/api/#django_components.BaseNode.flags","title":"flags  <code>instance-attribute</code>","text":"<pre><code>flags = flags or {flag: Falsefor flag in allowed_flags or []}\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.node_id","title":"node_id  <code>instance-attribute</code>","text":"<pre><code>node_id = node_id or gen_id()\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.nodelist","title":"nodelist  <code>instance-attribute</code>","text":"<pre><code>nodelist = nodelist or NodeList()\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.params","title":"params  <code>instance-attribute</code>","text":"<pre><code>params = params\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.tag","title":"tag  <code>instance-attribute</code>","text":"<pre><code>tag: str\n</code></pre> <p>See source code</p> <p>The tag name.</p> <p>E.g. <code>\"component\"</code> or <code>\"slot\"</code> will make this class match template tags <code>{% component %}</code> or <code>{% slot %}</code>.</p>"},{"location":"reference/api/#django_components.BaseNode.parse","title":"parse  <code>classmethod</code>","text":"<pre><code>parse(parser: Parser, token: Token, **kwargs: Any) -&gt; BaseNode\n</code></pre> <p>See source code</p> <p>This function is what is passed to Django's <code>Library.tag()</code> when registering the tag.</p> <p>In other words, this method is called by Django's template parser when we encounter a tag that matches this node's tag, e.g. <code>{% component %}</code> or <code>{% slot %}</code>.</p> <p>To register the tag, you can use <code>BaseNode.register()</code>.</p>"},{"location":"reference/api/#django_components.BaseNode.register","title":"register  <code>classmethod</code>","text":"<pre><code>register(library: Library) -&gt; None\n</code></pre> <p>See source code</p> <p>A convenience method for registering the tag with the given library.</p> <pre><code>class MyNode(BaseNode):\n    tag = \"mynode\"\n\nMyNode.register(library)\n</code></pre> <p>Allows you to then use the node in templates like so:</p> <pre><code>{% load mylibrary %}\n{% mynode %}\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.render","title":"render","text":"<pre><code>render(context: Context, *args: Any, **kwargs: Any) -&gt; str\n</code></pre> <p>See source code</p> <p>Render the node. This method is meant to be overridden by subclasses.</p> <p>The signature of this function decides what input the template tag accepts.</p> <p>The <code>render()</code> method MUST accept a <code>context</code> argument. Any arguments after that will be part of the tag's input parameters.</p> <p>So if you define a <code>render</code> method like this:</p> <pre><code>def render(self, context: Context, name: str, **kwargs: Any) -&gt; str:\n</code></pre> <p>Then the tag will require the <code>name</code> parameter, and accept any extra keyword arguments:</p> <pre><code>{% component name=\"John\" age=20 %}\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.unregister","title":"unregister  <code>classmethod</code>","text":"<pre><code>unregister(library: Library) -&gt; None\n</code></pre> <p>See source code</p> <p>Unregisters the node from the given library.</p>"},{"location":"reference/api/#django_components.CommandArg","title":"CommandArg  <code>dataclass</code>","text":"<pre><code>CommandArg(\n    name_or_flags: Union[str, Sequence[str]],\n    action: Optional[Union[CommandLiteralAction, Action]] = None,\n    nargs: Optional[Union[int, Literal[\"*\", \"+\", \"?\"]]] = None,\n    const: Any = None,\n    default: Any = None,\n    type: Optional[Union[Type, Callable[[str], Any]]] = None,\n    choices: Optional[Sequence[Any]] = None,\n    required: Optional[bool] = None,\n    help: Optional[str] = None,\n    metavar: Optional[str] = None,\n    dest: Optional[str] = None,\n    version: Optional[str] = None,\n    deprecated: Optional[bool] = None,\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Define a single positional argument or an option for a command.</p> <p>Fields on this class correspond to the arguments for <code>ArgumentParser.add_argument()</code></p> <p>Methods:</p> <ul> <li> <code>asdict</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>action</code>               (<code>Optional[Union[CommandLiteralAction, Action]]</code>)           \u2013            </li> <li> <code>choices</code>               (<code>Optional[Sequence[Any]]</code>)           \u2013            </li> <li> <code>const</code>               (<code>Any</code>)           \u2013            </li> <li> <code>default</code>               (<code>Any</code>)           \u2013            </li> <li> <code>deprecated</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>dest</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>help</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>metavar</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>name_or_flags</code>               (<code>Union[str, Sequence[str]]</code>)           \u2013            </li> <li> <code>nargs</code>               (<code>Optional[Union[int, Literal['*', '+', '?']]]</code>)           \u2013            </li> <li> <code>required</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>type</code>               (<code>Optional[Union[Type, Callable[[str], Any]]]</code>)           \u2013            </li> <li> <code>version</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.CommandArg.action","title":"action  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>action: Optional[Union[CommandLiteralAction, Action]] = None\n</code></pre> <p>See source code</p> <p>The basic type of action to be taken when this argument is encountered at the command line.</p>"},{"location":"reference/api/#django_components.CommandArg.choices","title":"choices  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>choices: Optional[Sequence[Any]] = None\n</code></pre> <p>See source code</p> <p>A sequence of the allowable values for the argument.</p>"},{"location":"reference/api/#django_components.CommandArg.const","title":"const  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>const: Any = None\n</code></pre> <p>See source code</p> <p>A constant value required by some action and nargs selections.</p>"},{"location":"reference/api/#django_components.CommandArg.default","title":"default  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>default: Any = None\n</code></pre> <p>See source code</p> <p>The value produced if the argument is absent from the command line and if it is absent from the namespace object.</p>"},{"location":"reference/api/#django_components.CommandArg.deprecated","title":"deprecated  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>deprecated: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Whether or not use of the argument is deprecated.</p> <p>NOTE: This is supported only in Python 3.13+</p>"},{"location":"reference/api/#django_components.CommandArg.dest","title":"dest  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>dest: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The name of the attribute to be added to the object returned by parse_args().</p>"},{"location":"reference/api/#django_components.CommandArg.help","title":"help  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>help: Optional[str] = None\n</code></pre> <p>See source code</p> <p>A brief description of what the argument does.</p>"},{"location":"reference/api/#django_components.CommandArg.metavar","title":"metavar  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>metavar: Optional[str] = None\n</code></pre> <p>See source code</p> <p>A name for the argument in usage messages.</p>"},{"location":"reference/api/#django_components.CommandArg.name_or_flags","title":"name_or_flags  <code>instance-attribute</code>","text":"<pre><code>name_or_flags: Union[str, Sequence[str]]\n</code></pre> <p>See source code</p> <p>Either a name or a list of option strings, e.g. 'foo' or '-f', '--foo'.</p>"},{"location":"reference/api/#django_components.CommandArg.nargs","title":"nargs  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>nargs: Optional[Union[int, Literal['*', '+', '?']]] = None\n</code></pre> <p>See source code</p> <p>The number of command-line arguments that should be consumed.</p>"},{"location":"reference/api/#django_components.CommandArg.required","title":"required  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>required: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Whether or not the command-line option may be omitted (optionals only).</p>"},{"location":"reference/api/#django_components.CommandArg.type","title":"type  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>type: Optional[Union[Type, Callable[[str], Any]]] = None\n</code></pre> <p>See source code</p> <p>The type to which the command-line argument should be converted.</p>"},{"location":"reference/api/#django_components.CommandArg.version","title":"version  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>version: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The version string to be added to the object returned by parse_args().</p> <p>MUST be used with <code>action='version'</code>.</p> <p>See https://docs.python.org/3/library/argparse.html#action</p>"},{"location":"reference/api/#django_components.CommandArg.asdict","title":"asdict","text":"<pre><code>asdict() -&gt; dict\n</code></pre> <p>See source code</p> <p>Convert the dataclass to a dictionary, stripping out fields with <code>None</code> values</p>"},{"location":"reference/api/#django_components.CommandArgGroup","title":"CommandArgGroup  <code>dataclass</code>","text":"<pre><code>CommandArgGroup(title: Optional[str] = None, description: Optional[str] = None, arguments: Sequence[CommandArg] = ())\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Define a group of arguments for a command.</p> <p>Fields on this class correspond to the arguments for <code>ArgumentParser.add_argument_group()</code></p> <p>Methods:</p> <ul> <li> <code>asdict</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>arguments</code>               (<code>Sequence[CommandArg]</code>)           \u2013            </li> <li> <code>description</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>title</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.CommandArgGroup.arguments","title":"arguments  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>arguments: Sequence[CommandArg] = ()\n</code></pre>"},{"location":"reference/api/#django_components.CommandArgGroup.description","title":"description  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>description: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Description for the argument group in help output, by default None</p>"},{"location":"reference/api/#django_components.CommandArgGroup.title","title":"title  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>title: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Title for the argument group in help output; by default \u201cpositional arguments\u201d if description is provided, otherwise uses title for positional arguments.</p>"},{"location":"reference/api/#django_components.CommandArgGroup.asdict","title":"asdict","text":"<pre><code>asdict() -&gt; dict\n</code></pre> <p>See source code</p> <p>Convert the dataclass to a dictionary, stripping out fields with <code>None</code> values</p>"},{"location":"reference/api/#django_components.CommandHandler","title":"CommandHandler","text":""},{"location":"reference/api/#django_components.CommandLiteralAction","title":"CommandLiteralAction  <code>module-attribute</code>","text":"<pre><code>CommandLiteralAction = Literal['append', 'append_const', 'count', 'extend', 'store', 'store_const', 'store_true', 'store_false', 'version']\n</code></pre> <p>See source code</p> <p>The basic type of action to be taken when this argument is encountered at the command line.</p> <p>This is a subset of the values for <code>action</code> in <code>ArgumentParser.add_argument()</code>.</p>"},{"location":"reference/api/#django_components.CommandParserInput","title":"CommandParserInput  <code>dataclass</code>","text":"<pre><code>CommandParserInput(\n    prog: Optional[str] = None,\n    usage: Optional[str] = None,\n    description: Optional[str] = None,\n    epilog: Optional[str] = None,\n    parents: Optional[Sequence[ArgumentParser]] = None,\n    formatter_class: Optional[Type[_FormatterClass]] = None,\n    prefix_chars: Optional[str] = None,\n    fromfile_prefix_chars: Optional[str] = None,\n    argument_default: Optional[Any] = None,\n    conflict_handler: Optional[str] = None,\n    add_help: Optional[bool] = None,\n    allow_abbrev: Optional[bool] = None,\n    exit_on_error: Optional[bool] = None,\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Typing for the input to the <code>ArgumentParser</code> constructor.</p> <p>Methods:</p> <ul> <li> <code>asdict</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>add_help</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>allow_abbrev</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>argument_default</code>               (<code>Optional[Any]</code>)           \u2013            </li> <li> <code>conflict_handler</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>description</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>epilog</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>exit_on_error</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>formatter_class</code>               (<code>Optional[Type[_FormatterClass]]</code>)           \u2013            </li> <li> <code>fromfile_prefix_chars</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>parents</code>               (<code>Optional[Sequence[ArgumentParser]]</code>)           \u2013            </li> <li> <code>prefix_chars</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>prog</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>usage</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.CommandParserInput.add_help","title":"add_help  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>add_help: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Add a -h/--help option to the parser (default: <code>True</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.allow_abbrev","title":"allow_abbrev  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>allow_abbrev: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Allows long options to be abbreviated if the abbreviation is unambiguous. (default: <code>True</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.argument_default","title":"argument_default  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>argument_default: Optional[Any] = None\n</code></pre> <p>See source code</p> <p>The global default value for arguments (default: <code>None</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.conflict_handler","title":"conflict_handler  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>conflict_handler: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The strategy for resolving conflicting optionals (usually unnecessary)</p>"},{"location":"reference/api/#django_components.CommandParserInput.description","title":"description  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>description: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Text to display before the argument help (by default, no text)</p>"},{"location":"reference/api/#django_components.CommandParserInput.epilog","title":"epilog  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>epilog: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Text to display after the argument help (by default, no text)</p>"},{"location":"reference/api/#django_components.CommandParserInput.exit_on_error","title":"exit_on_error  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>exit_on_error: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Determines whether or not ArgumentParser exits with error info when an error occurs. (default: <code>True</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.formatter_class","title":"formatter_class  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>formatter_class: Optional[Type[_FormatterClass]] = None\n</code></pre> <p>See source code</p> <p>A class for customizing the help output</p>"},{"location":"reference/api/#django_components.CommandParserInput.fromfile_prefix_chars","title":"fromfile_prefix_chars  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>fromfile_prefix_chars: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The set of characters that prefix files from which additional arguments should be read (default: <code>None</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.parents","title":"parents  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>parents: Optional[Sequence[ArgumentParser]] = None\n</code></pre> <p>See source code</p> <p>A list of ArgumentParser objects whose arguments should also be included</p>"},{"location":"reference/api/#django_components.CommandParserInput.prefix_chars","title":"prefix_chars  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>prefix_chars: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The set of characters that prefix optional arguments (default: \u2018-\u2018)</p>"},{"location":"reference/api/#django_components.CommandParserInput.prog","title":"prog  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>prog: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The name of the program (default: <code>os.path.basename(sys.argv[0])</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.usage","title":"usage  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>usage: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The string describing the program usage (default: generated from arguments added to parser)</p>"},{"location":"reference/api/#django_components.CommandParserInput.asdict","title":"asdict","text":"<pre><code>asdict() -&gt; dict\n</code></pre> <p>See source code</p> <p>Convert the dataclass to a dictionary, stripping out fields with <code>None</code> values</p>"},{"location":"reference/api/#django_components.CommandSubcommand","title":"CommandSubcommand  <code>dataclass</code>","text":"<pre><code>CommandSubcommand(\n    title: Optional[str] = None,\n    description: Optional[str] = None,\n    prog: Optional[str] = None,\n    parser_class: Optional[Type[ArgumentParser]] = None,\n    action: Optional[Union[CommandLiteralAction, Action]] = None,\n    dest: Optional[str] = None,\n    required: Optional[bool] = None,\n    help: Optional[str] = None,\n    metavar: Optional[str] = None,\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Define a subcommand for a command.</p> <p>Fields on this class correspond to the arguments for <code>ArgumentParser.add_subparsers.add_parser()</code></p> <p>Methods:</p> <ul> <li> <code>asdict</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>action</code>               (<code>Optional[Union[CommandLiteralAction, Action]]</code>)           \u2013            </li> <li> <code>description</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>dest</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>help</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>metavar</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>parser_class</code>               (<code>Optional[Type[ArgumentParser]]</code>)           \u2013            </li> <li> <code>prog</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>required</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>title</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.CommandSubcommand.action","title":"action  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>action: Optional[Union[CommandLiteralAction, Action]] = None\n</code></pre> <p>See source code</p> <p>The basic type of action to be taken when this argument is encountered at the command line.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.description","title":"description  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>description: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Description for the sub-parser group in help output, by default <code>None</code>.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.dest","title":"dest  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>dest: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the attribute under which sub-command name will be stored; by default <code>None</code> and no value is stored.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.help","title":"help  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>help: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Help for sub-parser group in help output, by default <code>None</code>.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.metavar","title":"metavar  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>metavar: Optional[str] = None\n</code></pre> <p>See source code</p> <p>String presenting available subcommands in help; by default it is None and presents subcommands in form <code>{cmd1, cmd2, ..}</code>.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.parser_class","title":"parser_class  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>parser_class: Optional[Type[ArgumentParser]] = None\n</code></pre> <p>See source code</p> <p>Class which will be used to create sub-parser instances, by default the class of the current parser (e.g. <code>ArgumentParser</code>).</p>"},{"location":"reference/api/#django_components.CommandSubcommand.prog","title":"prog  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>prog: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Usage information that will be displayed with sub-command help, by default the name of the program and any positional arguments before the subparser argument.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.required","title":"required  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>required: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Whether or not a subcommand must be provided, by default <code>False</code> (added in 3.7)</p>"},{"location":"reference/api/#django_components.CommandSubcommand.title","title":"title  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>title: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Title for the sub-parser group in help output; by default \u201csubcommands\u201d if description is provided, otherwise uses title for positional arguments.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.asdict","title":"asdict","text":"<pre><code>asdict() -&gt; dict\n</code></pre> <p>See source code</p> <p>Convert the dataclass to a dictionary, stripping out fields with <code>None</code> values</p>"},{"location":"reference/api/#django_components.Component","title":"Component","text":"<pre><code>Component(registered_name: Optional[str] = None, outer_context: Optional[Context] = None, registry: Optional[ComponentRegistry] = None)\n</code></pre> <p>Methods:</p> <ul> <li> <code>as_view</code>             \u2013              </li> <li> <code>get_context_data</code>             \u2013              </li> <li> <code>get_template</code>             \u2013              </li> <li> <code>get_template_name</code>             \u2013              </li> <li> <code>inject</code>             \u2013              </li> <li> <code>on_render_after</code>             \u2013              </li> <li> <code>on_render_before</code>             \u2013              </li> <li> <code>render</code>             \u2013              </li> <li> <code>render_to_response</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>Media</code>               (<code>Optional[Type[ComponentMediaInput]]</code>)           \u2013            </li> <li> <code>context_processors_data</code>               (<code>Dict</code>)           \u2013            </li> <li> <code>css</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>css_file</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>id</code>               (<code>str</code>)           \u2013            </li> <li> <code>input</code>               (<code>RenderInput[ArgsType, KwargsType, SlotsType]</code>)           \u2013            </li> <li> <code>is_filled</code>               (<code>SlotIsFilled</code>)           \u2013            </li> <li> <code>js</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>js_file</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>media</code>               (<code>Optional[Media]</code>)           \u2013            </li> <li> <code>media_class</code>               (<code>Type[Media]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>outer_context</code>               (<code>Optional[Context]</code>)           \u2013            </li> <li> <code>registered_name</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>registry</code>           \u2013            </li> <li> <code>request</code>               (<code>Optional[HttpRequest]</code>)           \u2013            </li> <li> <code>response_class</code>           \u2013            </li> <li> <code>template</code>               (<code>Optional[Union[str, Template]]</code>)           \u2013            </li> <li> <code>template_file</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>template_name</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.Component.Media","title":"Media  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>Media: Optional[Type[ComponentMediaInput]] = None\n</code></pre> <p>See source code</p> <p>Defines JS and CSS media files associated with this component.</p> <p>This <code>Media</code> class behaves similarly to Django's Media class:</p> <ul> <li>Paths are generally handled as static file paths, and resolved URLs are rendered to HTML with   <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A path that starts with <code>http</code>, <code>https</code>, or <code>/</code> is considered a URL, skipping the static file resolution.   This path is still rendered to HTML with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A <code>SafeString</code> (with <code>__html__</code> method) is considered an already-formatted HTML tag, skipping both static file     resolution and rendering with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>You can set <code>extend</code> to configure   whether to inherit JS / CSS from parent components. See   Controlling Media Inheritance.</li> </ul> <p>However, there's a few differences from Django's Media class:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list,    or (CSS-only) a dictionary (See <code>ComponentMediaInput</code>).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>,    <code>SafeString</code>, or a function    (See <code>ComponentMediaInputPath</code>).</li> </ol> <p>Example:</p> <pre><code>class MyTable(Component):\n    class Media:\n        js = [\n            \"path/to/script.js\",\n            \"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\",  # AlpineJS\n        ]\n        css = {\n            \"all\": [\n                \"path/to/style.css\",\n                \"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\",  # TailwindCSS\n            ],\n            \"print\": [\"path/to/style2.css\"],\n        }\n</code></pre>"},{"location":"reference/api/#django_components.Component.context_processors_data","title":"context_processors_data  <code>property</code>","text":"<pre><code>context_processors_data: Dict\n</code></pre> <p>See source code</p> <p>Retrieve data injected by <code>context_processors</code>.</p> <p>This data is also available from within the component's template, without having to return this data from <code>get_context_data()</code>.</p> <p>Unlike regular Django templates, the context processors are applied to components either when:</p> <ul> <li>The component is rendered with <code>RequestContext</code> (Regular Django behavior)</li> <li>The component is rendered with a regular <code>Context</code> (or none), but the <code>request</code> kwarg   of <code>Component.render()</code> is set.</li> <li>The component is nested in another component that matches one of the two conditions above.</li> </ul> <p>See <code>Component.request</code> on how the <code>request</code> (HTTPRequest) object is passed to and within the components.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        user = self.context_processors_data['user']\n        return {\n            'is_logged_in': user.is_authenticated,\n        }\n</code></pre>"},{"location":"reference/api/#django_components.Component.css","title":"css  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>css: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Main CSS associated with this component inlined as string.</p> <p>Only one of <code>css</code> or <code>css_file</code> must be defined.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    css = \"\"\"\n    .my-class {\n        color: red;\n    }\n    \"\"\"\n</code></pre>"},{"location":"reference/api/#django_components.Component.css_file","title":"css_file  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>css_file: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Main CSS associated with this component as file path.</p> <p>The filepath must be either:</p> <ul> <li>Relative to the directory where the Component's Python file is defined.</li> <li>Relative to one of the component directories, as set by   <code>COMPONENTS.dirs</code>   or   <code>COMPONENTS.app_dirs</code>   (e.g. <code>&lt;root&gt;/components/</code>).</li> <li>Relative to the staticfiles directories, as set by Django's <code>STATICFILES_DIRS</code> setting (e.g. <code>&lt;root&gt;/static/</code>).</li> </ul> <p>When you create a Component class with <code>css_file</code>, these will happen:</p> <ol> <li>If the file path is relative to the directory where the component's Python file is,    the path is resolved.</li> <li>The file is read and its contents is set to <code>Component.css</code>.</li> </ol> <p>Only one of <code>css</code> or <code>css_file</code> must be defined.</p> <p>Example:</p> path/to/style.css<pre><code>.my-class {\n    color: red;\n}\n</code></pre> path/to/component.py<pre><code>class MyComponent(Component):\n    css_file = \"path/to/style.css\"\n\nprint(MyComponent.css)\n# Output:\n# .my-class {\n#     color: red;\n# };\n</code></pre>"},{"location":"reference/api/#django_components.Component.id","title":"id  <code>property</code>","text":"<pre><code>id: str\n</code></pre> <p>See source code</p> <p>This ID is unique for every time a <code>Component.render()</code> (or equivalent) is called (AKA \"render ID\").</p> <p>This is useful for logging or debugging.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p> <p>A single render ID has a chance of collision 1 in 3.3M. However, due to birthday paradox, the chance of collision increases when approaching ~1,000 render IDs.</p> <p>Thus, there is a soft-cap of 1,000 components rendered on a single page.</p> <p>If you need to more than that, please open an issue on GitHub.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        print(f\"Rendering '{self.id}'\")\n        return {}\n\nMyComponent.render()\n# Rendering 'ab3c4d'\n</code></pre>"},{"location":"reference/api/#django_components.Component.input","title":"input  <code>property</code>","text":"<pre><code>input: RenderInput[ArgsType, KwargsType, SlotsType]\n</code></pre> <p>See source code</p> <p>Input holds the data (like arg, kwargs, slots) that were passed to the current execution of the <code>render</code> method.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p>"},{"location":"reference/api/#django_components.Component.is_filled","title":"is_filled  <code>property</code>","text":"<pre><code>is_filled: SlotIsFilled\n</code></pre> <p>See source code</p> <p>Dictionary describing which slots have or have not been filled.</p> <p>This attribute is available for use only within the template as <code>{{ component_vars.is_filled.slot_name }}</code>, and within <code>on_render_before</code> and <code>on_render_after</code> hooks.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p>"},{"location":"reference/api/#django_components.Component.js","title":"js  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>js: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Main JS associated with this component inlined as string.</p> <p>Only one of <code>js</code> or <code>js_file</code> must be defined.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    js = \"console.log('Hello, World!');\"\n</code></pre>"},{"location":"reference/api/#django_components.Component.js_file","title":"js_file  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>js_file: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Main JS associated with this component as file path.</p> <p>The filepath must be either:</p> <ul> <li>Relative to the directory where the Component's Python file is defined.</li> <li>Relative to one of the component directories, as set by   <code>COMPONENTS.dirs</code>   or   <code>COMPONENTS.app_dirs</code>   (e.g. <code>&lt;root&gt;/components/</code>).</li> <li>Relative to the staticfiles directories, as set by Django's <code>STATICFILES_DIRS</code> setting (e.g. <code>&lt;root&gt;/static/</code>).</li> </ul> <p>When you create a Component class with <code>js_file</code>, these will happen:</p> <ol> <li>If the file path is relative to the directory where the component's Python file is,    the path is resolved.</li> <li>The file is read and its contents is set to <code>Component.js</code>.</li> </ol> <p>Only one of <code>js</code> or <code>js_file</code> must be defined.</p> <p>Example:</p> path/to/script.js<pre><code>console.log('Hello, World!');\n</code></pre> path/to/component.py<pre><code>class MyComponent(Component):\n    js_file = \"path/to/script.js\"\n\nprint(MyComponent.js)\n# Output: console.log('Hello, World!');\n</code></pre>"},{"location":"reference/api/#django_components.Component.media","title":"media  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>media: Optional[Media] = None\n</code></pre> <p>See source code</p> <p>Normalized definition of JS and CSS media files associated with this component. <code>None</code> if <code>Component.Media</code> is not defined.</p> <p>This field is generated from <code>Component.media_class</code>.</p> <p>Read more on Accessing component's HTML / JS / CSS.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    class Media:\n        js = \"path/to/script.js\"\n        css = \"path/to/style.css\"\n\nprint(MyComponent.media)\n# Output:\n# &lt;script src=\"/static/path/to/script.js\"&gt;&lt;/script&gt;\n# &lt;link href=\"/static/path/to/style.css\" media=\"all\" rel=\"stylesheet\"&gt;\n</code></pre>"},{"location":"reference/api/#django_components.Component.media_class","title":"media_class  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>media_class: Type[Media] = Media\n</code></pre> <p>See source code</p> <p>Set the Media class that will be instantiated with the JS and CSS media files from <code>Component.Media</code>.</p> <p>This is useful when you want to customize the behavior of the media files, like customizing how the JS or CSS files are rendered into <code>&lt;script&gt;</code> or <code>&lt;link&gt;</code> HTML tags. Read more in Defining HTML / JS / CSS files.</p> <p>Example:</p> <pre><code>class MyTable(Component):\n    class Media:\n        js = \"path/to/script.js\"\n        css = \"path/to/style.css\"\n\n    media_class = MyMediaClass\n</code></pre>"},{"location":"reference/api/#django_components.Component.name","title":"name  <code>property</code>","text":"<pre><code>name: str\n</code></pre>"},{"location":"reference/api/#django_components.Component.outer_context","title":"outer_context  <code>instance-attribute</code>","text":"<pre><code>outer_context: Optional[Context] = outer_context\n</code></pre>"},{"location":"reference/api/#django_components.Component.registered_name","title":"registered_name  <code>instance-attribute</code>","text":"<pre><code>registered_name: Optional[str] = registered_name\n</code></pre>"},{"location":"reference/api/#django_components.Component.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry = registry or registry\n</code></pre>"},{"location":"reference/api/#django_components.Component.request","title":"request  <code>property</code>","text":"<pre><code>request: Optional[HttpRequest]\n</code></pre> <p>See source code</p> <p>HTTPRequest object passed to this component.</p> <p>In regular Django templates, you have to use <code>RequestContext</code> to pass the <code>HttpRequest</code> object to the template.</p> <p>But in Components, you can either use <code>RequestContext</code>, or pass the <code>request</code> object explicitly via <code>Component.render()</code> and <code>Component.render_to_response()</code>.</p> <p>When a component is nested in another, the child component uses parent's <code>request</code> object.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        user_id = self.request.GET['user_id']\n        return {\n            'user_id': user_id,\n        }\n</code></pre>"},{"location":"reference/api/#django_components.Component.response_class","title":"response_class  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>response_class = HttpResponse\n</code></pre> <p>See source code</p> <p>This allows to configure what class is used to generate response from <code>render_to_response</code></p>"},{"location":"reference/api/#django_components.Component.template","title":"template  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>template: Optional[Union[str, Template]] = None\n</code></pre> <p>See source code</p> <p>Inlined Django template associated with this component. Can be a plain string or a Template instance.</p> <p>Only one of <code>template_file</code>, <code>get_template_name</code>, <code>template</code> or <code>get_template</code> must be defined.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    template = \"Hello, {{ name }}!\"\n\n    def get_context_data(self):\n        return {\"name\": \"World\"}\n</code></pre>"},{"location":"reference/api/#django_components.Component.template_file","title":"template_file  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>template_file: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Filepath to the Django template associated with this component.</p> <p>The filepath must be either:</p> <ul> <li>Relative to the directory where the Component's Python file is defined.</li> <li>Relative to one of the component directories, as set by   <code>COMPONENTS.dirs</code>   or   <code>COMPONENTS.app_dirs</code>   (e.g. <code>&lt;root&gt;/components/</code>).</li> <li>Relative to the template directories, as set by Django's <code>TEMPLATES</code> setting (e.g. <code>&lt;root&gt;/templates/</code>).</li> </ul> <p>Only one of <code>template_file</code>, <code>get_template_name</code>, <code>template</code> or <code>get_template</code> must be defined.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    template_file = \"path/to/template.html\"\n\n    def get_context_data(self):\n        return {\"name\": \"World\"}\n</code></pre>"},{"location":"reference/api/#django_components.Component.template_name","title":"template_name  <code>instance-attribute</code>","text":"<pre><code>template_name: Optional[str]\n</code></pre> <p>See source code</p> <p>Alias for <code>template_file</code>.</p> <p>For historical reasons, django-components used <code>template_name</code> to align with Django's TemplateView.</p> <p><code>template_file</code> was introduced to align with <code>js/js_file</code> and <code>css/css_file</code>.</p> <p>Setting and accessing this attribute is proxied to <code>template_file</code>.</p>"},{"location":"reference/api/#django_components.Component.as_view","title":"as_view  <code>classmethod</code>","text":"<pre><code>as_view(**initkwargs: Any) -&gt; ViewFn\n</code></pre> <p>See source code</p> <p>Shortcut for calling <code>Component.View.as_view</code> and passing component instance to it.</p>"},{"location":"reference/api/#django_components.Component.get_context_data","title":"get_context_data","text":"<pre><code>get_context_data(*args: Any, **kwargs: Any) -&gt; DataType\n</code></pre>"},{"location":"reference/api/#django_components.Component.get_template","title":"get_template","text":"<pre><code>get_template(context: Context) -&gt; Optional[Union[str, Template]]\n</code></pre> <p>See source code</p> <p>Inlined Django template associated with this component. Can be a plain string or a Template instance.</p> <p>Only one of <code>template_file</code>, <code>get_template_name</code>, <code>template</code> or <code>get_template</code> must be defined.</p>"},{"location":"reference/api/#django_components.Component.get_template_name","title":"get_template_name","text":"<pre><code>get_template_name(context: Context) -&gt; Optional[str]\n</code></pre> <p>See source code</p> <p>Filepath to the Django template associated with this component.</p> <p>The filepath must be relative to either the file where the component class was defined, or one of the roots of <code>STATIFILES_DIRS</code>.</p> <p>Only one of <code>template_file</code>, <code>get_template_name</code>, <code>template</code> or <code>get_template</code> must be defined.</p>"},{"location":"reference/api/#django_components.Component.inject","title":"inject","text":"<pre><code>inject(key: str, default: Optional[Any] = None) -&gt; Any\n</code></pre> <p>See source code</p> <p>Use this method to retrieve the data that was passed to a <code>{% provide %}</code> tag with the corresponding key.</p> <p>To retrieve the data, <code>inject()</code> must be called inside a component that's inside the <code>{% provide %}</code> tag.</p> <p>You may also pass a default that will be used if the <code>provide</code> tag with given key was NOT found.</p> <p>This method mut be used inside the <code>get_context_data()</code> method and raises an error if called elsewhere.</p> <p>Example:</p> <p>Given this template: <pre><code>{% provide \"provider\" hello=\"world\" %}\n    {% component \"my_comp\" %}\n    {% endcomponent %}\n{% endprovide %}\n</code></pre></p> <p>And given this definition of \"my_comp\" component: <pre><code>from django_components import Component, register\n\n@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"hi {{ data.hello }}!\"\n    def get_context_data(self):\n        data = self.inject(\"provider\")\n        return {\"data\": data}\n</code></pre></p> <p>This renders into: <pre><code>hi world!\n</code></pre></p> <p>As the <code>{{ data.hello }}</code> is taken from the \"provider\".</p>"},{"location":"reference/api/#django_components.Component.on_render_after","title":"on_render_after","text":"<pre><code>on_render_after(context: Context, template: Template, content: str) -&gt; Optional[SlotResult]\n</code></pre> <p>See source code</p> <p>Hook that runs just after the component's template was rendered. It receives the rendered output as the last argument.</p> <p>You can use this hook to access the context or the template, but modifying them won't have any effect.</p> <p>To override the content that gets rendered, you can return a string or SafeString from this hook.</p>"},{"location":"reference/api/#django_components.Component.on_render_before","title":"on_render_before","text":"<pre><code>on_render_before(context: Context, template: Template) -&gt; None\n</code></pre> <p>See source code</p> <p>Hook that runs just before the component's template is rendered.</p> <p>You can use this hook to access or modify the context or the template.</p>"},{"location":"reference/api/#django_components.Component.render","title":"render  <code>classmethod</code>","text":"<pre><code>render(\n    context: Optional[Union[Dict[str, Any], Context]] = None,\n    args: Optional[ArgsType] = None,\n    kwargs: Optional[KwargsType] = None,\n    slots: Optional[SlotsType] = None,\n    escape_slots_content: bool = True,\n    type: RenderType = \"document\",\n    render_dependencies: bool = True,\n    request: Optional[HttpRequest] = None,\n) -&gt; str\n</code></pre> <p>See source code</p> <p>Render the component into a string.</p> <p>Inputs: - <code>args</code> - Positional args for the component. This is the same as calling the component   as <code>{% component \"my_comp\" arg1 arg2 ... %}</code> - <code>kwargs</code> - Kwargs for the component. This is the same as calling the component   as <code>{% component \"my_comp\" key1=val1 key2=val2 ... %}</code> - <code>slots</code> - Component slot fills. This is the same as pasing <code>{% fill %}</code> tags to the component.     Accepts a dictionary of <code>{ slot_name: slot_content }</code> where <code>slot_content</code> can be a string     or render function. - <code>escape_slots_content</code> - Whether the content from <code>slots</code> should be escaped. - <code>context</code> - A context (dictionary or Django's Context) within which the component   is rendered. The keys on the context can be accessed from within the template.     - NOTE: In \"isolated\" mode, context is NOT accessible, and data MUST be passed via       component's args and kwargs. - <code>type</code> - Configure how to handle JS and CSS dependencies.     - <code>\"document\"</code> (default) - JS dependencies are inserted into <code>{% component_js_dependencies %}</code>,       or to the end of the <code>&lt;body&gt;</code> tag. CSS dependencies are inserted into       <code>{% component_css_dependencies %}</code>, or the end of the <code>&lt;head&gt;</code> tag. - <code>render_dependencies</code> - Set this to <code>False</code> if you want to insert the resulting HTML into another component. - <code>request</code> - The request object. This is only required when needing to use RequestContext,               e.g. to enable template <code>context_processors</code>. Example: <pre><code>MyComponent.render(\n    args=[1, \"two\", {}],\n    kwargs={\n        \"key\": 123,\n    },\n    slots={\n        \"header\": 'STATIC TEXT HERE',\n        \"footer\": lambda ctx, slot_kwargs, slot_ref: f'CTX: {ctx['hello']} SLOT_DATA: {slot_kwargs['abc']}',\n    },\n    escape_slots_content=False,\n)\n</code></pre></p>"},{"location":"reference/api/#django_components.Component.render_to_response","title":"render_to_response  <code>classmethod</code>","text":"<pre><code>render_to_response(\n    context: Optional[Union[Dict[str, Any], Context]] = None,\n    slots: Optional[SlotsType] = None,\n    escape_slots_content: bool = True,\n    args: Optional[ArgsType] = None,\n    kwargs: Optional[KwargsType] = None,\n    type: RenderType = \"document\",\n    request: Optional[HttpRequest] = None,\n    *response_args: Any,\n    **response_kwargs: Any\n) -&gt; HttpResponse\n</code></pre> <p>See source code</p> <p>Render the component and wrap the content in the response class.</p> <p>The response class is taken from <code>Component.response_class</code>. Defaults to <code>django.http.HttpResponse</code>.</p> <p>This is the interface for the <code>django.views.View</code> class which allows us to use components as Django views with <code>component.as_view()</code>.</p> <p>Inputs: - <code>args</code> - Positional args for the component. This is the same as calling the component   as <code>{% component \"my_comp\" arg1 arg2 ... %}</code> - <code>kwargs</code> - Kwargs for the component. This is the same as calling the component   as <code>{% component \"my_comp\" key1=val1 key2=val2 ... %}</code> - <code>slots</code> - Component slot fills. This is the same as pasing <code>{% fill %}</code> tags to the component.     Accepts a dictionary of <code>{ slot_name: slot_content }</code> where <code>slot_content</code> can be a string     or render function. - <code>escape_slots_content</code> - Whether the content from <code>slots</code> should be escaped. - <code>context</code> - A context (dictionary or Django's Context) within which the component   is rendered. The keys on the context can be accessed from within the template.     - NOTE: In \"isolated\" mode, context is NOT accessible, and data MUST be passed via       component's args and kwargs. - <code>type</code> - Configure how to handle JS and CSS dependencies.     - <code>\"document\"</code> (default) - JS dependencies are inserted into <code>{% component_js_dependencies %}</code>,       or to the end of the <code>&lt;body&gt;</code> tag. CSS dependencies are inserted into       <code>{% component_css_dependencies %}</code>, or the end of the <code>&lt;head&gt;</code> tag. - <code>request</code> - The request object. This is only required when needing to use RequestContext,               e.g. to enable template <code>context_processors</code>.</p> <p>Any additional args and kwargs are passed to the <code>response_class</code>.</p> <p>Example: <pre><code>MyComponent.render_to_response(\n    args=[1, \"two\", {}],\n    kwargs={\n        \"key\": 123,\n    },\n    slots={\n        \"header\": 'STATIC TEXT HERE',\n        \"footer\": lambda ctx, slot_kwargs, slot_ref: f'CTX: {ctx['hello']} SLOT_DATA: {slot_kwargs['abc']}',\n    },\n    escape_slots_content=False,\n    # HttpResponse input\n    status=201,\n    headers={...},\n)\n# HttpResponse(content=..., status=201, headers=...)\n</code></pre></p>"},{"location":"reference/api/#django_components.ComponentCommand","title":"ComponentCommand","text":"<p>Bases: <code>object</code></p> <p>See source code</p> <p>Definition of a CLI command.</p> <p>This class is based on Python's <code>argparse</code> module and Django's <code>BaseCommand</code> class. <code>ComponentCommand</code> allows you to define:</p> <ul> <li>Command name, description, and help text</li> <li>Arguments and options (e.g. <code>--name John</code>)</li> <li>Group arguments (see argparse groups)</li> <li>Subcommands (e.g. <code>components ext run my_ext hello</code>)</li> <li>Handler behavior</li> </ul> <p>Each extension can add its own commands, which will be available to run with <code>components ext run</code>.</p> <p>Extensions use the <code>ComponentCommand</code> class to define their commands.</p> <p>For example, if you define and install the following extension:</p> <pre><code>from django_components ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n    def handle(self, *args, **kwargs):\n        print(\"Hello, world!\")\n\nclass MyExt(ComponentExtension):\n    name = \"my_ext\"\n    commands = [HelloCommand]\n</code></pre> <p>You can run the <code>hello</code> command with:</p> <pre><code>python manage.py components ext run my_ext hello\n</code></pre> <p>You can also define arguments for the command, which will be passed to the command's <code>handle</code> method.</p> <pre><code>from django_components import CommandArg, ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n    arguments = [\n        CommandArg(name=\"name\", help=\"The name to say hello to\"),\n        CommandArg(name=[\"--shout\", \"-s\"], action=\"store_true\"),\n    ]\n\n    def handle(self, name: str, *args, **kwargs):\n        shout = kwargs.get(\"shout\", False)\n        msg = f\"Hello, {name}!\"\n        if shout:\n            msg = msg.upper()\n        print(msg)\n</code></pre> <p>You can run the command with:</p> <pre><code>python manage.py components ext run my_ext hello --name John --shout\n</code></pre> <p>Note</p> <p>Command arguments and options are based on Python's <code>argparse</code> module.</p> <p>For more information, see the argparse documentation.</p> <p>Attributes:</p> <ul> <li> <code>arguments</code>               (<code>Sequence[Union[CommandArg, CommandArgGroup]]</code>)           \u2013            </li> <li> <code>handle</code>               (<code>Optional[CommandHandler]</code>)           \u2013            </li> <li> <code>help</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>parser_input</code>               (<code>Optional[CommandParserInput]</code>)           \u2013            </li> <li> <code>subcommands</code>               (<code>Sequence[Type[ComponentCommand]]</code>)           \u2013            </li> <li> <code>subparser_input</code>               (<code>Optional[CommandSubcommand]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentCommand.arguments","title":"arguments  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>arguments: Sequence[Union[CommandArg, CommandArgGroup]] = ()\n</code></pre> <p>See source code</p> <p>argparse arguments for the command</p>"},{"location":"reference/api/#django_components.ComponentCommand.handle","title":"handle  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>handle: Optional[CommandHandler] = None\n</code></pre> <p>See source code</p> <p>The function that is called when the command is run. If <code>None</code>, the command will print the help message.</p>"},{"location":"reference/api/#django_components.ComponentCommand.help","title":"help  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>help: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The help text for the command</p>"},{"location":"reference/api/#django_components.ComponentCommand.name","title":"name  <code>instance-attribute</code>","text":"<pre><code>name: str\n</code></pre> <p>See source code</p> <p>The name of the command - this is what is used to call the command</p>"},{"location":"reference/api/#django_components.ComponentCommand.parser_input","title":"parser_input  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>parser_input: Optional[CommandParserInput] = None\n</code></pre> <p>See source code</p> <p>The input to use when creating the <code>ArgumentParser</code> for this command. If <code>None</code>, the default values will be used.</p>"},{"location":"reference/api/#django_components.ComponentCommand.subcommands","title":"subcommands  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>subcommands: Sequence[Type[ComponentCommand]] = ()\n</code></pre> <p>See source code</p> <p>Subcommands for the command</p>"},{"location":"reference/api/#django_components.ComponentCommand.subparser_input","title":"subparser_input  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>subparser_input: Optional[CommandSubcommand] = None\n</code></pre> <p>See source code</p> <p>The input to use when this command is a subcommand installed with <code>add_subparser()</code>. If <code>None</code>, the default values will be used.</p>"},{"location":"reference/api/#django_components.ComponentExtension","title":"ComponentExtension","text":"<p>Bases: <code>object</code></p> <p>See source code</p> <p>Base class for all extensions.</p> <p>Read more on Extensions.</p> <p>Methods:</p> <ul> <li> <code>on_component_class_created</code>             \u2013              </li> <li> <code>on_component_class_deleted</code>             \u2013              </li> <li> <code>on_component_data</code>             \u2013              </li> <li> <code>on_component_input</code>             \u2013              </li> <li> <code>on_component_registered</code>             \u2013              </li> <li> <code>on_component_unregistered</code>             \u2013              </li> <li> <code>on_registry_created</code>             \u2013              </li> <li> <code>on_registry_deleted</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>ExtensionClass</code>           \u2013            </li> <li> <code>class_name</code>               (<code>str</code>)           \u2013            </li> <li> <code>commands</code>               (<code>List[Type[ComponentCommand]]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>urls</code>               (<code>List[URLRoute]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentExtension.ExtensionClass","title":"ExtensionClass  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>ExtensionClass = BaseExtensionClass\n</code></pre> <p>See source code</p> <p>Base class that the \"extension class\" nested within a <code>Component</code> class will inherit from.</p> <p>This is where you can define new methods and attributes that will be available to the component instance.</p> <p>Background:</p> <p>The extension may add new features to the <code>Component</code> class by allowing users to define and access a nested class in the <code>Component</code> class. E.g.:</p> <pre><code>class MyComp(Component):\n    class MyExtension:\n        ...\n\n    def get_context_data(self):\n        return {\n            \"my_extension\": self.my_extension.do_something(),\n        }\n</code></pre> <p>When rendering a component, the nested extension class will be set as a subclass of <code>ExtensionClass</code>. So it will be same as if the user had directly inherited from <code>ExtensionClass</code>. E.g.:</p> <pre><code>class MyComp(Component):\n    class MyExtension(ComponentExtension.ExtensionClass):\n        ...\n</code></pre> <p>This setting decides what the extension class will inherit from.</p>"},{"location":"reference/api/#django_components.ComponentExtension.class_name","title":"class_name  <code>instance-attribute</code>","text":"<pre><code>class_name: str\n</code></pre> <p>See source code</p> <p>Name of the extension class.</p> <p>By default, this is the same as <code>name</code>, but with snake_case converted to PascalCase.</p> <p>So if the extension name is <code>\"my_extension\"</code>, then the extension class name will be <code>\"MyExtension\"</code>.</p> <pre><code>class MyComp(Component):\n    class MyExtension:  # &lt;--- This is the extension class\n        ...\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.commands","title":"commands  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>commands: List[Type[ComponentCommand]] = []\n</code></pre> <p>See source code</p> <p>List of commands that can be run by the extension.</p> <p>These commands will be available to the user as <code>components ext run &lt;extension&gt; &lt;command&gt;</code>.</p> <p>Commands are defined as subclasses of <code>ComponentCommand</code>.</p> <p>Example:</p> <p>This example defines an extension with a command that prints \"Hello world\". To run the command, the user would run <code>components ext run hello_world hello</code>.</p> <pre><code>from django_components import ComponentCommand, ComponentExtension, CommandArg, CommandArgGroup\n\nclass HelloWorldCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Hello world command.\"\n\n    # Allow to pass flags `--foo`, `--bar` and `--baz`.\n    # Argument parsing is managed by `argparse`.\n    arguments = [\n        CommandArg(\n            name_or_flags=\"--foo\",\n            help=\"Foo description.\",\n        ),\n        # When printing the command help message, `bar` and `baz`\n        # will be grouped under \"group bar\".\n        CommandArgGroup(\n            title=\"group bar\",\n            description=\"Group description.\",\n            arguments=[\n                CommandArg(\n                    name_or_flags=\"--bar\",\n                    help=\"Bar description.\",\n                ),\n                CommandArg(\n                    name_or_flags=\"--baz\",\n                    help=\"Baz description.\",\n                ),\n            ],\n        ),\n    ]\n\n    # Callback that receives the parsed arguments and options.\n    def handle(self, *args, **kwargs):\n        print(f\"HelloWorldCommand.handle: args={args}, kwargs={kwargs}\")\n\n# Associate the command with the extension\nclass HelloWorldExtension(ComponentExtension):\n    name = \"hello_world\"\n\n    commands = [\n        HelloWorldCommand,\n    ]\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.name","title":"name  <code>instance-attribute</code>","text":"<pre><code>name: str\n</code></pre> <p>See source code</p> <p>Name of the extension.</p> <p>Name must be lowercase, and must be a valid Python identifier (e.g. <code>\"my_extension\"</code>).</p> <p>The extension may add new features to the <code>Component</code> class by allowing users to define and access a nested class in the <code>Component</code> class.</p> <p>The extension name determines the name of the nested class in the <code>Component</code> class, and the attribute under which the extension will be accessible.</p> <p>E.g. if the extension name is <code>\"my_extension\"</code>, then the nested class in the <code>Component</code> class will be <code>MyExtension</code>, and the extension will be accessible as <code>MyComp.my_extension</code>.</p> <pre><code>class MyComp(Component):\n    class MyExtension:\n        ...\n\n    def get_context_data(self):\n        return {\n            \"my_extension\": self.my_extension.do_something(),\n        }\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.urls","title":"urls  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>urls: List[URLRoute] = []\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_class_created","title":"on_component_class_created","text":"<pre><code>on_component_class_created(ctx: OnComponentClassCreatedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a new <code>Component</code> class is created.</p> <p>This hook is called after the <code>Component</code> class is fully defined but before it's registered.</p> <p>Use this hook to perform any initialization or validation of the <code>Component</code> class.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentClassCreatedContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_class_created(self, ctx: OnComponentClassCreatedContext) -&gt; None:\n        # Add a new attribute to the Component class\n        ctx.component_cls.my_attr = \"my_value\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_class_deleted","title":"on_component_class_deleted","text":"<pre><code>on_component_class_deleted(ctx: OnComponentClassDeletedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is being deleted.</p> <p>This hook is called before the <code>Component</code> class is deleted from memory.</p> <p>Use this hook to perform any cleanup related to the <code>Component</code> class.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentClassDeletedContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_class_deleted(self, ctx: OnComponentClassDeletedContext) -&gt; None:\n        # Remove Component class from the extension's cache on deletion\n        self.cache.pop(ctx.component_cls, None)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_data","title":"on_component_data","text":"<pre><code>on_component_data(ctx: OnComponentDataContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a Component was triggered to render, after a component's context and data methods have been processed.</p> <p>This hook is called after <code>Component.get_context_data()</code>, <code>Component.get_js_data()</code> and <code>Component.get_css_data()</code>.</p> <p>This hook runs after <code>on_component_input</code>.</p> <p>Use this hook to modify or validate the component's data before rendering.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentDataContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_data(self, ctx: OnComponentDataContext) -&gt; None:\n        # Add extra template variable to all components when they are rendered\n        ctx.context_data[\"my_template_var\"] = \"my_value\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_input","title":"on_component_input","text":"<pre><code>on_component_input(ctx: OnComponentInputContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> was triggered to render, but before a component's context and data methods are invoked.</p> <p>This hook is called before <code>Component.get_context_data()</code>, <code>Component.get_js_data()</code> and <code>Component.get_css_data()</code>.</p> <p>Use this hook to modify or validate component inputs before they're processed.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentInputContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_input(self, ctx: OnComponentInputContext) -&gt; None:\n        # Add extra kwarg to all components when they are rendered\n        ctx.kwargs[\"my_input\"] = \"my_value\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_registered","title":"on_component_registered","text":"<pre><code>on_component_registered(ctx: OnComponentRegisteredContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is registered with a <code>ComponentRegistry</code>.</p> <p>This hook is called after a <code>Component</code> class is successfully registered.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentRegisteredContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_registered(self, ctx: OnComponentRegisteredContext) -&gt; None:\n        print(f\"Component {ctx.component_cls} registered to {ctx.registry} as '{ctx.name}'\")\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_unregistered","title":"on_component_unregistered","text":"<pre><code>on_component_unregistered(ctx: OnComponentUnregisteredContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is unregistered from a <code>ComponentRegistry</code>.</p> <p>This hook is called after a <code>Component</code> class is removed from the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentUnregisteredContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_unregistered(self, ctx: OnComponentUnregisteredContext) -&gt; None:\n        print(f\"Component {ctx.component_cls} unregistered from {ctx.registry} as '{ctx.name}'\")\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_registry_created","title":"on_registry_created","text":"<pre><code>on_registry_created(ctx: OnRegistryCreatedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a new <code>ComponentRegistry</code> is created.</p> <p>This hook is called after a new <code>ComponentRegistry</code> instance is initialized.</p> <p>Use this hook to perform any initialization needed for the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnRegistryCreatedContext\n\nclass MyExtension(ComponentExtension):\n    def on_registry_created(self, ctx: OnRegistryCreatedContext) -&gt; None:\n        # Add a new attribute to the registry\n        ctx.registry.my_attr = \"my_value\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_registry_deleted","title":"on_registry_deleted","text":"<pre><code>on_registry_deleted(ctx: OnRegistryDeletedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>ComponentRegistry</code> is being deleted.</p> <p>This hook is called before a <code>ComponentRegistry</code> instance is deleted.</p> <p>Use this hook to perform any cleanup related to the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnRegistryDeletedContext\n\nclass MyExtension(ComponentExtension):\n    def on_registry_deleted(self, ctx: OnRegistryDeletedContext) -&gt; None:\n        # Remove registry from the extension's cache on deletion\n        self.cache.pop(ctx.registry, None)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentFileEntry","title":"ComponentFileEntry","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>Result returned by <code>get_component_files()</code>.</p> <p>Attributes:</p> <ul> <li> <code>dot_path</code>               (<code>str</code>)           \u2013            </li> <li> <code>filepath</code>               (<code>Path</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentFileEntry.dot_path","title":"dot_path  <code>instance-attribute</code>","text":"<pre><code>dot_path: str\n</code></pre> <p>See source code</p> <p>The python import path for the module. E.g. <code>app.components.mycomp</code></p>"},{"location":"reference/api/#django_components.ComponentFileEntry.filepath","title":"filepath  <code>instance-attribute</code>","text":"<pre><code>filepath: Path\n</code></pre> <p>See source code</p> <p>The filesystem path to the module. E.g. <code>/path/to/project/app/components/mycomp.py</code></p>"},{"location":"reference/api/#django_components.ComponentMediaInput","title":"ComponentMediaInput","text":"<p>Bases: <code>typing.Protocol</code></p> <p>See source code</p> <p>Defines JS and CSS media files associated with a <code>Component</code>.</p> <pre><code>class MyTable(Component):\n    class Media:\n        js = [\n            \"path/to/script.js\",\n            \"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\",  # AlpineJS\n        ]\n        css = {\n            \"all\": [\n                \"path/to/style.css\",\n                \"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\",  # TailwindCSS\n            ],\n            \"print\": [\"path/to/style2.css\"],\n        }\n</code></pre> <p>Attributes:</p> <ul> <li> <code>css</code>               (<code>Optional[Union[ComponentMediaInputPath, List[ComponentMediaInputPath], Dict[str, ComponentMediaInputPath], Dict[str, List[ComponentMediaInputPath]]]]</code>)           \u2013            </li> <li> <code>extend</code>               (<code>Union[bool, List[Type[Component]]]</code>)           \u2013            </li> <li> <code>js</code>               (<code>Optional[Union[ComponentMediaInputPath, List[ComponentMediaInputPath]]]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentMediaInput.css","title":"css  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>css: Optional[\n    Union[\n        ComponentMediaInputPath, List[ComponentMediaInputPath], Dict[str, ComponentMediaInputPath], Dict[str, List[ComponentMediaInputPath]]\n    ]\n] = None\n</code></pre> <p>See source code</p> <p>CSS files associated with a <code>Component</code>.</p> <ul> <li> <p>If a string, it's assumed to be a path to a CSS file.</p> </li> <li> <p>If a list, each entry is assumed to be a path to a CSS file.</p> </li> <li> <p>If a dict, the keys are media types (e.g. \"all\", \"print\", \"screen\", etc.), and the values are either:</p> <ul> <li>A string, assumed to be a path to a CSS file.</li> <li>A list, each entry is assumed to be a path to a CSS file.</li> </ul> </li> </ul> <p>Each entry can be a string, bytes, SafeString, PathLike, or a callable that returns one of the former (see <code>ComponentMediaInputPath</code>).</p> <p>Examples: <pre><code>class MyComponent(Component):\n    class Media:\n        css = \"path/to/style.css\"\n</code></pre></p> <pre><code>class MyComponent(Component):\n    class Media:\n        css = [\"path/to/style1.css\", \"path/to/style2.css\"]\n</code></pre> <pre><code>class MyComponent(Component):\n    class Media:\n        css = {\n            \"all\": \"path/to/style.css\",\n            \"print\": \"path/to/print.css\",\n        }\n</code></pre> <pre><code>class MyComponent(Component):\n    class Media:\n        css = {\n            \"all\": [\"path/to/style1.css\", \"path/to/style2.css\"],\n            \"print\": \"path/to/print.css\",\n        }\n</code></pre>"},{"location":"reference/api/#django_components.ComponentMediaInput.extend","title":"extend  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>extend: Union[bool, List[Type[Component]]] = True\n</code></pre> <p>See source code</p> <p>Configures whether the component should inherit the media files from the parent component.</p> <ul> <li>If <code>True</code>, the component inherits the media files from the parent component.</li> <li>If <code>False</code>, the component does not inherit the media files from the parent component.</li> <li>If a list of components classes, the component inherits the media files ONLY from these specified components.</li> </ul> <p>Read more in Controlling Media Inheritance section.</p> <p>Example:</p> <p>Disable media inheritance:</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        extend = False  # Don't inherit parent media\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"script.js\"]\n</code></pre> <p>Specify which components to inherit from. In this case, the media files are inherited ONLY from the specified components, and NOT from the original parent components:</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        # Only inherit from these, ignoring the files from the parent\n        extend = [OtherComponent1, OtherComponent2]\n\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"script.js\", \"other1.js\", \"other2.js\"]\n</code></pre>"},{"location":"reference/api/#django_components.ComponentMediaInput.js","title":"js  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>js: Optional[Union[ComponentMediaInputPath, List[ComponentMediaInputPath]]] = None\n</code></pre> <p>See source code</p> <p>JS files associated with a <code>Component</code>.</p> <ul> <li> <p>If a string, it's assumed to be a path to a JS file.</p> </li> <li> <p>If a list, each entry is assumed to be a path to a JS file.</p> </li> </ul> <p>Each entry can be a string, bytes, SafeString, PathLike, or a callable that returns one of the former (see <code>ComponentMediaInputPath</code>).</p> <p>Examples: <pre><code>class MyComponent(Component):\n    class Media:\n        js = \"path/to/script.js\"\n</code></pre></p> <pre><code>class MyComponent(Component):\n    class Media:\n        js = [\"path/to/script1.js\", \"path/to/script2.js\"]\n</code></pre> <pre><code>class MyComponent(Component):\n    class Media:\n        js = lambda: [\"path/to/script1.js\", \"path/to/script2.js\"]\n</code></pre>"},{"location":"reference/api/#django_components.ComponentMediaInputPath","title":"ComponentMediaInputPath  <code>module-attribute</code>","text":"<pre><code>ComponentMediaInputPath = Union[str, bytes, SafeData, Path, PathLike, Callable[[], Union[str, bytes, SafeData, Path, PathLike]]]\n</code></pre> <p>See source code</p> <p>A type representing an entry in Media.js or Media.css.</p> <p>If an entry is a SafeString (or has <code>__html__</code> method), then entry is assumed to be a formatted HTML tag. Otherwise, it's assumed to be a path to a file.</p> <p>Example:</p> <pre><code>class MyComponent\n    class Media:\n        js = [\n            \"path/to/script.js\",\n            b\"script.js\",\n            SafeString(\"&lt;script src='path/to/script.js'&gt;&lt;/script&gt;\"),\n        ]\n        css = [\n            Path(\"path/to/style.css\"),\n            lambda: \"path/to/style.css\",\n            lambda: Path(\"path/to/style.css\"),\n        ]\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry","title":"ComponentRegistry","text":"<pre><code>ComponentRegistry(\n    library: Optional[Library] = None, settings: Optional[Union[RegistrySettings, Callable[[ComponentRegistry], RegistrySettings]]] = None\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Manages components and makes them available in the template, by default as <code>{% component %}</code> tags.</p> <pre><code>{% component \"my_comp\" key=value %}\n{% endcomponent %}\n</code></pre> <p>To enable a component to be used in a template, the component must be registered with a component registry.</p> <p>When you register a component to a registry, behind the scenes the registry automatically adds the component's template tag (e.g. <code>{% component %}</code> to the <code>Library</code>. And the opposite happens when you unregister a component - the tag is removed.</p> <p>See Registering components.</p> <p>Parameters:</p> <ul> <li> <code>library</code>               (<code>Library</code>, default:                   <code>None</code> )           \u2013            <p>Django            <code>Library</code>            associated with this registry. If omitted, the default Library instance from django_components is used.</p> </li> <li> <code>settings</code>               (<code>Union[RegistrySettings, Callable[[ComponentRegistry], RegistrySettings]]</code>, default:                   <code>None</code> )           \u2013            <p>Configure            how the components registered with this registry will behave when rendered.            See <code>RegistrySettings</code>. Can be either            a static value or a callable that returns the settings. If omitted, the settings from            <code>COMPONENTS</code> are used.</p> </li> </ul> <p>Notes:</p> <ul> <li>The default registry is available as <code>django_components.registry</code>.</li> <li>The default registry is used when registering components with <code>@register</code> decorator.</li> </ul> <p>Example:</p> <pre><code># Use with default Library\nregistry = ComponentRegistry()\n\n# Or a custom one\nmy_lib = Library()\nregistry = ComponentRegistry(library=my_lib)\n\n# Usage\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\nregistry.all()\nregistry.clear()\nregistry.get(\"button\")\nregistry.has(\"button\")\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry--using-registry-to-share-components","title":"Using registry to share components","text":"<p>You can use component registry for isolating or \"packaging\" components:</p> <ol> <li> <p>Create new instance of <code>ComponentRegistry</code> and Library:     <pre><code>my_comps = Library()\nmy_comps_reg = ComponentRegistry(library=my_comps)\n</code></pre></p> </li> <li> <p>Register components to the registry:     <pre><code>my_comps_reg.register(\"my_button\", ButtonComponent)\nmy_comps_reg.register(\"my_card\", CardComponent)\n</code></pre></p> </li> <li> <p>In your target project, load the Library associated with the registry:     <pre><code>{% load my_comps %}\n</code></pre></p> </li> <li> <p>Use the registered components in your templates:     <pre><code>{% component \"button\" %}\n{% endcomponent %}\n</code></pre></p> </li> </ol> <p>Methods:</p> <ul> <li> <code>all</code>             \u2013              </li> <li> <code>clear</code>             \u2013              </li> <li> <code>get</code>             \u2013              </li> <li> <code>has</code>             \u2013              </li> <li> <code>register</code>             \u2013              </li> <li> <code>unregister</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>library</code>               (<code>Library</code>)           \u2013            </li> <li> <code>settings</code>               (<code>InternalRegistrySettings</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentRegistry.library","title":"library  <code>property</code>","text":"<pre><code>library: Library\n</code></pre> <p>See source code</p> <p>The template tag <code>Library</code> that is associated with the registry.</p>"},{"location":"reference/api/#django_components.ComponentRegistry.settings","title":"settings  <code>property</code>","text":"<pre><code>settings: InternalRegistrySettings\n</code></pre> <p>See source code</p> <p>Registry settings configured for this registry.</p>"},{"location":"reference/api/#django_components.ComponentRegistry.all","title":"all","text":"<pre><code>all() -&gt; Dict[str, Type[Component]]\n</code></pre> <p>See source code</p> <p>Retrieve all registered <code>Component</code> classes.</p> <p>Returns:</p> <ul> <li> <code>Dict[str, Type[Component]]</code>           \u2013            <p>Dict[str, Type[Component]]: A dictionary of component names to component classes</p> </li> </ul> <p>Example:</p> <pre><code># First register components\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\n# Then get all\nregistry.all()\n# &gt; {\n# &gt;   \"button\": ButtonComponent,\n# &gt;   \"card\": CardComponent,\n# &gt; }\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.clear","title":"clear","text":"<pre><code>clear() -&gt; None\n</code></pre> <p>See source code</p> <p>Clears the registry, unregistering all components.</p> <p>Example:</p> <pre><code># First register components\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\n# Then clear\nregistry.clear()\n# Then get all\nregistry.all()\n# &gt; {}\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.get","title":"get","text":"<pre><code>get(name: str) -&gt; Type[Component]\n</code></pre> <p>See source code</p> <p>Retrieve a <code>Component</code> class registered under the given name.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>The name under which the component was registered. Required.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>Type[Component]</code>           \u2013            <p>Type[Component]: The component class registered under the given name.</p> </li> </ul> <p>Raises:</p> <ul> <li><code>NotRegistered</code>   if the given name is not registered.</li> </ul> <p>Example:</p> <pre><code># First register component\nregistry.register(\"button\", ButtonComponent)\n# Then get\nregistry.get(\"button\")\n# &gt; ButtonComponent\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.has","title":"has","text":"<pre><code>has(name: str) -&gt; bool\n</code></pre> <p>See source code</p> <p>Check if a <code>Component</code> class is registered under the given name.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>The name under which the component was registered. Required.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>bool</code> (              <code>bool</code> )          \u2013            <p><code>True</code> if the component is registered, <code>False</code> otherwise.</p> </li> </ul> <p>Example:</p> <pre><code># First register component\nregistry.register(\"button\", ButtonComponent)\n# Then check\nregistry.has(\"button\")\n# &gt; True\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.register","title":"register","text":"<pre><code>register(name: str, component: Type[Component]) -&gt; None\n</code></pre> <p>See source code</p> <p>Register a <code>Component</code> class with this registry under the given name.</p> <p>A component MUST be registered before it can be used in a template such as: <pre><code>{% component \"my_comp\" %}\n{% endcomponent %}\n</code></pre></p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>The name under which the component will be registered. Required.</p> </li> <li> <code>component</code>               (<code>Type[Component]</code>)           \u2013            <p>The component class to register. Required.</p> </li> </ul> <p>Raises:</p> <ul> <li><code>AlreadyRegistered</code> if a different component was already registered under the same name.</li> </ul> <p>Example:</p> <pre><code>registry.register(\"button\", ButtonComponent)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.unregister","title":"unregister","text":"<pre><code>unregister(name: str) -&gt; None\n</code></pre> <p>See source code</p> <p>Unregister the <code>Component</code> class that was registered under the given name.</p> <p>Once a component is unregistered, it is no longer available in the templates.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>The name under which the component is registered. Required.</p> </li> </ul> <p>Raises:</p> <ul> <li><code>NotRegistered</code> if the given name is not registered.</li> </ul> <p>Example:</p> <pre><code># First register component\nregistry.register(\"button\", ButtonComponent)\n# Then unregister\nregistry.unregister(\"button\")\n</code></pre>"},{"location":"reference/api/#django_components.ComponentVars","title":"ComponentVars","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>Type for the variables available inside the component templates.</p> <p>All variables here are scoped under <code>component_vars.</code>, so e.g. attribute <code>is_filled</code> on this class is accessible inside the template as:</p> <pre><code>{{ component_vars.is_filled }}\n</code></pre> <p>Attributes:</p> <ul> <li> <code>is_filled</code>               (<code>Dict[str, bool]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentVars.is_filled","title":"is_filled  <code>instance-attribute</code>","text":"<pre><code>is_filled: Dict[str, bool]\n</code></pre> <p>See source code</p> <p>Dictonary describing which component slots are filled (<code>True</code>) or are not (<code>False</code>).</p> <p>New in version 0.70</p> <p>Use as <code>{{ component_vars.is_filled }}</code></p> <p>Example:</p> <pre><code>{# Render wrapping HTML only if the slot is defined #}\n{% if component_vars.is_filled.my_slot %}\n    &lt;div class=\"slot-wrapper\"&gt;\n        {% slot \"my_slot\" / %}\n    &lt;/div&gt;\n{% endif %}\n</code></pre> <p>This is equivalent to checking if a given key is among the slot fills:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"my_slot_filled\": \"my_slot\" in self.input.slots\n        }\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView","title":"ComponentView","text":"<pre><code>ComponentView(component: Component, **kwargs: Any)\n</code></pre> <p>Bases: <code>django_components.extension.BaseExtensionClass</code>, <code>django.views.generic.base.View</code></p> <p>See source code</p> <p>Subclass of <code>django.views.View</code> where the <code>Component</code> instance is available via <code>self.component</code>.</p> <p>Methods:</p> <ul> <li> <code>delete</code>             \u2013              </li> <li> <code>get</code>             \u2013              </li> <li> <code>head</code>             \u2013              </li> <li> <code>options</code>             \u2013              </li> <li> <code>patch</code>             \u2013              </li> <li> <code>post</code>             \u2013              </li> <li> <code>put</code>             \u2013              </li> <li> <code>trace</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>component</code>           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentView.component","title":"component  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>component = cast('Component', None)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.delete","title":"delete","text":"<pre><code>delete(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.get","title":"get","text":"<pre><code>get(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.head","title":"head","text":"<pre><code>head(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.options","title":"options","text":"<pre><code>options(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.patch","title":"patch","text":"<pre><code>patch(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.post","title":"post","text":"<pre><code>post(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.put","title":"put","text":"<pre><code>put(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.trace","title":"trace","text":"<pre><code>trace(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings","title":"ComponentsSettings","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>Settings available for django_components.</p> <p>Example:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    autodiscover=False,\n    dirs = [BASE_DIR / \"components\"],\n)\n</code></pre> <p>Attributes:</p> <ul> <li> <code>app_dirs</code>               (<code>Optional[Sequence[str]]</code>)           \u2013            </li> <li> <code>autodiscover</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>cache</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>context_behavior</code>               (<code>Optional[ContextBehaviorType]</code>)           \u2013            </li> <li> <code>debug_highlight_components</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>debug_highlight_slots</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>dirs</code>               (<code>Optional[Sequence[Union[str, PathLike, Tuple[str, str], Tuple[str, PathLike]]]]</code>)           \u2013            </li> <li> <code>dynamic_component_name</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>extensions</code>               (<code>Optional[Sequence[Union[Type[ComponentExtension], str]]]</code>)           \u2013            </li> <li> <code>forbidden_static_files</code>               (<code>Optional[List[Union[str, Pattern]]]</code>)           \u2013            </li> <li> <code>libraries</code>               (<code>Optional[List[str]]</code>)           \u2013            </li> <li> <code>multiline_tags</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>reload_on_file_change</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>reload_on_template_change</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>static_files_allowed</code>               (<code>Optional[List[Union[str, Pattern]]]</code>)           \u2013            </li> <li> <code>static_files_forbidden</code>               (<code>Optional[List[Union[str, Pattern]]]</code>)           \u2013            </li> <li> <code>tag_formatter</code>               (<code>Optional[Union[TagFormatterABC, str]]</code>)           \u2013            </li> <li> <code>template_cache_size</code>               (<code>Optional[int]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentsSettings.app_dirs","title":"app_dirs  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>app_dirs: Optional[Sequence[str]] = None\n</code></pre> <p>See source code</p> <p>Specify the app-level directories that contain your components.</p> <p>Defaults to <code>[\"components\"]</code>. That is, for each Django app, we search <code>&lt;app&gt;/components/</code> for components.</p> <p>The paths must be relative to app, e.g.:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    app_dirs=[\"my_comps\"],\n)\n</code></pre> <p>To search for <code>&lt;app&gt;/my_comps/</code>.</p> <p>These locations are searched during autodiscovery, or when you define HTML, JS, or CSS as separate files.</p> <p>Set to empty list to disable app-level components:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    app_dirs=[],\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.autodiscover","title":"autodiscover  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>autodiscover: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Toggle whether to run autodiscovery at the Django server startup.</p> <p>Defaults to <code>True</code></p> <pre><code>COMPONENTS = ComponentsSettings(\n    autodiscover=False,\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.cache","title":"cache  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>cache: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the Django cache to be used for storing component's JS and CSS files.</p> <p>If <code>None</code>, a <code>LocMemCache</code> is used with default settings.</p> <p>Defaults to <code>None</code>.</p> <p>Read more about caching.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    cache=\"my_cache\",\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.context_behavior","title":"context_behavior  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>context_behavior: Optional[ContextBehaviorType] = None\n</code></pre> <p>See source code</p> <p>Configure whether, inside a component template, you can use variables from the outside (<code>\"django\"</code>) or not (<code>\"isolated\"</code>). This also affects what variables are available inside the <code>{% fill %}</code> tags.</p> <p>Also see Component context and scope.</p> <p>Defaults to <code>\"django\"</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    context_behavior=\"isolated\",\n)\n</code></pre> <p>NOTE: <code>context_behavior</code> and <code>slot_context_behavior</code> options were merged in v0.70.</p> <p>If you are migrating from BEFORE v0.67, set <code>context_behavior</code> to <code>\"django\"</code>. From v0.67 to v0.78 (incl) the default value was <code>\"isolated\"</code>.</p> <p>For v0.79 and later, the default is again <code>\"django\"</code>. See the rationale for change here.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.debug_highlight_components","title":"debug_highlight_components  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>debug_highlight_components: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable component highlighting. See Troubleshooting for more details.</p> <p>Defaults to <code>False</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    debug_highlight_components=True,\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.debug_highlight_slots","title":"debug_highlight_slots  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>debug_highlight_slots: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable slot highlighting. See Troubleshooting for more details.</p> <p>Defaults to <code>False</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    debug_highlight_slots=True,\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.dirs","title":"dirs  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>dirs: Optional[Sequence[Union[str, PathLike, Tuple[str, str], Tuple[str, PathLike]]]] = None\n</code></pre> <p>See source code</p> <p>Specify the directories that contain your components.</p> <p>Defaults to <code>[Path(settings.BASE_DIR) / \"components\"]</code>. That is, the root <code>components/</code> app.</p> <p>Directories must be full paths, same as with STATICFILES_DIRS.</p> <p>These locations are searched during autodiscovery, or when you define HTML, JS, or CSS as separate files.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    dirs=[BASE_DIR / \"components\"],\n)\n</code></pre> <p>Set to empty list to disable global components directories:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    dirs=[],\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.dynamic_component_name","title":"dynamic_component_name  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>dynamic_component_name: Optional[str] = None\n</code></pre> <p>See source code</p> <p>By default, the dynamic component is registered under the name <code>\"dynamic\"</code>.</p> <p>In case of a conflict, you can use this setting to change the component name used for the dynamic components.</p> <pre><code># settings.py\nCOMPONENTS = ComponentsSettings(\n    dynamic_component_name=\"my_dynamic\",\n)\n</code></pre> <p>After which you will be able to use the dynamic component with the new name:</p> <pre><code>{% component \"my_dynamic\" is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.extensions","title":"extensions  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>extensions: Optional[Sequence[Union[Type[ComponentExtension], str]]] = None\n</code></pre> <p>See source code</p> <p>List of extensions to be loaded.</p> <p>The extensions can be specified as:</p> <ul> <li>Python import path, e.g. <code>\"path.to.my_extension.MyExtension\"</code>.</li> <li>Extension class, e.g. <code>my_extension.MyExtension</code>.</li> </ul> <pre><code>COMPONENTS = ComponentsSettings(\n    extensions=[\n        \"path.to.my_extension.MyExtension\",\n        StorybookExtension,\n    ],\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.forbidden_static_files","title":"forbidden_static_files  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>forbidden_static_files: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>COMPONENTS.static_files_forbidden</code> instead.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.libraries","title":"libraries  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>libraries: Optional[List[str]] = None\n</code></pre> <p>See source code</p> <p>Configure extra python modules that should be loaded.</p> <p>This may be useful if you are not using the autodiscovery feature, or you need to load components from non-standard locations. Thus you can have a structure of components that is independent from your apps.</p> <p>Expects a list of python module paths. Defaults to empty list.</p> <p>Example:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    libraries=[\n        \"mysite.components.forms\",\n        \"mysite.components.buttons\",\n        \"mysite.components.cards\",\n    ],\n)\n</code></pre> <p>This would be the equivalent of importing these modules from within Django's <code>AppConfig.ready()</code>:</p> <pre><code>class MyAppConfig(AppConfig):\n    def ready(self):\n        import \"mysite.components.forms\"\n        import \"mysite.components.buttons\"\n        import \"mysite.components.cards\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.libraries--manually-loading-libraries","title":"Manually loading libraries","text":"<p>In the rare case that you need to manually trigger the import of libraries, you can use the <code>import_libraries()</code> function:</p> <pre><code>from django_components import import_libraries\n\nimport_libraries()\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.multiline_tags","title":"multiline_tags  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>multiline_tags: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable multiline support for template tags. If <code>True</code>, template tags like <code>{% component %}</code> or <code>{{ my_var }}</code> can span multiple lines.</p> <p>Defaults to <code>True</code>.</p> <p>Disable this setting if you are making custom modifications to Django's regular expression for parsing templates at <code>django.template.base.tag_re</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    multiline_tags=False,\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.reload_on_file_change","title":"reload_on_file_change  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>reload_on_file_change: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>This is relevant if you are using the project structure where HTML, JS, CSS and Python are in separate files and nested in a directory.</p> <p>In this case you may notice that when you are running a development server, the server sometimes does not reload when you change component files.</p> <p>Django's native live reload logic handles only Python files and HTML template files. It does NOT reload when other file types change or when template files are nested more than one level deep.</p> <p>The setting <code>reload_on_file_change</code> fixes this, reloading the dev server even when your component's HTML, JS, or CSS changes.</p> <p>If <code>True</code>, django_components configures Django to reload when files inside <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> change.</p> <p>See Reload dev server on component file changes.</p> <p>Defaults to <code>False</code>.</p> <p>Warning</p> <p>This setting should be enabled only for the dev environment!</p>"},{"location":"reference/api/#django_components.ComponentsSettings.reload_on_template_change","title":"reload_on_template_change  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>reload_on_template_change: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>COMPONENTS.reload_on_file_change</code> instead.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.static_files_allowed","title":"static_files_allowed  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>static_files_allowed: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>A list of file extensions (including the leading dot) that define which files within <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> are treated as static files.</p> <p>If a file is matched against any of the patterns, it's considered a static file. Such files are collected when running <code>collectstatic</code>, and can be accessed under the static file endpoint.</p> <p>You can also pass in compiled regexes (<code>re.Pattern</code>) for more advanced patterns.</p> <p>By default, JS, CSS, and common image and font file formats are considered static files:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    static_files_allowed=[\n        \".css\",\n        \".js\", \".jsx\", \".ts\", \".tsx\",\n        # Images\n        \".apng\", \".png\", \".avif\", \".gif\", \".jpg\",\n        \".jpeg\",  \".jfif\", \".pjpeg\", \".pjp\", \".svg\",\n        \".webp\", \".bmp\", \".ico\", \".cur\", \".tif\", \".tiff\",\n        # Fonts\n        \".eot\", \".ttf\", \".woff\", \".otf\", \".svg\",\n    ],\n)\n</code></pre> <p>Warning</p> <p>Exposing your Python files can be a security vulnerability. See Security notes.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.static_files_forbidden","title":"static_files_forbidden  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>static_files_forbidden: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>A list of file extensions (including the leading dot) that define which files within <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> will NEVER be treated as static files.</p> <p>If a file is matched against any of the patterns, it will never be considered a static file, even if the file matches a pattern in <code>static_files_allowed</code>.</p> <p>Use this setting together with <code>static_files_allowed</code> for a fine control over what file types will be exposed.</p> <p>You can also pass in compiled regexes (<code>re.Pattern</code>) for more advanced patterns.</p> <p>By default, any HTML and Python are considered NOT static files:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    static_files_forbidden=[\n        \".html\", \".django\", \".dj\", \".tpl\",\n        # Python files\n        \".py\", \".pyc\",\n    ],\n)\n</code></pre> <p>Warning</p> <p>Exposing your Python files can be a security vulnerability. See Security notes.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.tag_formatter","title":"tag_formatter  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>tag_formatter: Optional[Union[TagFormatterABC, str]] = None\n</code></pre> <p>See source code</p> <p>Configure what syntax is used inside Django templates to render components. See the available tag formatters.</p> <p>Defaults to <code>\"django_components.component_formatter\"</code>.</p> <p>Learn more about Customizing component tags with TagFormatter.</p> <p>Can be set either as direct reference:</p> <pre><code>from django_components import component_formatter\n\nCOMPONENTS = ComponentsSettings(\n    \"tag_formatter\": component_formatter\n)\n</code></pre> <p>Or as an import string;</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_formatter\"\n)\n</code></pre> <p>Examples:</p> <ul> <li> <p><code>\"django_components.component_formatter\"</code></p> <p>Set</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_formatter\"\n)\n</code></pre> <p>To write components like this:</p> <pre><code>{% component \"button\" href=\"...\" %}\n    Click me!\n{% endcomponent %}\n</code></pre> </li> <li> <p><code>django_components.component_shorthand_formatter</code></p> <p>Set</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_shorthand_formatter\"\n)\n</code></pre> <p>To write components like this:</p> <pre><code>{% button href=\"...\" %}\n    Click me!\n{% endbutton %}\n</code></pre> </li> </ul>"},{"location":"reference/api/#django_components.ComponentsSettings.template_cache_size","title":"template_cache_size  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>template_cache_size: Optional[int] = None\n</code></pre> <p>See source code</p> <p>Configure the maximum amount of Django templates to be cached.</p> <p>Defaults to <code>128</code>.</p> <p>Each time a Django template is rendered, it is cached to a global in-memory cache (using Python's <code>lru_cache</code> decorator). This speeds up the next render of the component. As the same component is often used many times on the same page, these savings add up.</p> <p>By default the cache holds 128 component templates in memory, which should be enough for most sites. But if you have a lot of components, or if you are overriding <code>Component.get_template()</code> to render many dynamic templates, you can increase this number.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    template_cache_size=256,\n)\n</code></pre> <p>To remove the cache limit altogether and cache everything, set <code>template_cache_size</code> to <code>None</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    template_cache_size=None,\n)\n</code></pre> <p>If you want to add templates to the cache yourself, you can use <code>cached_template()</code>:</p> <pre><code>from django_components import cached_template\n\ncached_template(\"Variable: {{ variable }}\")\n\n# You can optionally specify Template class, and other Template inputs:\nclass MyTemplate(Template):\n    pass\n\ncached_template(\n    \"Variable: {{ variable }}\",\n    template_cls=MyTemplate,\n    name=...\n    origin=...\n    engine=...\n)\n</code></pre>"},{"location":"reference/api/#django_components.ContextBehavior","title":"ContextBehavior","text":"<p>Bases: <code>str</code>, <code>enum.Enum</code></p> <p>See source code</p> <p>Configure how (and whether) the context is passed to the component fills and what variables are available inside the <code>{% fill %}</code> tags.</p> <p>Also see Component context and scope.</p> <p>Options:</p> <ul> <li><code>django</code>: With this setting, component fills behave as usual Django tags.</li> <li><code>isolated</code>: This setting makes the component fills behave similar to Vue or React.</li> </ul> <p>Attributes:</p> <ul> <li> <code>DJANGO</code>           \u2013            </li> <li> <code>ISOLATED</code>           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ContextBehavior.DJANGO","title":"DJANGO  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>DJANGO = 'django'\n</code></pre> <p>See source code</p> <p>With this setting, component fills behave as usual Django tags. That is, they enrich the context, and pass it along.</p> <ol> <li>Component fills use the context of the component they are within.</li> <li>Variables from <code>Component.get_context_data()</code> are available to the component fill.</li> </ol> <p>Example:</p> <p>Given this template <pre><code>{% with cheese=\"feta\" %}\n  {% component 'my_comp' %}\n    {{ my_var }}  # my_var\n    {{ cheese }}  # cheese\n  {% endcomponent %}\n{% endwith %}\n</code></pre></p> <p>and this context returned from the <code>Component.get_context_data()</code> method <pre><code>{ \"my_var\": 123 }\n</code></pre></p> <p>Then if component \"my_comp\" defines context <pre><code>{ \"my_var\": 456 }\n</code></pre></p> <p>Then this will render: <pre><code>456   # my_var\nfeta  # cheese\n</code></pre></p> <p>Because \"my_comp\" overrides the variable \"my_var\", so <code>{{ my_var }}</code> equals <code>456</code>.</p> <p>And variable \"cheese\" will equal <code>feta</code>, because the fill CAN access the current context.</p>"},{"location":"reference/api/#django_components.ContextBehavior.ISOLATED","title":"ISOLATED  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>ISOLATED = 'isolated'\n</code></pre> <p>See source code</p> <p>This setting makes the component fills behave similar to Vue or React, where the fills use EXCLUSIVELY the context variables defined in <code>Component.get_context_data()</code>.</p> <p>Example:</p> <p>Given this template <pre><code>{% with cheese=\"feta\" %}\n  {% component 'my_comp' %}\n    {{ my_var }}  # my_var\n    {{ cheese }}  # cheese\n  {% endcomponent %}\n{% endwith %}\n</code></pre></p> <p>and this context returned from the <code>get_context_data()</code> method <pre><code>{ \"my_var\": 123 }\n</code></pre></p> <p>Then if component \"my_comp\" defines context <pre><code>{ \"my_var\": 456 }\n</code></pre></p> <p>Then this will render: <pre><code>123   # my_var\n      # cheese\n</code></pre></p> <p>Because both variables \"my_var\" and \"cheese\" are taken from the root context. Since \"cheese\" is not defined in root context, it's empty.</p>"},{"location":"reference/api/#django_components.EmptyDict","title":"EmptyDict","text":"<p>Bases: <code>dict</code></p> <p>See source code</p> <p>TypedDict with no members.</p> <p>You can use this to define a Component that accepts NO kwargs, or NO slots, or returns NO data from <code>Component.get_context_data()</code> / <code>Component.get_js_data()</code> / <code>Component.get_css_data()</code>:</p> <p>Accepts NO kwargs:</p> <pre><code>from django_components import Component, EmptyDict\n\nclass Table(Component(Any, EmptyDict, Any, Any, Any, Any))\n    ...\n</code></pre> <p>Accepts NO slots:</p> <pre><code>from django_components import Component, EmptyDict\n\nclass Table(Component(Any, Any, EmptyDict, Any, Any, Any))\n    ...\n</code></pre> <p>Returns NO data from <code>get_context_data()</code>:</p> <pre><code>from django_components import Component, EmptyDict\n\nclass Table(Component(Any, Any, Any, EmptyDict, Any, Any))\n    ...\n</code></pre> <p>Going back to the example with NO kwargs, when you then call <code>Component.render()</code> or <code>Component.render_to_response()</code>, the <code>kwargs</code> parameter will raise type error if <code>kwargs</code> is anything else than an empty dict.</p> <pre><code>Table.render(\n    kwargs: {},\n)\n</code></pre> <p>Omitting <code>kwargs</code> is also fine:</p> <pre><code>Table.render()\n</code></pre> <p>Other values are not allowed. This will raise an error with MyPy:</p> <pre><code>Table.render(\n    kwargs: {\n        \"one\": 2,\n        \"three\": 4,\n    },\n)\n</code></pre>"},{"location":"reference/api/#django_components.EmptyTuple","title":"EmptyTuple  <code>module-attribute</code>","text":"<pre><code>EmptyTuple = Tuple[]\n</code></pre> <p>See source code</p> <p>Tuple with no members.</p> <p>You can use this to define a Component that accepts NO positional arguments:</p> <pre><code>from django_components import Component, EmptyTuple\n\nclass Table(Component(EmptyTuple, Any, Any, Any, Any, Any))\n    ...\n</code></pre> <p>After that, when you call <code>Component.render()</code> or <code>Component.render_to_response()</code>, the <code>args</code> parameter will raise type error if <code>args</code> is anything else than an empty tuple.</p> <pre><code>Table.render(\n    args: (),\n)\n</code></pre> <p>Omitting <code>args</code> is also fine:</p> <pre><code>Table.render()\n</code></pre> <p>Other values are not allowed. This will raise an error with MyPy:</p> <pre><code>Table.render(\n    args: (\"one\", 2, \"three\"),\n)\n</code></pre>"},{"location":"reference/api/#django_components.OnComponentClassCreatedContext","title":"OnComponentClassCreatedContext","text":"<p>Attributes:</p> <ul> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentClassCreatedContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The created Component class</p>"},{"location":"reference/api/#django_components.OnComponentClassDeletedContext","title":"OnComponentClassDeletedContext","text":"<p>Attributes:</p> <ul> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentClassDeletedContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The to-be-deleted Component class</p>"},{"location":"reference/api/#django_components.OnComponentDataContext","title":"OnComponentDataContext","text":"<p>Attributes:</p> <ul> <li> <code>component</code>               (<code>Component</code>)           \u2013            </li> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> <li> <code>component_id</code>               (<code>str</code>)           \u2013            </li> <li> <code>context_data</code>               (<code>Dict</code>)           \u2013            </li> <li> <code>css_data</code>               (<code>Dict</code>)           \u2013            </li> <li> <code>js_data</code>               (<code>Dict</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentDataContext.component","title":"component  <code>instance-attribute</code>","text":"<pre><code>component: Component\n</code></pre> <p>See source code</p> <p>The Component instance that is being rendered</p>"},{"location":"reference/api/#django_components.OnComponentDataContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The Component class</p>"},{"location":"reference/api/#django_components.OnComponentDataContext.component_id","title":"component_id  <code>instance-attribute</code>","text":"<pre><code>component_id: str\n</code></pre> <p>See source code</p> <p>The unique identifier for this component instance</p>"},{"location":"reference/api/#django_components.OnComponentDataContext.context_data","title":"context_data  <code>instance-attribute</code>","text":"<pre><code>context_data: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of context data from <code>Component.get_context_data()</code></p>"},{"location":"reference/api/#django_components.OnComponentDataContext.css_data","title":"css_data  <code>instance-attribute</code>","text":"<pre><code>css_data: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of CSS data from <code>Component.get_css_data()</code></p>"},{"location":"reference/api/#django_components.OnComponentDataContext.js_data","title":"js_data  <code>instance-attribute</code>","text":"<pre><code>js_data: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of JavaScript data from <code>Component.get_js_data()</code></p>"},{"location":"reference/api/#django_components.OnComponentInputContext","title":"OnComponentInputContext","text":"<p>Attributes:</p> <ul> <li> <code>args</code>               (<code>List</code>)           \u2013            </li> <li> <code>component</code>               (<code>Component</code>)           \u2013            </li> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> <li> <code>component_id</code>               (<code>str</code>)           \u2013            </li> <li> <code>context</code>               (<code>Context</code>)           \u2013            </li> <li> <code>kwargs</code>               (<code>Dict</code>)           \u2013            </li> <li> <code>slots</code>               (<code>Dict</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentInputContext.args","title":"args  <code>instance-attribute</code>","text":"<pre><code>args: List\n</code></pre> <p>See source code</p> <p>List of positional arguments passed to the component</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.component","title":"component  <code>instance-attribute</code>","text":"<pre><code>component: Component\n</code></pre> <p>See source code</p> <p>The Component instance that received the input and is being rendered</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The Component class</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.component_id","title":"component_id  <code>instance-attribute</code>","text":"<pre><code>component_id: str\n</code></pre> <p>See source code</p> <p>The unique identifier for this component instance</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.context","title":"context  <code>instance-attribute</code>","text":"<pre><code>context: Context\n</code></pre> <p>See source code</p> <p>The Django template Context object</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.kwargs","title":"kwargs  <code>instance-attribute</code>","text":"<pre><code>kwargs: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of keyword arguments passed to the component</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.slots","title":"slots  <code>instance-attribute</code>","text":"<pre><code>slots: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of slot definitions</p>"},{"location":"reference/api/#django_components.OnComponentRegisteredContext","title":"OnComponentRegisteredContext","text":"<p>Attributes:</p> <ul> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>registry</code>               (<code>ComponentRegistry</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentRegisteredContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The registered Component class</p>"},{"location":"reference/api/#django_components.OnComponentRegisteredContext.name","title":"name  <code>instance-attribute</code>","text":"<pre><code>name: str\n</code></pre> <p>See source code</p> <p>The name the component was registered under</p>"},{"location":"reference/api/#django_components.OnComponentRegisteredContext.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry: ComponentRegistry\n</code></pre> <p>See source code</p> <p>The registry the component was registered to</p>"},{"location":"reference/api/#django_components.OnComponentUnregisteredContext","title":"OnComponentUnregisteredContext","text":"<p>Attributes:</p> <ul> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>registry</code>               (<code>ComponentRegistry</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentUnregisteredContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The unregistered Component class</p>"},{"location":"reference/api/#django_components.OnComponentUnregisteredContext.name","title":"name  <code>instance-attribute</code>","text":"<pre><code>name: str\n</code></pre> <p>See source code</p> <p>The name the component was registered under</p>"},{"location":"reference/api/#django_components.OnComponentUnregisteredContext.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry: ComponentRegistry\n</code></pre> <p>See source code</p> <p>The registry the component was unregistered from</p>"},{"location":"reference/api/#django_components.OnRegistryCreatedContext","title":"OnRegistryCreatedContext","text":"<p>Attributes:</p> <ul> <li> <code>registry</code>               (<code>ComponentRegistry</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnRegistryCreatedContext.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry: ComponentRegistry\n</code></pre> <p>See source code</p> <p>The created ComponentRegistry instance</p>"},{"location":"reference/api/#django_components.OnRegistryDeletedContext","title":"OnRegistryDeletedContext","text":"<p>Attributes:</p> <ul> <li> <code>registry</code>               (<code>ComponentRegistry</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnRegistryDeletedContext.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry: ComponentRegistry\n</code></pre> <p>See source code</p> <p>The to-be-deleted ComponentRegistry instance</p>"},{"location":"reference/api/#django_components.RegistrySettings","title":"RegistrySettings","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>Configuration for a <code>ComponentRegistry</code>.</p> <p>These settings define how the components registered with this registry will behave when rendered.</p> <pre><code>from django_components import ComponentRegistry, RegistrySettings\n\nregistry_settings = RegistrySettings(\n    context_behavior=\"django\",\n    tag_formatter=\"django_components.component_shorthand_formatter\",\n)\n\nregistry = ComponentRegistry(settings=registry_settings)\n</code></pre> <p>Attributes:</p> <ul> <li> <code>CONTEXT_BEHAVIOR</code>               (<code>Optional[ContextBehaviorType]</code>)           \u2013            </li> <li> <code>TAG_FORMATTER</code>               (<code>Optional[Union[TagFormatterABC, str]]</code>)           \u2013            </li> <li> <code>context_behavior</code>               (<code>Optional[ContextBehaviorType]</code>)           \u2013            </li> <li> <code>tag_formatter</code>               (<code>Optional[Union[TagFormatterABC, str]]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.RegistrySettings.CONTEXT_BEHAVIOR","title":"CONTEXT_BEHAVIOR  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>CONTEXT_BEHAVIOR: Optional[ContextBehaviorType] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>context_behavior</code> instead. Will be removed in v1.</p> <p>Same as the global <code>COMPONENTS.context_behavior</code> setting, but for this registry.</p> <p>If omitted, defaults to the global <code>COMPONENTS.context_behavior</code> setting.</p>"},{"location":"reference/api/#django_components.RegistrySettings.TAG_FORMATTER","title":"TAG_FORMATTER  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>TAG_FORMATTER: Optional[Union[TagFormatterABC, str]] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>tag_formatter</code> instead. Will be removed in v1.</p> <p>Same as the global <code>COMPONENTS.tag_formatter</code> setting, but for this registry.</p> <p>If omitted, defaults to the global <code>COMPONENTS.tag_formatter</code> setting.</p>"},{"location":"reference/api/#django_components.RegistrySettings.context_behavior","title":"context_behavior  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>context_behavior: Optional[ContextBehaviorType] = None\n</code></pre> <p>See source code</p> <p>Same as the global <code>COMPONENTS.context_behavior</code> setting, but for this registry.</p> <p>If omitted, defaults to the global <code>COMPONENTS.context_behavior</code> setting.</p>"},{"location":"reference/api/#django_components.RegistrySettings.tag_formatter","title":"tag_formatter  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>tag_formatter: Optional[Union[TagFormatterABC, str]] = None\n</code></pre> <p>See source code</p> <p>Same as the global <code>COMPONENTS.tag_formatter</code> setting, but for this registry.</p> <p>If omitted, defaults to the global <code>COMPONENTS.tag_formatter</code> setting.</p>"},{"location":"reference/api/#django_components.Slot","title":"Slot  <code>dataclass</code>","text":"<pre><code>Slot(\n    content_func: SlotFunc[TSlotData],\n    escaped: bool = False,\n    component_name: Optional[str] = None,\n    slot_name: Optional[str] = None,\n    nodelist: Optional[NodeList] = None,\n)\n</code></pre> <p>Bases: <code>typing.Generic</code></p> <p>See source code</p> <p>This class holds the slot content function along with related metadata.</p> <p>Attributes:</p> <ul> <li> <code>component_name</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>content_func</code>               (<code>SlotFunc[TSlotData]</code>)           \u2013            </li> <li> <code>do_not_call_in_templates</code>               (<code>bool</code>)           \u2013            </li> <li> <code>escaped</code>               (<code>bool</code>)           \u2013            </li> <li> <code>nodelist</code>               (<code>Optional[NodeList]</code>)           \u2013            </li> <li> <code>slot_name</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.Slot.component_name","title":"component_name  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>component_name: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the component that originally defined or accepted this slot fill.</p>"},{"location":"reference/api/#django_components.Slot.content_func","title":"content_func  <code>instance-attribute</code>","text":"<pre><code>content_func: SlotFunc[TSlotData]\n</code></pre>"},{"location":"reference/api/#django_components.Slot.do_not_call_in_templates","title":"do_not_call_in_templates  <code>property</code>","text":"<pre><code>do_not_call_in_templates: bool\n</code></pre>"},{"location":"reference/api/#django_components.Slot.escaped","title":"escaped  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>escaped: bool = False\n</code></pre> <p>See source code</p> <p>Whether the slot content has been escaped.</p>"},{"location":"reference/api/#django_components.Slot.nodelist","title":"nodelist  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>nodelist: Optional[NodeList] = None\n</code></pre> <p>See source code</p> <p>Nodelist of the slot content.</p>"},{"location":"reference/api/#django_components.Slot.slot_name","title":"slot_name  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>slot_name: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the slot that originally defined or accepted this slot fill.</p>"},{"location":"reference/api/#django_components.SlotContent","title":"SlotContent  <code>module-attribute</code>","text":"<pre><code>SlotContent = Union[SlotResult, SlotFunc[TSlotData], Slot[TSlotData]]\n</code></pre>"},{"location":"reference/api/#django_components.SlotFunc","title":"SlotFunc","text":""},{"location":"reference/api/#django_components.SlotRef","title":"SlotRef","text":"<pre><code>SlotRef(slot: SlotNode, context: Context)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>SlotRef allows to treat a slot as a variable. The slot is rendered only once the instance is coerced to string.</p> <p>This is used to access slots as variables inside the templates. When a SlotRef is rendered in the template with <code>{{ my_lazy_slot }}</code>, it will output the contents of the slot.</p>"},{"location":"reference/api/#django_components.SlotResult","title":"SlotResult  <code>module-attribute</code>","text":"<pre><code>SlotResult = Union[str, SafeString]\n</code></pre>"},{"location":"reference/api/#django_components.TagFormatterABC","title":"TagFormatterABC","text":"<p>Bases: <code>abc.ABC</code></p> <p>See source code</p> <p>Abstract base class for defining custom tag formatters.</p> <p>Tag formatters define how the component tags are used in the template.</p> <p>Read more about Tag formatter.</p> <p>For example, with the default tag formatter (<code>ComponentFormatter</code>), components are written as:</p> <pre><code>{% component \"comp_name\" %}\n{% endcomponent %}\n</code></pre> <p>While with the shorthand tag formatter (<code>ShorthandComponentFormatter</code>), components are written as: <pre><code>{% comp_name %}\n{% endcomp_name %}\n</code></pre></p> <p>Example:</p> <p>Implementation for <code>ShorthandComponentFormatter</code>:</p> <pre><code>from djagno_components import TagFormatterABC, TagResult\n\nclass ShorthandComponentFormatter(TagFormatterABC):\n    def start_tag(self, name: str) -&gt; str:\n        return name\n\n    def end_tag(self, name: str) -&gt; str:\n        return f\"end{name}\"\n\n    def parse(self, tokens: List[str]) -&gt; TagResult:\n        tokens = [*tokens]\n        name = tokens.pop(0)\n        return TagResult(name, tokens)\n</code></pre> <p>Methods:</p> <ul> <li> <code>end_tag</code>             \u2013              </li> <li> <code>parse</code>             \u2013              </li> <li> <code>start_tag</code>             \u2013              </li> </ul>"},{"location":"reference/api/#django_components.TagFormatterABC.end_tag","title":"end_tag  <code>abstractmethod</code>","text":"<pre><code>end_tag(name: str) -&gt; str\n</code></pre> <p>See source code</p> <p>Formats the end tag of a block component.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>Component's registered name. Required.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>str</code> (              <code>str</code> )          \u2013            <p>The formatted end tag.</p> </li> </ul>"},{"location":"reference/api/#django_components.TagFormatterABC.parse","title":"parse  <code>abstractmethod</code>","text":"<pre><code>parse(tokens: List[str]) -&gt; TagResult\n</code></pre> <p>See source code</p> <p>Given the tokens (words) passed to a component start tag, this function extracts the component name from the tokens list, and returns <code>TagResult</code>, which is a tuple of <code>(component_name, remaining_tokens)</code>.</p> <p>Parameters:</p> <ul> <li> <code>tokens</code>               (<code>[List(str]</code>)           \u2013            <p>List of tokens passed to the component tag.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>TagResult</code> (              <code>TagResult</code> )          \u2013            <p>Parsed component name and remaining tokens.</p> </li> </ul> <p>Example:</p> <p>Assuming we used a component in a template like this:</p> <pre><code>{% component \"my_comp\" key=val key2=val2 %}\n{% endcomponent %}\n</code></pre> <p>This function receives a list of tokens:</p> <pre><code>['component', '\"my_comp\"', 'key=val', 'key2=val2']\n</code></pre> <ul> <li><code>component</code> is the tag name, which we drop.</li> <li><code>\"my_comp\"</code> is the component name, but we must remove the extra quotes.</li> <li>The remaining tokens we pass unmodified, as that's the input to the component.</li> </ul> <p>So in the end, we return:</p> <pre><code>TagResult('my_comp', ['key=val', 'key2=val2'])\n</code></pre>"},{"location":"reference/api/#django_components.TagFormatterABC.start_tag","title":"start_tag  <code>abstractmethod</code>","text":"<pre><code>start_tag(name: str) -&gt; str\n</code></pre> <p>See source code</p> <p>Formats the start tag of a component.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>Component's registered name. Required.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>str</code> (              <code>str</code> )          \u2013            <p>The formatted start tag.</p> </li> </ul>"},{"location":"reference/api/#django_components.TagResult","title":"TagResult","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>The return value from <code>TagFormatter.parse()</code>.</p> <p>Read more about Tag formatter.</p> <p>Attributes:</p> <ul> <li> <code>component_name</code>               (<code>str</code>)           \u2013            </li> <li> <code>tokens</code>               (<code>List[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.TagResult.component_name","title":"component_name  <code>instance-attribute</code>","text":"<pre><code>component_name: str\n</code></pre> <p>See source code</p> <p>Component name extracted from the template tag</p> <p>For example, if we had tag</p> <pre><code>{% component \"my_comp\" key=val key2=val2 %}\n</code></pre> <p>Then <code>component_name</code> would be <code>my_comp</code>.</p>"},{"location":"reference/api/#django_components.TagResult.tokens","title":"tokens  <code>instance-attribute</code>","text":"<pre><code>tokens: List[str]\n</code></pre> <p>See source code</p> <p>Remaining tokens (words) that were passed to the tag, with component name removed</p> <p>For example, if we had tag</p> <pre><code>{% component \"my_comp\" key=val key2=val2 %}\n</code></pre> <p>Then <code>tokens</code> would be <code>['key=val', 'key2=val2']</code>.</p>"},{"location":"reference/api/#django_components.URLRoute","title":"URLRoute  <code>dataclass</code>","text":"<pre><code>URLRoute(\n    path: str,\n    handler: Optional[URLRouteHandler] = None,\n    children: List[URLRoute] = list(),\n    name: Optional[str] = None,\n    extra: Dict[str, Any] = dict(),\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Framework-agnostic route definition.</p> <p>This is similar to Django's <code>URLPattern</code> object created with <code>django.urls.path()</code>.</p> <p>The <code>URLRoute</code> must either define a <code>handler</code> function or have a list of child routes <code>children</code>. If both are defined, an error will be raised.</p> <p>Example:</p> <pre><code>URLRoute(\"/my/path\", handler=my_handler, name=\"my_name\", extra={\"kwargs\": {\"my_extra\": \"my_value\"}})\n</code></pre> <p>Is equivalent to:</p> <pre><code>django.urls.path(\"/my/path\", my_handler, name=\"my_name\", kwargs={\"my_extra\": \"my_value\"})\n</code></pre> <p>With children:</p> <pre><code>URLRoute(\n    \"/my/path\",\n    name=\"my_name\",\n    extra={\"kwargs\": {\"my_extra\": \"my_value\"}},\n    children=[\n        URLRoute(\n            \"/child/&lt;str:name&gt;/\",\n            handler=my_handler,\n            name=\"my_name\",\n            extra={\"kwargs\": {\"my_extra\": \"my_value\"}},\n        ),\n        URLRoute(\"/other/&lt;int:id&gt;/\", handler=other_handler),\n    ],\n)\n</code></pre> <p>Attributes:</p> <ul> <li> <code>children</code>               (<code>List[URLRoute]</code>)           \u2013            </li> <li> <code>extra</code>               (<code>Dict[str, Any]</code>)           \u2013            </li> <li> <code>handler</code>               (<code>Optional[URLRouteHandler]</code>)           \u2013            </li> <li> <code>name</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>path</code>               (<code>str</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.URLRoute.children","title":"children  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>children: List[URLRoute] = field(default_factory=list)\n</code></pre>"},{"location":"reference/api/#django_components.URLRoute.extra","title":"extra  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>extra: Dict[str, Any] = field(default_factory=dict)\n</code></pre>"},{"location":"reference/api/#django_components.URLRoute.handler","title":"handler  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>handler: Optional[URLRouteHandler] = None\n</code></pre>"},{"location":"reference/api/#django_components.URLRoute.name","title":"name  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>name: Optional[str] = None\n</code></pre>"},{"location":"reference/api/#django_components.URLRoute.path","title":"path  <code>instance-attribute</code>","text":"<pre><code>path: str\n</code></pre>"},{"location":"reference/api/#django_components.URLRouteHandler","title":"URLRouteHandler","text":"<p>Bases: <code>typing.Protocol</code></p> <p>See source code</p> <p>Framework-agnostic 'view' function for routes</p>"},{"location":"reference/api/#django_components.all_components","title":"all_components","text":"<pre><code>all_components() -&gt; List[Type[Component]]\n</code></pre> <p>See source code</p> <p>Get a list of all created <code>Component</code> classes.</p>"},{"location":"reference/api/#django_components.all_registries","title":"all_registries","text":"<pre><code>all_registries() -&gt; List[ComponentRegistry]\n</code></pre> <p>See source code</p> <p>Get a list of all created <code>ComponentRegistry</code> instances.</p>"},{"location":"reference/api/#django_components.autodiscover","title":"autodiscover","text":"<pre><code>autodiscover(map_module: Optional[Callable[[str], str]] = None) -&gt; List[str]\n</code></pre> <p>See source code</p> <p>Search for all python files in <code>COMPONENTS.dirs</code> and <code>COMPONENTS.app_dirs</code> and import them.</p> <p>See Autodiscovery.</p> <p>NOTE: Subdirectories and files starting with an underscore <code>_</code> (except for <code>__init__.py</code> are ignored.</p> <p>Parameters:</p> <ul> <li> <code>map_module</code>               (<code>Callable[[str], str]</code>, default:                   <code>None</code> )           \u2013            <p>Map the module paths with <code>map_module</code> function.        This serves as an escape hatch for when you need to use this function in tests.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>List[str]</code>           \u2013            <p>List[str]: A list of module paths of imported files.</p> </li> </ul> <p>To get the same list of modules that <code>autodiscover()</code> would return, but without importing them, use <code>get_component_files()</code>:</p> <pre><code>from django_components import get_component_files\n\nmodules = get_component_files(\".py\")\n</code></pre>"},{"location":"reference/api/#django_components.cached_template","title":"cached_template","text":"<pre><code>cached_template(\n    template_string: str,\n    template_cls: Optional[Type[Template]] = None,\n    origin: Optional[Origin] = None,\n    name: Optional[str] = None,\n    engine: Optional[Any] = None,\n) -&gt; Template\n</code></pre> <p>See source code</p> <p>Create a Template instance that will be cached as per the <code>COMPONENTS.template_cache_size</code> setting.</p> <p>Parameters:</p> <ul> <li> <code>template_string</code>               (<code>str</code>)           \u2013            <p>Template as a string, same as the first argument to Django's            <code>Template</code>. Required.</p> </li> <li> <code>template_cls</code>               (<code>Type[Template]</code>, default:                   <code>None</code> )           \u2013            <p>Specify the Template class that should be instantiated.            Defaults to Django's <code>Template</code> class.</p> </li> <li> <code>origin</code>               (<code>Type[Origin]</code>, default:                   <code>None</code> )           \u2013            <p>Sets             <code>Template.Origin</code>.</p> </li> <li> <code>name</code>               (<code>Type[str]</code>, default:                   <code>None</code> )           \u2013            <p>Sets <code>Template.name</code></p> </li> <li> <code>engine</code>               (<code>Type[Any]</code>, default:                   <code>None</code> )           \u2013            <p>Sets <code>Template.engine</code></p> </li> </ul> <pre><code>from django_components import cached_template\n\ntemplate = cached_template(\"Variable: {{ variable }}\")\n\n# You can optionally specify Template class, and other Template inputs:\nclass MyTemplate(Template):\n    pass\n\ntemplate = cached_template(\n    \"Variable: {{ variable }}\",\n    template_cls=MyTemplate,\n    name=...\n    origin=...\n    engine=...\n)\n</code></pre>"},{"location":"reference/api/#django_components.get_component_dirs","title":"get_component_dirs","text":"<pre><code>get_component_dirs(include_apps: bool = True) -&gt; List[Path]\n</code></pre> <p>See source code</p> <p>Get directories that may contain component files.</p> <p>This is the heart of all features that deal with filesystem and file lookup. Autodiscovery, Django template resolution, static file resolution - They all use this.</p> <p>Parameters:</p> <ul> <li> <code>include_apps</code>               (<code>bool</code>, default:                   <code>True</code> )           \u2013            <p>Include directories from installed Django apps.            Defaults to <code>True</code>.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>List[Path]</code>           \u2013            <p>List[Path]: A list of directories that may contain component files.</p> </li> </ul> <p><code>get_component_dirs()</code> searches for dirs set in <code>COMPONENTS.dirs</code> settings. If none set, defaults to searching for a <code>\"components\"</code> app.</p> <p>In addition to that, also all installed Django apps are checked whether they contain directories as set in <code>COMPONENTS.app_dirs</code> (e.g. <code>[app]/components</code>).</p> <p>Notes:</p> <ul> <li> <p>Paths that do not point to directories are ignored.</p> </li> <li> <p><code>BASE_DIR</code> setting is required.</p> </li> <li> <p>The paths in <code>COMPONENTS.dirs</code>     must be absolute paths.</p> </li> </ul>"},{"location":"reference/api/#django_components.get_component_files","title":"get_component_files","text":"<pre><code>get_component_files(suffix: Optional[str] = None) -&gt; List[ComponentFileEntry]\n</code></pre> <p>See source code</p> <p>Search for files within the component directories (as defined in <code>get_component_dirs()</code>).</p> <p>Requires <code>BASE_DIR</code> setting to be set.</p> <p>Subdirectories and files starting with an underscore <code>_</code> (except <code>__init__.py</code>) are ignored.</p> <p>Parameters:</p> <ul> <li> <code>suffix</code>               (<code>Optional[str]</code>, default:                   <code>None</code> )           \u2013            <p>The suffix to search for. E.g. <code>.py</code>, <code>.js</code>, <code>.css</code>.            Defaults to <code>None</code>, which will search for all files.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>List[ComponentFileEntry]</code>           \u2013            <p>List[ComponentFileEntry] A list of entries that contain both the filesystem path and             the python import path (dot path).</p> </li> </ul> <p>Example:</p> <pre><code>from django_components import get_component_files\n\nmodules = get_component_files(\".py\")\n</code></pre>"},{"location":"reference/api/#django_components.import_libraries","title":"import_libraries","text":"<pre><code>import_libraries(map_module: Optional[Callable[[str], str]] = None) -&gt; List[str]\n</code></pre> <p>See source code</p> <p>Import modules set in <code>COMPONENTS.libraries</code> setting.</p> <p>See Autodiscovery.</p> <p>Parameters:</p> <ul> <li> <code>map_module</code>               (<code>Callable[[str], str]</code>, default:                   <code>None</code> )           \u2013            <p>Map the module paths with <code>map_module</code> function.        This serves as an escape hatch for when you need to use this function in tests.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>List[str]</code>           \u2013            <p>List[str]: A list of module paths of imported files.</p> </li> </ul> <p>Examples:</p> <p>Normal usage - load libraries after Django has loaded <pre><code>from django_components import import_libraries\n\nclass MyAppConfig(AppConfig):\n    def ready(self):\n        import_libraries()\n</code></pre></p> <p>Potential usage in tests <pre><code>from django_components import import_libraries\n\nimport_libraries(lambda path: path.replace(\"tests.\", \"myapp.\"))\n</code></pre></p>"},{"location":"reference/api/#django_components.register","title":"register","text":"<pre><code>register(name: str, registry: Optional[ComponentRegistry] = None) -&gt; Callable[\n    [Type[Component[ArgsType, KwargsType, SlotsType, DataType, JsDataType, CssDataType]]],\n    Type[Component[ArgsType, KwargsType, SlotsType, DataType, JsDataType, CssDataType]],\n]\n</code></pre> <p>See source code</p> <p>Class decorator for registering a component to a component registry.</p> <p>See Registering components.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>Registered name. This is the name by which the component will be accessed            from within a template when using the <code>{% component %}</code> tag. Required.</p> </li> <li> <code>registry</code>               (<code>ComponentRegistry</code>, default:                   <code>None</code> )           \u2013            <p>Specify the registry            to which to register this component. If omitted, component is registered to the default registry.</p> </li> </ul> <p>Raises:</p> <ul> <li> <code>AlreadyRegistered</code>             \u2013            <p>If there is already a component registered under the same name.</p> </li> </ul> <p>Examples:</p> <pre><code>from django_components import Component, register\n\n@register(\"my_component\")\nclass MyComponent(Component):\n    ...\n</code></pre> <p>Specifing <code>ComponentRegistry</code> the component should be registered to by setting the <code>registry</code> kwarg:</p> <pre><code>from django.template import Library\nfrom django_components import Component, ComponentRegistry, register\n\nmy_lib = Library()\nmy_reg = ComponentRegistry(library=my_lib)\n\n@register(\"my_component\", registry=my_reg)\nclass MyComponent(Component):\n    ...\n</code></pre>"},{"location":"reference/api/#django_components.registry","title":"registry  <code>module-attribute</code>","text":"<pre><code>registry: ComponentRegistry = ComponentRegistry()\n</code></pre> <p>See source code</p> <p>The default and global component registry. Use this instance to directly register or remove components:</p> <p>See Registering components.</p> <pre><code># Register components\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\n\n# Get single\nregistry.get(\"button\")\n\n# Get all\nregistry.all()\n\n# Check if component is registered\nregistry.has(\"button\")\n\n# Unregister single\nregistry.unregister(\"button\")\n\n# Unregister all\nregistry.clear()\n</code></pre>"},{"location":"reference/api/#django_components.render_dependencies","title":"render_dependencies","text":"<pre><code>render_dependencies(content: TContent, type: RenderType = 'document') -&gt; TContent\n</code></pre> <p>See source code</p> <p>Given a string that contains parts that were rendered by components, this function inserts all used JS and CSS.</p> <p>By default, the string is parsed as an HTML and: - CSS is inserted at the end of <code>&lt;head&gt;</code> (if present) - JS is inserted at the end of <code>&lt;body&gt;</code> (if present)</p> <p>If you used <code>{% component_js_dependencies %}</code> or <code>{% component_css_dependencies %}</code>, then the JS and CSS will be inserted only at these locations.</p> <p>Example: <pre><code>def my_view(request):\n    template = Template('''\n        {% load components %}\n        &lt;!doctype html&gt;\n        &lt;html&gt;\n            &lt;head&gt;&lt;/head&gt;\n            &lt;body&gt;\n                &lt;h1&gt;{{ table_name }}&lt;/h1&gt;\n                {% component \"table\" name=table_name / %}\n            &lt;/body&gt;\n        &lt;/html&gt;\n    ''')\n\n    html = template.render(\n        Context({\n            \"table_name\": request.GET[\"name\"],\n        })\n    )\n\n    # This inserts components' JS and CSS\n    processed_html = render_dependencies(html)\n\n    return HttpResponse(processed_html)\n</code></pre></p>"},{"location":"reference/api/#django_components.template_tag","title":"template_tag","text":"<pre><code>template_tag(\n    library: Library, tag: str, end_tag: Optional[str] = None, allowed_flags: Optional[List[str]] = None\n) -&gt; Callable[[Callable], Callable]\n</code></pre> <p>See source code</p> <p>A simplified version of creating a template tag based on <code>BaseNode</code>.</p> <p>Instead of defining the whole class, you can just define the <code>render()</code> method.</p> <pre><code>from django.template import Context, Library\nfrom django_components import BaseNode, template_tag\n\nlibrary = Library()\n\n@template_tag(\n    library,\n    tag=\"mytag\",\n    end_tag=\"endmytag\",\n    allowed_flags=[\"required\"],\n)\ndef mytag(node: BaseNode, context: Context, name: str, **kwargs: Any) -&gt; str:\n    return f\"Hello, {name}!\"\n</code></pre> <p>This will allow the template tag <code>{% mytag %}</code> to be used like this:</p> <pre><code>{% mytag name=\"John\" %}\n{% mytag name=\"John\" required %} ... {% endmytag %}\n</code></pre> <p>The given function will be wrapped in a class that inherits from <code>BaseNode</code>.</p> <p>And this class will be registered with the given library.</p> <p>The function MUST accept at least two positional arguments: <code>node</code> and <code>context</code></p> <ul> <li><code>node</code> is the <code>BaseNode</code> instance.</li> <li><code>context</code> is the <code>Context</code>     of the template.</li> </ul> <p>Any extra parameters defined on this function will be part of the tag's input parameters.</p> <p>For more info, see <code>BaseNode.render()</code>.</p>"},{"location":"reference/commands/","title":"Commands","text":""},{"location":"reference/commands/#commands","title":"Commands","text":"<p>These are all the Django management commands that will be added by installing <code>django_components</code>:</p>"},{"location":"reference/commands/#components","title":"<code>components</code>","text":"<pre><code>usage: python manage.py  components [-h] {create,upgrade,ext,list} ...\n</code></pre> <p>See source code</p> <p>The entrypoint for the 'components' commands.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> </ul> <p>Subcommands:</p> <ul> <li><code>create</code><ul> <li>Create a new django component.</li> </ul> </li> <li><code>upgrade</code><ul> <li>Upgrade django components syntax from '{% component_block ... %}' to '{% component ... %}'.</li> </ul> </li> <li><code>ext</code><ul> <li>Run extension commands.</li> </ul> </li> <li><code>list</code><ul> <li>List all components created in this project.</li> </ul> </li> </ul> <p>The entrypoint for the \"components\" commands.</p> <pre><code>python manage.py components list\npython manage.py components create &lt;name&gt;\npython manage.py components upgrade\npython manage.py components ext list\npython manage.py components ext run &lt;extension&gt; &lt;command&gt;\n</code></pre>"},{"location":"reference/commands/#components-create","title":"<code>components create</code>","text":"<pre><code>usage: python manage.py components create [-h] [--path PATH] [--js JS] [--css CSS] [--template TEMPLATE]\n              [--force] [--verbose] [--dry-run]\n              name\n</code></pre> <p>See source code</p> <p>Create a new django component.</p> <p>Positional Arguments:</p> <ul> <li><code>name</code><ul> <li>The name of the component to create. This is a required argument.</li> </ul> </li> </ul> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--path PATH</code><ul> <li>The path to the component's directory. This is an optional argument. If not provided, the command will use the <code>COMPONENTS.dirs</code> setting from your Django settings.</li> </ul> </li> <li><code>--js JS</code><ul> <li>The name of the JavaScript file. This is an optional argument. The default value is <code>script.js</code>.</li> </ul> </li> <li><code>--css CSS</code><ul> <li>The name of the CSS file. This is an optional argument. The default value is <code>style.css</code>.</li> </ul> </li> <li><code>--template TEMPLATE</code><ul> <li>The name of the template file. This is an optional argument. The default value is <code>template.html</code>.</li> </ul> </li> <li><code>--force</code><ul> <li>This option allows you to overwrite existing files if they exist. This is an optional argument.</li> </ul> </li> <li><code>--verbose</code><ul> <li>This option allows the command to print additional information during component creation. This is an optional argument.</li> </ul> </li> <li><code>--dry-run</code><ul> <li>This option allows you to simulate component creation without actually creating any files. This is an optional argument. The default value is <code>False</code>.</li> </ul> </li> </ul>"},{"location":"reference/commands/#usage","title":"Usage","text":"<p>To use the command, run the following command in your terminal:</p> <pre><code>python manage.py components create &lt;name&gt; --path &lt;path&gt; --js &lt;js_filename&gt; --css &lt;css_filename&gt; --template &lt;template_filename&gt; --force --verbose --dry-run\n</code></pre> <p>Replace <code>&lt;name&gt;</code>, <code>&lt;path&gt;</code>, <code>&lt;js_filename&gt;</code>, <code>&lt;css_filename&gt;</code>, and <code>&lt;template_filename&gt;</code> with your desired values.</p>"},{"location":"reference/commands/#examples","title":"Examples","text":"<p>Here are some examples of how you can use the command:</p> <p>Creating a Component with Default Settings</p> <p>To create a component with the default settings, you only need to provide the name of the component:</p> <pre><code>python manage.py components create my_component\n</code></pre> <p>This will create a new component named <code>my_component</code> in the <code>components</code> directory of your Django project. The JavaScript, CSS, and template files will be named <code>script.js</code>, <code>style.css</code>, and <code>template.html</code>, respectively.</p> <p>Creating a Component with Custom Settings</p> <p>You can also create a component with custom settings by providing additional arguments:</p> <pre><code>python manage.py components create new_component --path my_components --js my_script.js --css my_style.css --template my_template.html\n</code></pre> <p>This will create a new component named <code>new_component</code> in the <code>my_components</code> directory. The JavaScript, CSS, and template files will be named <code>my_script.js</code>, <code>my_style.css</code>, and <code>my_template.html</code>, respectively.</p> <p>Overwriting an Existing Component</p> <p>If you want to overwrite an existing component, you can use the <code>--force</code> option:</p> <pre><code>python manage.py components create my_component --force\n</code></pre> <p>This will overwrite the existing <code>my_component</code> if it exists.</p> <p>Simulating Component Creation</p> <p>If you want to simulate the creation of a component without actually creating any files, you can use the <code>--dry-run</code> option:</p> <pre><code>python manage.py components create my_component --dry-run\n</code></pre> <p>This will simulate the creation of <code>my_component</code> without creating any files.</p>"},{"location":"reference/commands/#components-upgrade","title":"<code>components upgrade</code>","text":"<pre><code>usage: python manage.py components upgrade [-h] [--path PATH]\n</code></pre> <p>See source code</p> <p>Upgrade django components syntax from '{% component_block ... %}' to '{% component ... %}'.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--path PATH</code><ul> <li>Path to search for components</li> </ul> </li> </ul>"},{"location":"reference/commands/#components-ext","title":"<code>components ext</code>","text":"<pre><code>usage: python manage.py components ext [-h] {list,run} ...\n</code></pre> <p>See source code</p> <p>Run extension commands.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> </ul> <p>Subcommands:</p> <ul> <li><code>list</code><ul> <li>List all extensions.</li> </ul> </li> <li><code>run</code><ul> <li>Run a command added by an extension.</li> </ul> </li> </ul> <p>Run extension commands.</p> <pre><code>python manage.py components ext list\npython manage.py components ext run &lt;extension&gt; &lt;command&gt;\n</code></pre>"},{"location":"reference/commands/#components-ext-list","title":"<code>components ext list</code>","text":"<pre><code>usage: python manage.py components ext list [-h] [--all] [--columns COLUMNS] [-s]\n</code></pre> <p>See source code</p> <p>List all extensions.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--all</code><ul> <li>Show all columns. Same as <code>--columns name</code>.</li> </ul> </li> <li><code>--columns COLUMNS</code><ul> <li>Comma-separated list of columns to show. Available columns: name. Defaults to <code>--columns name</code>.</li> </ul> </li> <li><code>-s</code>, <code>--simple</code><ul> <li>Only show table data, without headers. Use this option for generating machine-readable output.</li> </ul> </li> </ul> <p>List all extensions.</p> <pre><code>python manage.py components ext list\n</code></pre> <p>Prints the list of installed extensions:</p> <pre><code>name\n==============\nview\nmy_extension\n</code></pre> <p>To specify which columns to show, use the <code>--columns</code> flag:</p> <pre><code>python manage.py components ext list --columns name\n</code></pre> <p>Which prints:</p> <pre><code>name\n==============\nview\nmy_extension\n</code></pre> <p>To print out all columns, use the <code>--all</code> flag:</p> <pre><code>python manage.py components ext list --all\n</code></pre> <p>If you need to omit the title in order to programmatically post-process the output, you can use the <code>--simple</code> (or <code>-s</code>) flag:</p> <pre><code>python manage.py components ext list --simple\n</code></pre> <p>Which prints just:</p> <pre><code>view\nmy_extension\n</code></pre>"},{"location":"reference/commands/#components-ext-run","title":"<code>components ext run</code>","text":"<pre><code>usage: python manage.py components ext run [-h]\n</code></pre> <p>See source code</p> <p>Run a command added by an extension.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> </ul> <p>Run a command added by an extension.</p> <p>Each extension can add its own commands, which will be available to run with this command.</p> <p>For example, if you define and install the following extension:</p> <pre><code>from django_components import ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n    def handle(self, *args, **kwargs):\n        print(\"Hello, world!\")\n\nclass MyExt(ComponentExtension):\n    name = \"my_ext\"\n    commands = [HelloCommand]\n</code></pre> <p>You can run the <code>hello</code> command with:</p> <pre><code>python manage.py components ext run my_ext hello\n</code></pre> <p>You can also define arguments for the command, which will be passed to the command's <code>handle</code> method.</p> <pre><code>from django_components import CommandArg, ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n    arguments = [\n        CommandArg(name=\"name\", help=\"The name to say hello to\"),\n        CommandArg(name=[\"--shout\", \"-s\"], action=\"store_true\"),\n    ]\n\n    def handle(self, name: str, *args, **kwargs):\n        shout = kwargs.get(\"shout\", False)\n        msg = f\"Hello, {name}!\"\n        if shout:\n            msg = msg.upper()\n        print(msg)\n</code></pre> <p>You can run the command with:</p> <pre><code>python manage.py components ext run my_ext hello --name John --shout\n</code></pre> <p>Note</p> <p>Command arguments and options are based on Python's <code>argparse</code> module.</p> <p>For more information, see the argparse documentation.</p>"},{"location":"reference/commands/#components-list","title":"<code>components list</code>","text":"<pre><code>usage: python manage.py components list [-h] [--all] [--columns COLUMNS] [-s]\n</code></pre> <p>See source code</p> <p>List all components created in this project.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--all</code><ul> <li>Show all columns. Same as <code>--columns name,full_name,path</code>.</li> </ul> </li> <li><code>--columns COLUMNS</code><ul> <li>Comma-separated list of columns to show. Available columns: name, full_name, path. Defaults to <code>--columns full_name,path</code>.</li> </ul> </li> <li><code>-s</code>, <code>--simple</code><ul> <li>Only show table data, without headers. Use this option for generating machine-readable output.</li> </ul> </li> </ul> <p>List all components.</p> <pre><code>python manage.py components list\n</code></pre> <p>Prints the list of available components:</p> <pre><code>full_name                                                     path\n==================================================================================================\nproject.pages.project.ProjectPage                             ./project/pages/project\nproject.components.dashboard.ProjectDashboard                 ./project/components/dashboard\nproject.components.dashboard_action.ProjectDashboardAction    ./project/components/dashboard_action\n</code></pre> <p>To specify which columns to show, use the <code>--columns</code> flag:</p> <pre><code>python manage.py components list --columns name,full_name,path\n</code></pre> <p>Which prints:</p> <pre><code>name                      full_name                                                     path\n==================================================================================================\nProjectPage               project.pages.project.ProjectPage                             ./project/pages/project\nProjectDashboard          project.components.dashboard.ProjectDashboard                 ./project/components/dashboard\nProjectDashboardAction    project.components.dashboard_action.ProjectDashboardAction    ./project/components/dashboard_action\n</code></pre> <p>To print out all columns, use the <code>--all</code> flag:</p> <pre><code>python manage.py components list --all\n</code></pre> <p>If you need to omit the title in order to programmatically post-process the output, you can use the <code>--simple</code> (or <code>-s</code>) flag:</p> <pre><code>python manage.py components list --simple\n</code></pre> <p>Which prints just:</p> <pre><code>ProjectPage               project.pages.project.ProjectPage                             ./project/pages/project\nProjectDashboard          project.components.dashboard.ProjectDashboard                 ./project/components/dashboard\nProjectDashboardAction    project.components.dashboard_action.ProjectDashboardAction    ./project/components/dashboard_action\n</code></pre>"},{"location":"reference/commands/#upgradecomponent","title":"<code>upgradecomponent</code>","text":"<pre><code>usage: upgradecomponent [-h] [--path PATH] [--version] [-v {0,1,2,3}]\n                        [--settings SETTINGS] [--pythonpath PYTHONPATH]\n                        [--traceback] [--no-color] [--force-color]\n                        [--skip-checks]\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>components upgrade</code> instead.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--path PATH</code><ul> <li>Path to search for components</li> </ul> </li> <li><code>--version</code><ul> <li>Show program's version number and exit.</li> </ul> </li> <li><code>-v</code>, <code>--verbosity {0,1,2,3}</code><ul> <li>Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output</li> </ul> </li> <li><code>--settings SETTINGS</code><ul> <li>The Python path to a settings module, e.g. \"myproject.settings.main\". If this isn't provided, the DJANGO_SETTINGS_MODULE environment variable will be used.</li> </ul> </li> <li><code>--pythonpath PYTHONPATH</code><ul> <li>A directory to add to the Python path, e.g. \"/home/djangoprojects/myproject\".</li> </ul> </li> <li><code>--traceback</code><ul> <li>Raise on CommandError exceptions.</li> </ul> </li> <li><code>--no-color</code><ul> <li>Don't colorize the command output.</li> </ul> </li> <li><code>--force-color</code><ul> <li>Force colorization of the command output.</li> </ul> </li> <li><code>--skip-checks</code><ul> <li>Skip system checks.</li> </ul> </li> </ul> <p>Deprecated. Use <code>components upgrade</code> instead.</p>"},{"location":"reference/commands/#startcomponent","title":"<code>startcomponent</code>","text":"<pre><code>usage: startcomponent [-h] [--path PATH] [--js JS] [--css CSS]\n                      [--template TEMPLATE] [--force] [--verbose] [--dry-run]\n                      [--version] [-v {0,1,2,3}] [--settings SETTINGS]\n                      [--pythonpath PYTHONPATH] [--traceback] [--no-color]\n                      [--force-color] [--skip-checks]\n                      name\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>components create</code> instead.</p> <p>Positional Arguments:</p> <ul> <li><code>name</code><ul> <li>The name of the component to create. This is a required argument.</li> </ul> </li> </ul> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--path PATH</code><ul> <li>The path to the component's directory. This is an optional argument. If not provided, the command will use the <code>COMPONENTS.dirs</code> setting from your Django settings.</li> </ul> </li> <li><code>--js JS</code><ul> <li>The name of the JavaScript file. This is an optional argument. The default value is <code>script.js</code>.</li> </ul> </li> <li><code>--css CSS</code><ul> <li>The name of the CSS file. This is an optional argument. The default value is <code>style.css</code>.</li> </ul> </li> <li><code>--template TEMPLATE</code><ul> <li>The name of the template file. This is an optional argument. The default value is <code>template.html</code>.</li> </ul> </li> <li><code>--force</code><ul> <li>This option allows you to overwrite existing files if they exist. This is an optional argument.</li> </ul> </li> <li><code>--verbose</code><ul> <li>This option allows the command to print additional information during component creation. This is an optional argument.</li> </ul> </li> <li><code>--dry-run</code><ul> <li>This option allows you to simulate component creation without actually creating any files. This is an optional argument. The default value is <code>False</code>.</li> </ul> </li> <li><code>--version</code><ul> <li>Show program's version number and exit.</li> </ul> </li> <li><code>-v</code>, <code>--verbosity {0,1,2,3}</code><ul> <li>Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output</li> </ul> </li> <li><code>--settings SETTINGS</code><ul> <li>The Python path to a settings module, e.g. \"myproject.settings.main\". If this isn't provided, the DJANGO_SETTINGS_MODULE environment variable will be used.</li> </ul> </li> <li><code>--pythonpath PYTHONPATH</code><ul> <li>A directory to add to the Python path, e.g. \"/home/djangoprojects/myproject\".</li> </ul> </li> <li><code>--traceback</code><ul> <li>Raise on CommandError exceptions.</li> </ul> </li> <li><code>--no-color</code><ul> <li>Don't colorize the command output.</li> </ul> </li> <li><code>--force-color</code><ul> <li>Force colorization of the command output.</li> </ul> </li> <li><code>--skip-checks</code><ul> <li>Skip system checks.</li> </ul> </li> </ul> <p>Deprecated. Use <code>components create</code> instead.</p>"},{"location":"reference/components/","title":"Components","text":""},{"location":"reference/components/#components","title":"Components","text":"<p>These are the components provided by django_components.</p>"},{"location":"reference/components/#django_components.components.dynamic.DynamicComponent","title":"<code>DynamicComponent</code>","text":"<p>Bases: <code>django_components.component.Component</code></p> <p>See source code</p> <p>This component is given a registered name or a reference to another component, and behaves as if the other component was in its place.</p> <p>The args, kwargs, and slot fills are all passed down to the underlying component.</p> <p>Parameters:</p> <ul> <li> <code>is</code>               (<code>str | Type[Component]</code>)           \u2013            <p>Component that should be rendered. Either a registered name of a component, or a Component class directly. Required.</p> </li> <li> <code>registry</code>               (<code>ComponentRegistry</code>, default:                   <code>None</code> )           \u2013            <p>Specify the registry            to search for the registered name. If omitted, all registries are searched until the first match.</p> </li> <li> <code>*args</code>           \u2013            <p>Additional data passed to the component.</p> </li> <li> <code>**kwargs</code>           \u2013            <p>Additional data passed to the component.</p> </li> </ul> <p>Slots:</p> <ul> <li>Any slots, depending on the actual component.</li> </ul> <p>Examples:</p> <p>Django <pre><code>{% component \"dynamic\" is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre></p> <p>Or in case you use the <code>django_components.component_shorthand_formatter</code> tag formatter:</p> <pre><code>{% dynamic is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% enddynamic %}\n</code></pre> <p>Python <pre><code>from django_components import DynamicComponent\n\nDynamicComponent.render(\n    kwargs={\n        \"is\": table_comp,\n        \"data\": table_data,\n        \"headers\": table_headers,\n    },\n    slots={\n        \"pagination\": PaginationComponent.render(\n            render_dependencies=False,\n        ),\n    },\n)\n</code></pre></p>"},{"location":"reference/components/#django_components.components.dynamic.DynamicComponent--use-cases","title":"Use cases","text":"<p>Dynamic components are suitable if you are writing something like a form component. You may design it such that users give you a list of input types, and you render components depending on the input types.</p> <p>While you could handle this with a series of if / else statements, that's not an extensible approach. Instead, you can use the dynamic component in place of normal components.</p>"},{"location":"reference/components/#django_components.components.dynamic.DynamicComponent--component-name","title":"Component name","text":"<p>By default, the dynamic component is registered under the name <code>\"dynamic\"</code>. In case of a conflict, you can set the <code>COMPONENTS.dynamic_component_name</code> setting to change the name used for the dynamic components.</p> <pre><code># settings.py\nCOMPONENTS = ComponentsSettings(\n    dynamic_component_name=\"my_dynamic\",\n)\n</code></pre> <p>After which you will be able to use the dynamic component with the new name: <pre><code>{% component \"my_dynamic\" is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre></p>"},{"location":"reference/exceptions/","title":"Exceptions","text":""},{"location":"reference/exceptions/#exceptions","title":"Exceptions","text":""},{"location":"reference/exceptions/#django_components.AlreadyRegistered","title":"AlreadyRegistered","text":"<p>Bases: <code>Exception</code></p> <p>See source code</p> <p>Raised when you try to register a Component, but it's already registered with given ComponentRegistry.</p>"},{"location":"reference/exceptions/#django_components.NotRegistered","title":"NotRegistered","text":"<p>Bases: <code>Exception</code></p> <p>See source code</p> <p>Raised when you try to access a Component, but it's NOT registered with given ComponentRegistry.</p>"},{"location":"reference/exceptions/#django_components.TagProtectedError","title":"TagProtectedError","text":"<p>Bases: <code>Exception</code></p> <p>See source code</p> <p>The way the <code>TagFormatter</code> works is that, based on which start and end tags are used for rendering components, the <code>ComponentRegistry</code> behind the scenes un-/registers the template tags with the associated instance of Django's <code>Library</code>.</p> <p>In other words, if I have registered a component <code>\"table\"</code>, and I use the shorthand syntax:</p> <pre><code>{% table ... %}\n{% endtable %}\n</code></pre> <p>Then <code>ComponentRegistry</code> registers the tag <code>table</code> onto the Django's Library instance.</p> <p>However, that means that if we registered a component <code>\"slot\"</code>, then we would overwrite the <code>{% slot %}</code> tag from django_components.</p> <p>Thus, this exception is raised when a component is attempted to be registered under a forbidden name, such that it would overwrite one of django_component's own template tags.</p>"},{"location":"reference/extension_hooks/","title":"Extension hooks","text":""},{"location":"reference/extension_hooks/#extension-hooks","title":"Extension Hooks","text":"<p>Overview of all the extension hooks available in Django Components.</p> <p>Read more on Extensions.</p> <p>Available data:</p> name type description <code>component_cls</code> <code>Type[Component]</code> The created Component class <p>Available data:</p> name type description <code>component_cls</code> <code>Type[Component]</code> The to-be-deleted Component class <p>Available data:</p> name type description <code>component</code> <code>Component</code> The Component instance that is being rendered <code>component_cls</code> <code>Type[Component]</code> The Component class <code>component_id</code> <code>str</code> The unique identifier for this component instance <code>context_data</code> <code>Dict</code> Dictionary of context data from <code>Component.get_context_data()</code> <code>css_data</code> <code>Dict</code> Dictionary of CSS data from <code>Component.get_css_data()</code> <code>js_data</code> <code>Dict</code> Dictionary of JavaScript data from <code>Component.get_js_data()</code> <p>Available data:</p> name type description <code>args</code> <code>List</code> List of positional arguments passed to the component <code>component</code> <code>Component</code> The Component instance that received the input and is being rendered <code>component_cls</code> <code>Type[Component]</code> The Component class <code>component_id</code> <code>str</code> The unique identifier for this component instance <code>context</code> <code>Context</code> The Django template Context object <code>kwargs</code> <code>Dict</code> Dictionary of keyword arguments passed to the component <code>slots</code> <code>Dict</code> Dictionary of slot definitions <p>Available data:</p> name type description <code>component_cls</code> <code>Type[Component]</code> The registered Component class <code>name</code> <code>str</code> The name the component was registered under <code>registry</code> <code>ComponentRegistry</code> The registry the component was registered to <p>Available data:</p> name type description <code>component_cls</code> <code>Type[Component]</code> The unregistered Component class <code>name</code> <code>str</code> The name the component was registered under <code>registry</code> <code>ComponentRegistry</code> The registry the component was unregistered from <p>Available data:</p> name type description <code>registry</code> <code>ComponentRegistry</code> The created ComponentRegistry instance <p>Available data:</p> name type description <code>registry</code> <code>ComponentRegistry</code> The to-be-deleted ComponentRegistry instance"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_class_created","title":"on_component_class_created","text":"<pre><code>on_component_class_created(ctx: OnComponentClassCreatedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a new <code>Component</code> class is created.</p> <p>This hook is called after the <code>Component</code> class is fully defined but before it's registered.</p> <p>Use this hook to perform any initialization or validation of the <code>Component</code> class.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentClassCreatedContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_class_created(self, ctx: OnComponentClassCreatedContext) -&gt; None:\n        # Add a new attribute to the Component class\n        ctx.component_cls.my_attr = \"my_value\"\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_class_deleted","title":"on_component_class_deleted","text":"<pre><code>on_component_class_deleted(ctx: OnComponentClassDeletedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is being deleted.</p> <p>This hook is called before the <code>Component</code> class is deleted from memory.</p> <p>Use this hook to perform any cleanup related to the <code>Component</code> class.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentClassDeletedContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_class_deleted(self, ctx: OnComponentClassDeletedContext) -&gt; None:\n        # Remove Component class from the extension's cache on deletion\n        self.cache.pop(ctx.component_cls, None)\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_data","title":"on_component_data","text":"<pre><code>on_component_data(ctx: OnComponentDataContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a Component was triggered to render, after a component's context and data methods have been processed.</p> <p>This hook is called after <code>Component.get_context_data()</code>, <code>Component.get_js_data()</code> and <code>Component.get_css_data()</code>.</p> <p>This hook runs after <code>on_component_input</code>.</p> <p>Use this hook to modify or validate the component's data before rendering.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentDataContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_data(self, ctx: OnComponentDataContext) -&gt; None:\n        # Add extra template variable to all components when they are rendered\n        ctx.context_data[\"my_template_var\"] = \"my_value\"\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_input","title":"on_component_input","text":"<pre><code>on_component_input(ctx: OnComponentInputContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> was triggered to render, but before a component's context and data methods are invoked.</p> <p>This hook is called before <code>Component.get_context_data()</code>, <code>Component.get_js_data()</code> and <code>Component.get_css_data()</code>.</p> <p>Use this hook to modify or validate component inputs before they're processed.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentInputContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_input(self, ctx: OnComponentInputContext) -&gt; None:\n        # Add extra kwarg to all components when they are rendered\n        ctx.kwargs[\"my_input\"] = \"my_value\"\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_registered","title":"on_component_registered","text":"<pre><code>on_component_registered(ctx: OnComponentRegisteredContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is registered with a <code>ComponentRegistry</code>.</p> <p>This hook is called after a <code>Component</code> class is successfully registered.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentRegisteredContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_registered(self, ctx: OnComponentRegisteredContext) -&gt; None:\n        print(f\"Component {ctx.component_cls} registered to {ctx.registry} as '{ctx.name}'\")\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_unregistered","title":"on_component_unregistered","text":"<pre><code>on_component_unregistered(ctx: OnComponentUnregisteredContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is unregistered from a <code>ComponentRegistry</code>.</p> <p>This hook is called after a <code>Component</code> class is removed from the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentUnregisteredContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_unregistered(self, ctx: OnComponentUnregisteredContext) -&gt; None:\n        print(f\"Component {ctx.component_cls} unregistered from {ctx.registry} as '{ctx.name}'\")\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_registry_created","title":"on_registry_created","text":"<pre><code>on_registry_created(ctx: OnRegistryCreatedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a new <code>ComponentRegistry</code> is created.</p> <p>This hook is called after a new <code>ComponentRegistry</code> instance is initialized.</p> <p>Use this hook to perform any initialization needed for the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnRegistryCreatedContext\n\nclass MyExtension(ComponentExtension):\n    def on_registry_created(self, ctx: OnRegistryCreatedContext) -&gt; None:\n        # Add a new attribute to the registry\n        ctx.registry.my_attr = \"my_value\"\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_registry_deleted","title":"on_registry_deleted","text":"<pre><code>on_registry_deleted(ctx: OnRegistryDeletedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>ComponentRegistry</code> is being deleted.</p> <p>This hook is called before a <code>ComponentRegistry</code> instance is deleted.</p> <p>Use this hook to perform any cleanup related to the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnRegistryDeletedContext\n\nclass MyExtension(ComponentExtension):\n    def on_registry_deleted(self, ctx: OnRegistryDeletedContext) -&gt; None:\n        # Remove registry from the extension's cache on deletion\n        self.cache.pop(ctx.registry, None)\n</code></pre>"},{"location":"reference/middlewares/","title":"Middlewares","text":""},{"location":"reference/middlewares/#middlewares","title":"Middlewares","text":""},{"location":"reference/middlewares/#django_components.dependencies.ComponentDependencyMiddleware","title":"<code>ComponentDependencyMiddleware</code>","text":"<p>Bases: <code>object</code></p> <p>See source code</p> <p>Middleware that inserts CSS/JS dependencies for all rendered components at points marked with template tags.</p>"},{"location":"reference/settings/","title":"Settings","text":""},{"location":"reference/settings/#settings","title":"Settings","text":"<p>You can configure django_components with a global <code>COMPONENTS</code> variable in your Django settings file, e.g. <code>settings.py</code>. By default you don't need it set, there are resonable defaults.</p> <p>To configure the settings you can instantiate <code>ComponentsSettings</code> for validation and type hints. Or, for backwards compatibility, you can also use plain dictionary:</p> <pre><code># settings.py\nfrom django_components import ComponentsSettings\n\nCOMPONENTS = ComponentsSettings(\n    autodiscover=True,\n    ...\n)\n\n# or\n\nCOMPONENTS = {\n    \"autodiscover\": True,\n    ...\n}\n</code></pre>"},{"location":"reference/settings/#settings-defaults","title":"Settings defaults","text":"<p>Here's overview of all available settings and their defaults:</p> <pre><code>defaults = ComponentsSettings(\n    autodiscover=True,\n    cache=None,\n    context_behavior=ContextBehavior.DJANGO.value,  # \"django\" | \"isolated\"\n    # Root-level \"components\" dirs, e.g. `/path/to/proj/components/`\n    dirs=[Path(settings.BASE_DIR) / \"components\"],\n    # App-level \"components\" dirs, e.g. `[app]/components/`\n    app_dirs=[\"components\"],\n    debug_highlight_components=False,\n    debug_highlight_slots=False,\n    dynamic_component_name=\"dynamic\",\n    extensions=[],\n    libraries=[],  # E.g. [\"mysite.components.forms\", ...]\n    multiline_tags=True,\n    reload_on_file_change=False,\n    static_files_allowed=[\n        \".css\",\n        \".js\", \".jsx\", \".ts\", \".tsx\",\n        # Images\n        \".apng\", \".png\", \".avif\", \".gif\", \".jpg\",\n        \".jpeg\", \".jfif\", \".pjpeg\", \".pjp\", \".svg\",\n        \".webp\", \".bmp\", \".ico\", \".cur\", \".tif\", \".tiff\",\n        # Fonts\n        \".eot\", \".ttf\", \".woff\", \".otf\", \".svg\",\n    ],\n    static_files_forbidden=[\n        # See https://marketplace.visualstudio.com/items?itemName=junstyle.vscode-django-support\n        \".html\", \".django\", \".dj\", \".tpl\",\n        # Python files\n        \".py\", \".pyc\",\n    ],\n    tag_formatter=\"django_components.component_formatter\",\n    template_cache_size=128,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.app_dirs","title":"app_dirs","text":"<pre><code>app_dirs: Optional[Sequence[str]] = None\n</code></pre> <p>See source code</p> <p>Specify the app-level directories that contain your components.</p> <p>Defaults to <code>[\"components\"]</code>. That is, for each Django app, we search <code>&lt;app&gt;/components/</code> for components.</p> <p>The paths must be relative to app, e.g.:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    app_dirs=[\"my_comps\"],\n)\n</code></pre> <p>To search for <code>&lt;app&gt;/my_comps/</code>.</p> <p>These locations are searched during autodiscovery, or when you define HTML, JS, or CSS as separate files.</p> <p>Set to empty list to disable app-level components:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    app_dirs=[],\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.autodiscover","title":"autodiscover","text":"<pre><code>autodiscover: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Toggle whether to run autodiscovery at the Django server startup.</p> <p>Defaults to <code>True</code></p> <pre><code>COMPONENTS = ComponentsSettings(\n    autodiscover=False,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.cache","title":"cache","text":"<pre><code>cache: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the Django cache to be used for storing component's JS and CSS files.</p> <p>If <code>None</code>, a <code>LocMemCache</code> is used with default settings.</p> <p>Defaults to <code>None</code>.</p> <p>Read more about caching.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    cache=\"my_cache\",\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.context_behavior","title":"context_behavior","text":"<pre><code>context_behavior: Optional[ContextBehaviorType] = None\n</code></pre> <p>See source code</p> <p>Configure whether, inside a component template, you can use variables from the outside (<code>\"django\"</code>) or not (<code>\"isolated\"</code>). This also affects what variables are available inside the <code>{% fill %}</code> tags.</p> <p>Also see Component context and scope.</p> <p>Defaults to <code>\"django\"</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    context_behavior=\"isolated\",\n)\n</code></pre> <p>NOTE: <code>context_behavior</code> and <code>slot_context_behavior</code> options were merged in v0.70.</p> <p>If you are migrating from BEFORE v0.67, set <code>context_behavior</code> to <code>\"django\"</code>. From v0.67 to v0.78 (incl) the default value was <code>\"isolated\"</code>.</p> <p>For v0.79 and later, the default is again <code>\"django\"</code>. See the rationale for change here.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_components","title":"debug_highlight_components","text":"<pre><code>debug_highlight_components: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable component highlighting. See Troubleshooting for more details.</p> <p>Defaults to <code>False</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    debug_highlight_components=True,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_slots","title":"debug_highlight_slots","text":"<pre><code>debug_highlight_slots: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable slot highlighting. See Troubleshooting for more details.</p> <p>Defaults to <code>False</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    debug_highlight_slots=True,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.dirs","title":"dirs","text":"<pre><code>dirs: Optional[Sequence[Union[str, PathLike, Tuple[str, str], Tuple[str, PathLike]]]] = None\n</code></pre> <p>See source code</p> <p>Specify the directories that contain your components.</p> <p>Defaults to <code>[Path(settings.BASE_DIR) / \"components\"]</code>. That is, the root <code>components/</code> app.</p> <p>Directories must be full paths, same as with STATICFILES_DIRS.</p> <p>These locations are searched during autodiscovery, or when you define HTML, JS, or CSS as separate files.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    dirs=[BASE_DIR / \"components\"],\n)\n</code></pre> <p>Set to empty list to disable global components directories:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    dirs=[],\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.dynamic_component_name","title":"dynamic_component_name","text":"<pre><code>dynamic_component_name: Optional[str] = None\n</code></pre> <p>See source code</p> <p>By default, the dynamic component is registered under the name <code>\"dynamic\"</code>.</p> <p>In case of a conflict, you can use this setting to change the component name used for the dynamic components.</p> <pre><code># settings.py\nCOMPONENTS = ComponentsSettings(\n    dynamic_component_name=\"my_dynamic\",\n)\n</code></pre> <p>After which you will be able to use the dynamic component with the new name:</p> <pre><code>{% component \"my_dynamic\" is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.extensions","title":"extensions","text":"<pre><code>extensions: Optional[Sequence[Union[Type[ComponentExtension], str]]] = None\n</code></pre> <p>See source code</p> <p>List of extensions to be loaded.</p> <p>The extensions can be specified as:</p> <ul> <li>Python import path, e.g. <code>\"path.to.my_extension.MyExtension\"</code>.</li> <li>Extension class, e.g. <code>my_extension.MyExtension</code>.</li> </ul> <pre><code>COMPONENTS = ComponentsSettings(\n    extensions=[\n        \"path.to.my_extension.MyExtension\",\n        StorybookExtension,\n    ],\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.forbidden_static_files","title":"forbidden_static_files","text":"<pre><code>forbidden_static_files: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>COMPONENTS.static_files_forbidden</code> instead.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.libraries","title":"libraries","text":"<pre><code>libraries: Optional[List[str]] = None\n</code></pre> <p>See source code</p> <p>Configure extra python modules that should be loaded.</p> <p>This may be useful if you are not using the autodiscovery feature, or you need to load components from non-standard locations. Thus you can have a structure of components that is independent from your apps.</p> <p>Expects a list of python module paths. Defaults to empty list.</p> <p>Example:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    libraries=[\n        \"mysite.components.forms\",\n        \"mysite.components.buttons\",\n        \"mysite.components.cards\",\n    ],\n)\n</code></pre> <p>This would be the equivalent of importing these modules from within Django's <code>AppConfig.ready()</code>:</p> <pre><code>class MyAppConfig(AppConfig):\n    def ready(self):\n        import \"mysite.components.forms\"\n        import \"mysite.components.buttons\"\n        import \"mysite.components.cards\"\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.libraries--manually-loading-libraries","title":"Manually loading libraries","text":"<p>In the rare case that you need to manually trigger the import of libraries, you can use the <code>import_libraries()</code> function:</p> <pre><code>from django_components import import_libraries\n\nimport_libraries()\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.multiline_tags","title":"multiline_tags","text":"<pre><code>multiline_tags: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable multiline support for template tags. If <code>True</code>, template tags like <code>{% component %}</code> or <code>{{ my_var }}</code> can span multiple lines.</p> <p>Defaults to <code>True</code>.</p> <p>Disable this setting if you are making custom modifications to Django's regular expression for parsing templates at <code>django.template.base.tag_re</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    multiline_tags=False,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.reload_on_file_change","title":"reload_on_file_change","text":"<pre><code>reload_on_file_change: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>This is relevant if you are using the project structure where HTML, JS, CSS and Python are in separate files and nested in a directory.</p> <p>In this case you may notice that when you are running a development server, the server sometimes does not reload when you change component files.</p> <p>Django's native live reload logic handles only Python files and HTML template files. It does NOT reload when other file types change or when template files are nested more than one level deep.</p> <p>The setting <code>reload_on_file_change</code> fixes this, reloading the dev server even when your component's HTML, JS, or CSS changes.</p> <p>If <code>True</code>, django_components configures Django to reload when files inside <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> change.</p> <p>See Reload dev server on component file changes.</p> <p>Defaults to <code>False</code>.</p> <p>Warning</p> <p>This setting should be enabled only for the dev environment!</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.reload_on_template_change","title":"reload_on_template_change","text":"<pre><code>reload_on_template_change: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>COMPONENTS.reload_on_file_change</code> instead.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.static_files_allowed","title":"static_files_allowed","text":"<pre><code>static_files_allowed: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>A list of file extensions (including the leading dot) that define which files within <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> are treated as static files.</p> <p>If a file is matched against any of the patterns, it's considered a static file. Such files are collected when running <code>collectstatic</code>, and can be accessed under the static file endpoint.</p> <p>You can also pass in compiled regexes (<code>re.Pattern</code>) for more advanced patterns.</p> <p>By default, JS, CSS, and common image and font file formats are considered static files:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    static_files_allowed=[\n        \".css\",\n        \".js\", \".jsx\", \".ts\", \".tsx\",\n        # Images\n        \".apng\", \".png\", \".avif\", \".gif\", \".jpg\",\n        \".jpeg\",  \".jfif\", \".pjpeg\", \".pjp\", \".svg\",\n        \".webp\", \".bmp\", \".ico\", \".cur\", \".tif\", \".tiff\",\n        # Fonts\n        \".eot\", \".ttf\", \".woff\", \".otf\", \".svg\",\n    ],\n)\n</code></pre> <p>Warning</p> <p>Exposing your Python files can be a security vulnerability. See Security notes.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.static_files_forbidden","title":"static_files_forbidden","text":"<pre><code>static_files_forbidden: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>A list of file extensions (including the leading dot) that define which files within <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> will NEVER be treated as static files.</p> <p>If a file is matched against any of the patterns, it will never be considered a static file, even if the file matches a pattern in <code>static_files_allowed</code>.</p> <p>Use this setting together with <code>static_files_allowed</code> for a fine control over what file types will be exposed.</p> <p>You can also pass in compiled regexes (<code>re.Pattern</code>) for more advanced patterns.</p> <p>By default, any HTML and Python are considered NOT static files:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    static_files_forbidden=[\n        \".html\", \".django\", \".dj\", \".tpl\",\n        # Python files\n        \".py\", \".pyc\",\n    ],\n)\n</code></pre> <p>Warning</p> <p>Exposing your Python files can be a security vulnerability. See Security notes.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.tag_formatter","title":"tag_formatter","text":"<pre><code>tag_formatter: Optional[Union[TagFormatterABC, str]] = None\n</code></pre> <p>See source code</p> <p>Configure what syntax is used inside Django templates to render components. See the available tag formatters.</p> <p>Defaults to <code>\"django_components.component_formatter\"</code>.</p> <p>Learn more about Customizing component tags with TagFormatter.</p> <p>Can be set either as direct reference:</p> <pre><code>from django_components import component_formatter\n\nCOMPONENTS = ComponentsSettings(\n    \"tag_formatter\": component_formatter\n)\n</code></pre> <p>Or as an import string;</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_formatter\"\n)\n</code></pre> <p>Examples:</p> <ul> <li> <p><code>\"django_components.component_formatter\"</code></p> <p>Set</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_formatter\"\n)\n</code></pre> <p>To write components like this:</p> <pre><code>{% component \"button\" href=\"...\" %}\n    Click me!\n{% endcomponent %}\n</code></pre> </li> <li> <p><code>django_components.component_shorthand_formatter</code></p> <p>Set</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_shorthand_formatter\"\n)\n</code></pre> <p>To write components like this:</p> <pre><code>{% button href=\"...\" %}\n    Click me!\n{% endbutton %}\n</code></pre> </li> </ul>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.template_cache_size","title":"template_cache_size","text":"<pre><code>template_cache_size: Optional[int] = None\n</code></pre> <p>See source code</p> <p>Configure the maximum amount of Django templates to be cached.</p> <p>Defaults to <code>128</code>.</p> <p>Each time a Django template is rendered, it is cached to a global in-memory cache (using Python's <code>lru_cache</code> decorator). This speeds up the next render of the component. As the same component is often used many times on the same page, these savings add up.</p> <p>By default the cache holds 128 component templates in memory, which should be enough for most sites. But if you have a lot of components, or if you are overriding <code>Component.get_template()</code> to render many dynamic templates, you can increase this number.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    template_cache_size=256,\n)\n</code></pre> <p>To remove the cache limit altogether and cache everything, set <code>template_cache_size</code> to <code>None</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    template_cache_size=None,\n)\n</code></pre> <p>If you want to add templates to the cache yourself, you can use <code>cached_template()</code>:</p> <pre><code>from django_components import cached_template\n\ncached_template(\"Variable: {{ variable }}\")\n\n# You can optionally specify Template class, and other Template inputs:\nclass MyTemplate(Template):\n    pass\n\ncached_template(\n    \"Variable: {{ variable }}\",\n    template_cls=MyTemplate,\n    name=...\n    origin=...\n    engine=...\n)\n</code></pre>"},{"location":"reference/signals/","title":"Signals","text":""},{"location":"reference/signals/#signals","title":"Signals","text":"<p>Below are the signals that are sent by or during the use of django-components.</p>"},{"location":"reference/signals/#template_rendered","title":"template_rendered","text":"<p>Django's <code>template_rendered</code> signal. This signal is sent when a template is rendered.</p> <p>Django-components triggers this signal when a component is rendered. If there are nested components, the signal is triggered for each component.</p> <p>Import from django as <code>django.test.signals.template_rendered</code>.</p> <pre><code>from django.test.signals import template_rendered\n\n# Setup a callback function\ndef my_callback(sender, **kwargs):\n    ...\n\ntemplate_rendered.connect(my_callback)\n\nclass MyTable(Component):\n    template = \"\"\"\n    &lt;table&gt;\n        &lt;tr&gt;\n            &lt;th&gt;Header&lt;/th&gt;\n        &lt;/tr&gt;\n        &lt;tr&gt;\n            &lt;td&gt;Cell&lt;/td&gt;\n        &lt;/tr&gt;\n    \"\"\"\n\n# This will trigger the signal\nMyTable().render()\n</code></pre>"},{"location":"reference/tag_formatters/","title":"Tag formatters","text":""},{"location":"reference/tag_formatters/#tag-formatters","title":"Tag Formatters","text":"<p>Tag formatters allow you to change the syntax for calling components from within the Django templates.</p> <p>Tag formatter are set via the tag_formatter setting.</p>"},{"location":"reference/tag_formatters/#available-tag-formatters","title":"Available tag formatters","text":"<ul> <li> <p><code>django_components.component_formatter</code> for ComponentFormatter</p> </li> <li> <p><code>django_components.component_shorthand_formatter</code> for ShorthandComponentFormatter </p> </li> </ul>"},{"location":"reference/tag_formatters/#django_components.tag_formatter.ComponentFormatter","title":"<code>ComponentFormatter</code>","text":"<p>Bases: <code>django_components.tag_formatter.TagFormatterABC</code></p> <p>See source code</p> <p>The original django_component's component tag formatter, it uses the <code>{% component %}</code> and <code>{% endcomponent %}</code> tags, and the component name is given as the first positional arg.</p> <p>Example as block: <pre><code>{% component \"mycomp\" abc=123 %}\n    {% fill \"myfill\" %}\n        ...\n    {% endfill %}\n{% endcomponent %}\n</code></pre></p> <p>Example as inlined tag: <pre><code>{% component \"mycomp\" abc=123 / %}\n</code></pre></p>"},{"location":"reference/tag_formatters/#django_components.tag_formatter.ShorthandComponentFormatter","title":"<code>ShorthandComponentFormatter</code>","text":"<p>Bases: <code>django_components.tag_formatter.TagFormatterABC</code></p> <p>See source code</p> <p>The component tag formatter that uses <code>{% &lt;name&gt; %}</code> / <code>{% end&lt;name&gt; %}</code> tags.</p> <p>This is similar to django-web-components and django-slippers syntax.</p> <p>Example as block: <pre><code>{% mycomp abc=123 %}\n    {% fill \"myfill\" %}\n        ...\n    {% endfill %}\n{% endmycomp %}\n</code></pre></p> <p>Example as inlined tag: <pre><code>{% mycomp abc=123 / %}\n</code></pre></p>"},{"location":"reference/template_tags/","title":"Template tags","text":""},{"location":"reference/template_tags/#template-tags","title":"Template tags","text":"<p>All following template tags are defined in</p> <p><code>django_components.templatetags.component_tags</code></p> <p>Import as <pre><code>{% load component_tags %}\n</code></pre></p>"},{"location":"reference/template_tags/#component_css_dependencies","title":"component_css_dependencies","text":"<pre><code>{% component_css_dependencies  %}\n</code></pre> <p>See source code</p> <p>Marks location where CSS link tags should be rendered after the whole HTML has been generated.</p> <p>Generally, this should be inserted into the <code>&lt;head&gt;</code> tag of the HTML.</p> <p>If the generated HTML does NOT contain any <code>{% component_css_dependencies %}</code> tags, CSS links are by default inserted into the <code>&lt;head&gt;</code> tag of the HTML. (See JS and CSS output locations)</p> <p>Note that there should be only one <code>{% component_css_dependencies %}</code> for the whole HTML document. If you insert this tag multiple times, ALL CSS links will be duplicately inserted into ALL these places.</p>"},{"location":"reference/template_tags/#component_js_dependencies","title":"component_js_dependencies","text":"<pre><code>{% component_js_dependencies  %}\n</code></pre> <p>See source code</p> <p>Marks location where JS link tags should be rendered after the whole HTML has been generated.</p> <p>Generally, this should be inserted at the end of the <code>&lt;body&gt;</code> tag of the HTML.</p> <p>If the generated HTML does NOT contain any <code>{% component_js_dependencies %}</code> tags, JS scripts are by default inserted at the end of the <code>&lt;body&gt;</code> tag of the HTML. (See JS and CSS output locations)</p> <p>Note that there should be only one <code>{% component_js_dependencies %}</code> for the whole HTML document. If you insert this tag multiple times, ALL JS scripts will be duplicately inserted into ALL these places.</p>"},{"location":"reference/template_tags/#component","title":"component","text":"<pre><code>{% component *args: Any, **kwargs: Any [only] %}\n{% endcomponent %}\n</code></pre> <p>See source code</p> <p>Renders one of the components that was previously registered with <code>@register()</code> decorator.</p> <p>Args:</p> <ul> <li><code>name</code> (str, required): Registered name of the component to render</li> <li>All other args and kwargs are defined based on the component itself.</li> </ul> <p>If you defined a component <code>\"my_table\"</code></p> <pre><code>from django_component import Component, register\n\n@register(\"my_table\")\nclass MyTable(Component):\n    template = \"\"\"\n      &lt;table&gt;\n        &lt;thead&gt;\n          {% for header in headers %}\n            &lt;th&gt;{{ header }}&lt;/th&gt;\n          {% endfor %}\n        &lt;/thead&gt;\n        &lt;tbody&gt;\n          {% for row in rows %}\n            &lt;tr&gt;\n              {% for cell in row %}\n                &lt;td&gt;{{ cell }}&lt;/td&gt;\n              {% endfor %}\n            &lt;/tr&gt;\n          {% endfor %}\n        &lt;tbody&gt;\n      &lt;/table&gt;\n    \"\"\"\n\n    def get_context_data(self, rows: List, headers: List):\n        return {\n            \"rows\": rows,\n            \"headers\": headers,\n        }\n</code></pre> <p>Then you can render this component by referring to <code>MyTable</code> via its registered name <code>\"my_table\"</code>:</p> <pre><code>{% component \"my_table\" rows=rows headers=headers ... / %}\n</code></pre>"},{"location":"reference/template_tags/#component-input","title":"Component input","text":"<p>Positional and keyword arguments can be literals or template variables.</p> <p>The component name must be a single- or double-quotes string and must be either:</p> <ul> <li> <p>The first positional argument after <code>component</code>:</p> <pre><code>{% component \"my_table\" rows=rows headers=headers ... / %}\n</code></pre> </li> <li> <p>Passed as kwarg <code>name</code>:</p> <pre><code>{% component rows=rows headers=headers name=\"my_table\" ... / %}\n</code></pre> </li> </ul>"},{"location":"reference/template_tags/#inserting-into-slots","title":"Inserting into slots","text":"<p>If the component defined any slots, you can pass in the content to be placed inside those slots by inserting <code>{% fill %}</code> tags, directly within the <code>{% component %}</code> tag:</p> <pre><code>{% component \"my_table\" rows=rows headers=headers ... / %}\n  {% fill \"pagination\" %}\n    &lt; 1 | 2 | 3 &gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/template_tags/#isolating-components","title":"Isolating components","text":"<p>By default, components behave similarly to Django's <code>{% include %}</code>, and the template inside the component has access to the variables defined in the outer template.</p> <p>You can selectively isolate a component, using the <code>only</code> flag, so that the inner template can access only the data that was explicitly passed to it:</p> <pre><code>{% component \"name\" positional_arg keyword_arg=value ... only %}\n</code></pre>"},{"location":"reference/template_tags/#fill","title":"fill","text":"<pre><code>{% fill name: str, *, data: Optional[str] = None, default: Optional[str] = None %}\n{% endfill %}\n</code></pre> <p>See source code</p> <p>Use this tag to insert content into component's slots.</p> <p><code>{% fill %}</code> tag may be used only within a <code>{% component %}..{% endcomponent %}</code> block. Runtime checks should prohibit other usages.</p> <p>Args:</p> <ul> <li><code>name</code> (str, required): Name of the slot to insert this content into. Use <code>\"default\"</code> for     the default slot.</li> <li><code>default</code> (str, optional): This argument allows you to access the original content of the slot     under the specified variable name. See     Accessing original content of slots</li> <li><code>data</code> (str, optional): This argument allows you to access the data passed to the slot     under the specified variable name. See Scoped slots</li> </ul> <p>Examples:</p> <p>Basic usage: <pre><code>{% component \"my_table\" %}\n  {% fill \"pagination\" %}\n    &lt; 1 | 2 | 3 &gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre></p>"},{"location":"reference/template_tags/#accessing-slots-default-content-with-the-default-kwarg","title":"Accessing slot's default content with the <code>default</code> kwarg","text":"<pre><code>{# my_table.html #}\n&lt;table&gt;\n  ...\n  {% slot \"pagination\" %}\n    &lt; 1 | 2 | 3 &gt;\n  {% endslot %}\n&lt;/table&gt;\n</code></pre> <pre><code>{% component \"my_table\" %}\n  {% fill \"pagination\" default=\"default_pag\" %}\n    &lt;div class=\"my-class\"&gt;\n      {{ default_pag }}\n    &lt;/div&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/template_tags/#accessing-slots-data-with-the-data-kwarg","title":"Accessing slot's data with the <code>data</code> kwarg","text":"<pre><code>{# my_table.html #}\n&lt;table&gt;\n  ...\n  {% slot \"pagination\" pages=pages %}\n    &lt; 1 | 2 | 3 &gt;\n  {% endslot %}\n&lt;/table&gt;\n</code></pre> <pre><code>{% component \"my_table\" %}\n  {% fill \"pagination\" data=\"slot_data\" %}\n    {% for page in slot_data.pages %}\n        &lt;a href=\"{{ page.link }}\"&gt;\n          {{ page.index }}\n        &lt;/a&gt;\n    {% endfor %}\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/template_tags/#accessing-slot-data-and-default-content-on-the-default-slot","title":"Accessing slot data and default content on the default slot","text":"<p>To access slot data and the default slot content on the default slot, use <code>{% fill %}</code> with <code>name</code> set to <code>\"default\"</code>:</p> <pre><code>{% component \"button\" %}\n  {% fill name=\"default\" data=\"slot_data\" default=\"default_slot\" %}\n    You clicked me {{ slot_data.count }} times!\n    {{ default_slot }}\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/template_tags/#html_attrs","title":"html_attrs","text":"<pre><code>{% html_attrs attrs: Optional[Dict] = None, defaults: Optional[Dict] = None, **kwargs: Any %}\n</code></pre> <p>See source code</p> <p>Generate HTML attributes (<code>key=\"value\"</code>), combining data from multiple sources, whether its template variables or static text.</p> <p>It is designed to easily merge HTML attributes passed from outside with the internal. See how to in Passing HTML attributes to components.</p> <p>Args:</p> <ul> <li><code>attrs</code> (dict, optional): Optional dictionary that holds HTML attributes. On conflict, overrides     values in the <code>default</code> dictionary.</li> <li><code>default</code> (str, optional): Optional dictionary that holds HTML attributes. On conflict, is overriden     with values in the <code>attrs</code> dictionary.</li> <li>Any extra kwargs will be appended to the corresponding keys</li> </ul> <p>The attributes in <code>attrs</code> and <code>defaults</code> are merged and resulting dict is rendered as HTML attributes (<code>key=\"value\"</code>).</p> <p>Extra kwargs (<code>key=value</code>) are concatenated to existing keys. So if we have</p> <pre><code>attrs = {\"class\": \"my-class\"}\n</code></pre> <p>Then</p> <pre><code>{% html_attrs attrs class=\"extra-class\" %}\n</code></pre> <p>will result in <code>class=\"my-class extra-class\"</code>.</p> <p>Example: <pre><code>&lt;div {% html_attrs\n    attrs\n    defaults:class=\"default-class\"\n    class=\"extra-class\"\n    data-id=\"123\"\n%}&gt;\n</code></pre></p> <p>renders</p> <pre><code>&lt;div class=\"my-class extra-class\" data-id=\"123\"&gt;\n</code></pre> <p>See more usage examples in HTML attributes.</p>"},{"location":"reference/template_tags/#provide","title":"provide","text":"<pre><code>{% provide name: str, **kwargs: Any %}\n{% endprovide %}\n</code></pre> <p>See source code</p> <p>The \"provider\" part of the provide / inject feature. Pass kwargs to this tag to define the provider's data. Any components defined within the <code>{% provide %}..{% endprovide %}</code> tags will be able to access this data with <code>Component.inject()</code>.</p> <p>This is similar to React's <code>ContextProvider</code>, or Vue's <code>provide()</code>.</p> <p>Args:</p> <ul> <li><code>name</code> (str, required): Provider name. This is the name you will then use in     <code>Component.inject()</code>.</li> <li><code>**kwargs</code>: Any extra kwargs will be passed as the provided data.</li> </ul> <p>Example:</p> <p>Provide the \"user_data\" in parent component:</p> <pre><code>@register(\"parent\")\nclass Parent(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% provide \"user_data\" user=user %}\n          {% component \"child\" / %}\n        {% endprovide %}\n      &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self, user: User):\n        return {\n            \"user\": user,\n        }\n</code></pre> <p>Since the \"child\" component is used within the <code>{% provide %} / {% endprovide %}</code> tags, we can request the \"user_data\" using <code>Component.inject(\"user_data\")</code>:</p> <pre><code>@register(\"child\")\nclass Child(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        User is: {{ user }}\n      &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self):\n        user = self.inject(\"user_data\").user\n        return {\n            \"user\": user,\n        }\n</code></pre> <p>Notice that the keys defined on the <code>{% provide %}</code> tag are then accessed as attributes when accessing them with <code>Component.inject()</code>.</p> <p>\u2705 Do this <pre><code>user = self.inject(\"user_data\").user\n</code></pre></p> <p>\u274c Don't do this <pre><code>user = self.inject(\"user_data\")[\"user\"]\n</code></pre></p>"},{"location":"reference/template_tags/#slot","title":"slot","text":"<pre><code>{% slot name: str, **kwargs: Any [default] [required] %}\n{% endslot %}\n</code></pre> <p>See source code</p> <p>Slot tag marks a place inside a component where content can be inserted from outside.</p> <p>Learn more about using slots.</p> <p>This is similar to slots as seen in Web components, Vue or React's <code>children</code>.</p> <p>Args:</p> <ul> <li><code>name</code> (str, required): Registered name of the component to render</li> <li><code>default</code>: Optional flag. If there is a default slot, you can pass the component slot content     without using the <code>{% fill %}</code> tag. See     Default slot</li> <li><code>required</code>: Optional flag. Will raise an error if a slot is required but not given.</li> <li><code>**kwargs</code>: Any extra kwargs will be passed as the slot data.</li> </ul> <p>Example:</p> <pre><code>@register(\"child\")\nclass Child(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% slot \"content\" default %}\n          This is shown if not overriden!\n        {% endslot %}\n      &lt;/div&gt;\n      &lt;aside&gt;\n        {% slot \"sidebar\" required / %}\n      &lt;/aside&gt;\n    \"\"\"\n</code></pre> <pre><code>@register(\"parent\")\nclass Parent(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% component \"child\" %}\n          {% fill \"content\" %}\n            \ud83d\uddde\ufe0f\ud83d\udcf0\n          {% endfill %}\n\n          {% fill \"sidebar\" %}\n            \ud83c\udf77\ud83e\uddc9\ud83c\udf7e\n          {% endfill %}\n        {% endcomponent %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre>"},{"location":"reference/template_tags/#passing-data-to-slots","title":"Passing data to slots","text":"<p>Any extra kwargs will be considered as slot data, and will be accessible in the <code>{% fill %}</code> tag via fill's <code>data</code> kwarg:</p> <pre><code>@register(\"child\")\nclass Child(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {# Passing data to the slot #}\n        {% slot \"content\" user=user %}\n          This is shown if not overriden!\n        {% endslot %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre> <pre><code>@register(\"parent\")\nclass Parent(Component):\n    template = \"\"\"\n      {# Parent can access the slot data #}\n      {% component \"child\" %}\n        {% fill \"content\" data=\"data\" %}\n          &lt;div class=\"wrapper-class\"&gt;\n            {{ data.user }}\n          &lt;/div&gt;\n        {% endfill %}\n      {% endcomponent %}\n    \"\"\"\n</code></pre>"},{"location":"reference/template_tags/#accessing-default-slot-content","title":"Accessing default slot content","text":"<p>The content between the <code>{% slot %}..{% endslot %}</code> tags is the default content that will be rendered if no fill is given for the slot.</p> <p>This default content can then be accessed from within the <code>{% fill %}</code> tag using the fill's <code>default</code> kwarg. This is useful if you need to wrap / prepend / append the original slot's content.</p> <pre><code>@register(\"child\")\nclass Child(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% slot \"content\" %}\n          This is default content!\n        {% endslot %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre> <pre><code>@register(\"parent\")\nclass Parent(Component):\n    template = \"\"\"\n      {# Parent can access the slot's default content #}\n      {% component \"child\" %}\n        {% fill \"content\" default=\"default\" %}\n          {{ default }}\n        {% endfill %}\n      {% endcomponent %}\n    \"\"\"\n</code></pre>"},{"location":"reference/template_vars/","title":"Template vars","text":""},{"location":"reference/template_vars/#template-variables","title":"Template variables","text":"<p>Here is a list of all variables that are automatically available from inside the component's template and in <code>on_render_before</code> / <code>on_render_after</code> hooks.</p>"},{"location":"reference/template_vars/#django_components.component.ComponentVars.is_filled","title":"is_filled  <code>instance-attribute</code>","text":"<pre><code>is_filled: Dict[str, bool]\n</code></pre> <p>See source code</p> <p>Dictonary describing which component slots are filled (<code>True</code>) or are not (<code>False</code>).</p> <p>New in version 0.70</p> <p>Use as <code>{{ component_vars.is_filled }}</code></p> <p>Example:</p> <pre><code>{# Render wrapping HTML only if the slot is defined #}\n{% if component_vars.is_filled.my_slot %}\n    &lt;div class=\"slot-wrapper\"&gt;\n        {% slot \"my_slot\" / %}\n    &lt;/div&gt;\n{% endif %}\n</code></pre> <p>This is equivalent to checking if a given key is among the slot fills:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"my_slot_filled\": \"my_slot\" in self.input.slots\n        }\n</code></pre>"},{"location":"reference/testing_api/","title":"Testing API","text":""},{"location":"reference/testing_api/#testing-api","title":"Testing API","text":""},{"location":"reference/testing_api/#django_components.testing.djc_test","title":"djc_test","text":"<pre><code>djc_test(\n    django_settings: Union[Optional[Dict], Callable, Type] = None,\n    components_settings: Optional[Dict] = None,\n    parametrize: Optional[\n        Union[\n            Tuple[Sequence[str], Sequence[Sequence[Any]]],\n            Tuple[\n                Sequence[str],\n                Sequence[Sequence[Any]],\n                Optional[Union[Iterable[Union[None, str, float, int, bool]], Callable[[Any], Optional[object]]]],\n            ],\n        ]\n    ] = None,\n    gc_collect: bool = True,\n) -&gt; Callable\n</code></pre> <p>See source code</p> <p>Decorator for testing components from django-components.</p> <p><code>@djc_test</code> manages the global state of django-components, ensuring that each test is properly isolated and that components registered in one test do not affect other tests.</p> <p>This decorator can be applied to a function, method, or a class. If applied to a class, it will search for all methods that start with <code>test_</code>, and apply the decorator to them. This is applied recursively to nested classes as well.</p> <p>Examples:</p> <p>Applying to a function: <pre><code>from django_components.testing import djc_test\n\n@djc_test\ndef test_my_component():\n    @register(\"my_component\")\n    class MyComponent(Component):\n        template = \"...\"\n    ...\n</code></pre></p> <p>Applying to a class: <pre><code>from django_components.testing import djc_test\n\n@djc_test\nclass TestMyComponent:\n    def test_something(self):\n        ...\n\n    class Nested:\n        def test_something_else(self):\n            ...\n</code></pre></p> <p>Applying to a class is the same as applying the decorator to each <code>test_</code> method individually: <pre><code>from django_components.testing import djc_test\n\nclass TestMyComponent:\n    @djc_test\n    def test_something(self):\n        ...\n\n    class Nested:\n        @djc_test\n        def test_something_else(self):\n            ...\n</code></pre></p> <p>To use <code>@djc_test</code>, Django must be set up first:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\n@djc_test\ndef test_my_component():\n    ...\n</code></pre> <p>Arguments:</p> <ul> <li> <p><code>django_settings</code>: Django settings, a dictionary passed to Django's   <code>@override_settings</code>.   The test runs within the context of these overridden settings.</p> <p>If <code>django_settings</code> contains django-components settings (<code>COMPONENTS</code> field), these are merged. Other Django settings are simply overridden.</p> </li> <li> <p><code>components_settings</code>: Instead of defining django-components settings under <code>django_settings[\"COMPONENTS\"]</code>,     you can simply set the Components settings here.</p> <p>These settings are merged with the django-components settings from <code>django_settings[\"COMPONENTS\"]</code>.</p> <p>Fields in <code>components_settings</code> override fields in <code>django_settings[\"COMPONENTS\"]</code>.</p> </li> <li> <p><code>parametrize</code>: Parametrize the test function with     <code>pytest.mark.parametrize</code>.     This requires pytest to be installed.</p> <p>The input is a tuple of:</p> <ul> <li><code>(param_names, param_values)</code> or</li> <li><code>(param_names, param_values, ids)</code></li> </ul> <p>Example:</p> <pre><code>from django_components.testing import djc_test\n\n@djc_test(\n    parametrize=(\n         [\"input\", \"expected\"],\n         [[1, \"&lt;div&gt;1&lt;/div&gt;\"], [2, \"&lt;div&gt;2&lt;/div&gt;\"]],\n         ids=[\"1\", \"2\"]\n     )\n)\ndef test_component(input, expected):\n    rendered = MyComponent(input=input).render()\n    assert rendered == expected\n</code></pre> <p>You can parametrize the Django or Components settings by setting up parameters called <code>django_settings</code> and <code>components_settings</code>. These will be merged with the respetive settings from the decorator.</p> <p>Example of parametrizing context_behavior: <pre><code>from django_components.testing import djc_test\n\n@djc_test(\n    components_settings={\n        # Settings shared by all tests\n        \"app_dirs\": [\"custom_dir\"],\n    },\n    parametrize=(\n        # Parametrized settings\n        [\"components_settings\"],\n        [\n            [{\"context_behavior\": \"django\"}],\n            [{\"context_behavior\": \"isolated\"}],\n        ],\n        [\"django\", \"isolated\"],\n    )\n)\ndef test_context_behavior(components_settings):\n    rendered = MyComponent().render()\n    ...\n</code></pre></p> </li> <li> <p><code>gc_collect</code>: By default <code>djc_test</code> runs garbage collection after each test to force the state cleanup.   Set this to <code>False</code> to skip this.</p> </li> </ul> <p>Settings resolution:</p> <p><code>@djc_test</code> accepts settings from different sources. The settings are resolved in the following order:</p> <ul> <li> <p>Django settings:</p> <ol> <li>The defaults are the Django settings that Django was set up with.</li> <li>Those are then overriden with fields in the <code>django_settings</code> kwarg.</li> <li>The parametrized <code>django_settings</code> override the fields on the <code>django_settings</code> kwarg.</li> </ol> <p>Priority: <code>django_settings</code> (parametrized) &gt; <code>django_settings</code> &gt; <code>django.conf.settings</code></p> </li> <li> <p>Components settings:</p> <ol> <li>Same as above, except that the <code>django_settings[\"COMPONENTS\"]</code> field is merged instead of overridden.</li> <li>The <code>components_settings</code> kwarg is then merged with the <code>django_settings[\"COMPONENTS\"]</code> field.</li> <li>The parametrized <code>components_settings</code> override the fields on the <code>components_settings</code> kwarg.</li> </ol> <p>Priority: <code>components_settings</code> (parametrized) &gt; <code>components_settings</code> &gt; <code>django_settings[\"COMPONENTS\"]</code> &gt; <code>django.conf.settings.COMPONENTS</code></p> </li> </ul>"},{"location":"reference/urls/","title":"URLs","text":""},{"location":"reference/urls/#urls","title":"URLs","text":"<p>Below are all the URL patterns that will be added by adding <code>django_components.urls</code>.</p> <p>See Installation on how to add these URLs to your Django project.</p> <p>Django components already prefixes all URLs with <code>components/</code>. So when you are adding the URLs to <code>urlpatterns</code>, you can use an empty string as the first argument:</p> <pre><code>from django.urls import include, path\n\nurlpatterns = [\n    ...\n    path(\"\", include(\"django_components.urls\")),\n]\n</code></pre>"},{"location":"reference/urls/#list-of-urls","title":"List of URLs","text":"<ul> <li> <p><code>components/cache/&lt;str:comp_cls_hash&gt;.&lt;str:input_hash&gt;.&lt;str:script_type&gt;</code></p> </li> <li> <p><code>components/cache/&lt;str:comp_cls_hash&gt;.&lt;str:script_type&gt;</code></p> </li> </ul>"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to Django Components","text":"<p><code>django-components</code> combines Django's templating system with the modularity seen in modern frontend frameworks like Vue or React.</p> <p>With <code>django-components</code> you can support Django projects small and large without leaving the Django ecosystem.</p>"},{"location":"#quickstart","title":"Quickstart","text":"<p>A component in django-components can be as simple as a Django template and Python code to declare the component:</p> components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n</code></pre> <p>Or a combination of Django template, Python, CSS, and Javascript:</p> components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> components/calendar/calendar.css<pre><code>.calendar {\n  width: 200px;\n  background: pink;\n}\n</code></pre> components/calendar/calendar.js<pre><code>document.querySelector(\".calendar\").onclick = () =&gt; {\n  alert(\"Clicked calendar!\");\n};\n</code></pre> components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    def get_context_data(self, date):\n        return {\"date\": date}\n</code></pre> <p>Use the component like this:</p> <pre><code>{% component \"calendar\" date=\"2024-11-06\" %}{% endcomponent %}\n</code></pre> <p>And this is what gets rendered:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n  Today's date is &lt;span&gt;2024-11-06&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>Read on to learn about all the exciting details and configuration possibilities!</p> <p>(If you instead prefer to jump right into the code, check out the example project)</p>"},{"location":"#features","title":"Features","text":""},{"location":"#modern-and-modular-ui","title":"Modern and modular UI","text":"<ul> <li>Create self-contained, reusable UI elements.</li> <li>Each component can include its own HTML, CSS, and JS, or additional third-party JS and CSS.</li> <li>HTML, CSS, and JS can be defined on the component class, or loaded from files.</li> </ul> <pre><code>from django_components import Component\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template = \"\"\"\n        &lt;div class=\"calendar\"&gt;\n            Today's date is\n            &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css = \"\"\"\n        .calendar {\n            width: 200px;\n            background: pink;\n        }\n    \"\"\"\n\n    js = \"\"\"\n        document.querySelector(\".calendar\")\n            .addEventListener(\"click\", () =&gt; {\n                alert(\"Clicked calendar!\");\n            });\n    \"\"\"\n\n    # Additional JS and CSS\n    class Media:\n        js = [\"https://cdn.jsdelivr.net/npm/htmx.org@2.1.1/dist/htmx.min.js\"]\n        css = [\"bootstrap/dist/css/bootstrap.min.css\"]\n\n    # Variables available in the template\n    def get_context_data(self, date):\n        return {\n            \"date\": date\n        }\n</code></pre>"},{"location":"#composition-with-slots","title":"Composition with slots","text":"<ul> <li>Render components inside templates with <code>{% component %}</code> tag.</li> <li>Compose them with <code>{% slot %}</code> and <code>{% fill %}</code> tags.</li> <li>Vue-like slot system, including scoped slots.</li> </ul> <pre><code>{% component \"Layout\"\n    bookmarks=bookmarks\n    breadcrumbs=breadcrumbs\n%}\n    {% fill \"header\" %}\n        &lt;div class=\"flex justify-between gap-x-12\"&gt;\n            &lt;div class=\"prose\"&gt;\n                &lt;h3&gt;{{ project.name }}&lt;/h3&gt;\n            &lt;/div&gt;\n            &lt;div class=\"font-semibold text-gray-500\"&gt;\n                {{ project.start_date }} - {{ project.end_date }}\n            &lt;/div&gt;\n        &lt;/div&gt;\n    {% endfill %}\n\n    {# Access data passed to `{% slot %}` with `data` #}\n    {% fill \"tabs\" data=\"tabs_data\" %}\n        {% component \"TabItem\" header=\"Project Info\" %}\n            {% component \"ProjectInfo\"\n                project=project\n                project_tags=project_tags\n                attrs:class=\"py-5\"\n                attrs:width=tabs_data.width\n            / %}\n        {% endcomponent %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"#extended-template-tags","title":"Extended template tags","text":"<p><code>django-components</code> extends Django's template tags syntax with:</p> <ul> <li>Literal lists and dictionaries in template tags</li> <li>Self-closing tags <code>{% mytag / %}</code></li> <li>Multi-line template tags</li> <li>Spread operator <code>...</code> to dynamically pass args or kwargs into the template tag</li> <li>Nested template tags like <code>\"{{ first_name }} {{ last_name }}\"</code></li> <li>Flat definition of dictionary keys <code>attr:key=val</code></li> </ul> <pre><code>{% component \"table\"\n    ...default_attrs\n    title=\"Friend list for {{ user.name }}\"\n    headers=[\"Name\", \"Age\", \"Email\"]\n    data=[\n        {\n            \"name\": \"John\"|upper,\n            \"age\": 30|add:1,\n            \"email\": \"john@example.com\",\n            \"hobbies\": [\"reading\"],\n        },\n        {\n            \"name\": \"Jane\"|upper,\n            \"age\": 25|add:1,\n            \"email\": \"jane@example.com\",\n            \"hobbies\": [\"reading\", \"coding\"],\n        },\n    ],\n    attrs:class=\"py-4 ma-2 border-2 border-gray-300 rounded-md\"\n/ %}\n</code></pre>"},{"location":"#html-fragment-support","title":"HTML fragment support","text":"<p><code>django-components</code> makes intergration with HTMX, AlpineJS or jQuery easy by allowing components to be rendered as HTML fragments:</p> <ul> <li> <p>Components's JS and CSS is loaded automatically when the fragment is inserted into the DOM.</p> </li> <li> <p>Expose components as views with <code>get</code>, <code>post</code>, <code>put</code>, <code>patch</code>, <code>delete</code> methods</p> </li> </ul> <pre><code># components/calendar/calendar.py\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n\n    def get(self, request, *args, **kwargs):\n        page = request.GET.get(\"page\", 1)\n        return self.render_to_response(\n            kwargs={\n                \"page\": page,\n            }\n        )\n\n    def get_context_data(self, page):\n        return {\n            \"page\": page,\n        }\n\n# urls.py\npath(\"calendar/\", Calendar.as_view()),\n</code></pre>"},{"location":"#type-hints","title":"Type hints","text":"<p>Opt-in to type hints by defining types for component's args, kwargs, slots, and more:</p> <pre><code>from typing import NotRequired, Tuple, TypedDict, SlotContent, SlotFunc\n\nButtonArgs = Tuple[int, str]\n\nclass ButtonKwargs(TypedDict):\n    variable: str\n    another: int\n    maybe_var: NotRequired[int] # May be omitted\n\nclass ButtonData(TypedDict):\n    variable: str\n\nclass ButtonSlots(TypedDict):\n    my_slot: NotRequired[SlotFunc]\n    another_slot: SlotContent\n\nButtonType = Component[ButtonArgs, ButtonKwargs, ButtonSlots, ButtonData, JsData, CssData]\n\nclass Button(ButtonType):\n    def get_context_data(self, *args, **kwargs):\n        self.input.args[0]  # int\n        self.input.kwargs[\"variable\"]  # str\n        self.input.slots[\"my_slot\"]  # SlotFunc[MySlotData]\n\n        return {}  # Error: Key \"variable\" is missing\n</code></pre> <p>When you then call <code>Button.render()</code> or <code>Button.render_to_response()</code>, you will get type hints:</p> <pre><code>Button.render(\n    # Error: First arg must be `int`, got `float`\n    args=(1.25, \"abc\"),\n    # Error: Key \"another\" is missing\n    kwargs={\n        \"variable\": \"text\",\n    },\n)\n</code></pre>"},{"location":"#extensions","title":"Extensions","text":"<p>Django-components functionality can be extended with \"extensions\". Extensions allow for powerful customization and integrations. They can:</p> <ul> <li>Tap into lifecycle events, such as when a component is created, deleted, or registered.</li> <li>Add new attributes and methods to the components under an extension-specific nested class.</li> </ul> <p>Some of the planned extensions include:</p> <ul> <li>Caching</li> <li>AlpineJS integration</li> <li>Storybook integration</li> <li>Pydantic validation</li> <li>Component-level benchmarking with asv</li> </ul>"},{"location":"#simple-testing","title":"Simple testing","text":"<ul> <li>Write tests for components with <code>@djc_test</code> decorator.</li> <li>The decorator manages global state, ensuring that tests don't leak.</li> <li>If using <code>pytest</code>, the decorator allows you to parametrize Django or Components settings.</li> <li>The decorator also serves as a stand-in for Django's <code>@override_settings</code>.</li> </ul> <pre><code>from djc_test import djc_test\n\nfrom components.my_component import MyTable\n\n@djc_test\ndef test_my_table():\n    rendered = MyTable.render(\n        kwargs={\n            \"title\": \"My table\",\n        },\n    )\n    assert rendered == \"&lt;table&gt;My table&lt;/table&gt;\"\n</code></pre>"},{"location":"#handle-large-projects-with-ease","title":"Handle large projects with ease","text":"<ul> <li>Components can be infinitely nested.</li> <li>(Soon) Optimize performance with component-level caching</li> </ul>"},{"location":"#debugging-features","title":"Debugging features","text":"<ul> <li>Visual component inspection: Highlight components and slots directly in your browser.</li> <li>Detailed tracing logs to supply AI-agents with context: The logs include component and slot names and IDs, and their position in the tree.</li> </ul>"},{"location":"#sharing-components","title":"Sharing components","text":"<ul> <li>Install and use third-party components from PyPI</li> <li>Or publish your own \"component registry\"</li> <li> <p>Highly customizable - Choose how the components are called in the template (and more):</p> <pre><code>{% component \"calendar\" date=\"2024-11-06\" %}\n{% endcomponent %}\n\n{% calendar date=\"2024-11-06\" %}\n{% endcalendar %}\n</code></pre> </li> </ul>"},{"location":"#other-features","title":"Other features","text":"<ul> <li>Vue-like provide / inject system</li> <li>Format HTML attributes with <code>{% html_attrs %}</code></li> </ul>"},{"location":"#performance","title":"Performance","text":"<p>Our aim is to be at least as fast as Django templates.</p> <p>As of <code>0.130</code>, <code>django-components</code> is ~4x slower than Django templates.</p> Render time django 68.9\u00b10.6ms django-components 259\u00b14ms <p>See the full performance breakdown for more information.</p>"},{"location":"#release-notes","title":"Release notes","text":"<p>Read the Release Notes to see the latest features and fixes.</p>"},{"location":"#community-examples","title":"Community examples","text":"<p>One of our goals with <code>django-components</code> is to make it easy to share components between projects. Head over to the Community examples to see some examples.</p>"},{"location":"#contributing-and-development","title":"Contributing and development","text":"<p>Get involved or sponsor this project - See here</p> <p>Running django-components locally for development - See here</p>"},{"location":"migrating_from_safer_staticfiles/","title":"Migrating from safer_staticfiles","text":"<p>This guide is for you if you're upgrating django_components to v0.100 or later from older versions.</p> <p>In version 0.100, we changed how components' static JS and CSS files are handled. See more in the \"Static files\" section.</p> <p>Migration steps:</p> <ol> <li>Remove <code>django_components.safer_staticfiles</code> from <code>INSTALLED_APPS</code> in your <code>settings.py</code>,    and replace it with <code>django.contrib.staticfiles</code>.</li> </ol> <p>Before:</p> <pre><code>INSTALLED_APPS = [\n   \"django.contrib.admin\",\n   ...\n   # \"django.contrib.staticfiles\",  # &lt;-- ADD\n   \"django_components\",\n   \"django_components.safer_staticfiles\",  # &lt;-- REMOVE\n]\n</code></pre> <p>After:</p> <pre><code>INSTALLED_APPS = [\n   \"django.contrib.admin\",\n   ...\n   \"django.contrib.staticfiles\",\n   \"django_components\",\n]\n</code></pre> <ol> <li>Add <code>STATICFILES_FINDERS</code> to <code>settings.py</code>, and add <code>django_components.finders.ComponentsFileSystemFinder</code>:</li> </ol> <pre><code>STATICFILES_FINDERS = [\n   # Default finders\n   \"django.contrib.staticfiles.finders.FileSystemFinder\",\n   \"django.contrib.staticfiles.finders.AppDirectoriesFinder\",\n   # Django components\n   \"django_components.finders.ComponentsFileSystemFinder\",  # &lt;-- ADDED\n]\n</code></pre> <ol> <li>Add <code>COMPONENTS.dirs</code> to <code>settings.py</code>.</li> </ol> <p>If you previously defined <code>STATICFILES_DIRS</code>, move    only those directories from <code>STATICFILES_DIRS</code> that point to components directories, and keep the rest.</p> <p>E.g. if you have <code>STATICFILES_DIRS</code> like this:</p> <pre><code>STATICFILES_DIRS = [\n   BASE_DIR / \"components\",  # &lt;-- MOVE\n   BASE_DIR / \"myapp\" / \"components\",  # &lt;-- MOVE\n   BASE_DIR / \"assets\",\n]\n</code></pre> <p>Then first two entries point to components dirs, whereas <code>/assets</code> points to non-component static files.    In this case move only the first two paths:</p> <pre><code>COMPONENTS = {\n   \"dirs\": [\n      BASE_DIR / \"components\",  # &lt;-- MOVED\n      BASE_DIR / \"myapp\" / \"components\",  # &lt;-- MOVED\n   ],\n}\n\nSTATICFILES_DIRS = [\n   BASE_DIR / \"assets\",\n]\n</code></pre> <p>Moreover, if you defined app-level component directories in <code>STATICFILES_DIRS</code> before,    you can now define as a RELATIVE path in <code>app_dirs</code>:</p> <pre><code>COMPONENTS = {\n   \"dirs\": [\n      # Search top-level \"/components/\" dir\n      BASE_DIR / \"components\",\n   ],\n   \"app_dirs\": [\n      # Search \"/[app]/components/\" dirs\n      \"components\",\n   ],\n}\n\nSTATICFILES_DIRS = [\n   BASE_DIR / \"assets\",\n]\n</code></pre>"},{"location":"release_notes/","title":"Release notes","text":""},{"location":"release_notes/#v0132","title":"v0.132","text":""},{"location":"release_notes/#feat","title":"Feat","text":"<ul> <li> <p>Allow to use glob patterns as paths for additional JS / CSS in   <code>Component.Media.js</code> and <code>Component.Media.css</code></p> <pre><code>class MyComponent(Component):\n    class Media:\n        js = [\"*.js\"]\n        css = [\"*.css\"]\n</code></pre> </li> </ul>"},{"location":"release_notes/#v0131","title":"v0.131","text":""},{"location":"release_notes/#feat_1","title":"Feat","text":"<ul> <li> <p>Support for extensions (plugins) for django-components!</p> <ul> <li>Hook into lifecycle events of django-components</li> <li>Pre-/post-process component inputs, outputs, and templates</li> <li>Add extra methods or attributes to Components</li> <li>Add custom extension-specific CLI commands</li> <li>Add custom extension-specific URL routes</li> </ul> <p>Read more on Extensions.</p> </li> <li> <p>New CLI commands:</p> <ul> <li><code>components list</code> - List all components</li> <li><code>components create &lt;name&gt;</code> - Create a new component (supersedes <code>startcomponent</code>)</li> <li><code>components upgrade</code> - Upgrade a component (supersedes <code>upgradecomponent</code>)</li> <li><code>components ext list</code> - List all extensions</li> <li><code>components ext run &lt;extension&gt; &lt;command&gt;</code> - Run a command added by an extension</li> </ul> </li> <li> <p><code>@djc_test</code> decorator for writing tests that involve Components.</p> <ul> <li>The decorator manages global state, ensuring that tests don't leak.</li> <li>If using <code>pytest</code>, the decorator allows you to parametrize Django or Components settings.</li> <li>The decorator also serves as a stand-in for Django's <code>@override_settings</code>.</li> </ul> <p>See the API reference for <code>@djc_test</code> for more details.</p> </li> <li> <p><code>ComponentRegistry</code> now has a <code>has()</code> method to check if a component is registered    without raising an error.</p> </li> <li> <p>Get all created <code>Component</code> classes with <code>all_components()</code>.</p> </li> <li> <p>Get all created <code>ComponentRegistry</code> instances with <code>all_registries()</code>.</p> </li> </ul>"},{"location":"release_notes/#refactor","title":"Refactor","text":"<ul> <li> <p>The <code>startcomponent</code> and <code>upgradecomponent</code> commands are deprecated, and will be removed in v1.</p> <p>Instead, use <code>components create &lt;name&gt;</code> and <code>components upgrade</code>.</p> </li> </ul>"},{"location":"release_notes/#internal","title":"Internal","text":"<ul> <li>Settings are now loaded only once, and thus are considered immutable once loaded. Previously,   django-components would load settings from <code>settings.COMPONENTS</code> on each access. The new behavior   aligns with Django's settings.</li> </ul>"},{"location":"release_notes/#v0130","title":"v0.130","text":""},{"location":"release_notes/#feat_2","title":"Feat","text":"<ul> <li> <p>Access the HttpRequest object under <code>Component.request</code>.</p> <p>To pass the request object to a component, either: - Render a template or component with <code>RequestContext</code>, - Or set the <code>request</code> kwarg to <code>Component.render()</code> or <code>Component.render_to_response()</code>.</p> <p>Read more on HttpRequest.</p> </li> <li> <p>Access the context processors data under <code>Component.context_processors_data</code>.</p> <p>Context processors data is available only when the component has access to the <code>request</code> object, either by: - Passing the request to <code>Component.render()</code> or <code>Component.render_to_response()</code>, - Or by rendering a template or component with <code>RequestContext</code>, - Or being nested in another component that has access to the request object.</p> <p>The data from context processors is automatically available within the component's template.</p> <p>Read more on HttpRequest.</p> </li> </ul>"},{"location":"release_notes/#v0129","title":"v0.129","text":""},{"location":"release_notes/#fix","title":"Fix","text":"<ul> <li>Fix thread unsafe media resolve validation by moving it to ComponentMedia <code>__post_init</code> (#977</li> <li>Fix bug: Relative path in extends and include does not work when using template_file (#976</li> <li>Fix error when template cache setting (<code>template_cache_size</code>) is set to 0 (#974</li> </ul>"},{"location":"release_notes/#v0128","title":"v0.128","text":""},{"location":"release_notes/#feat_3","title":"Feat","text":"<ul> <li> <p>Configurable cache - Set <code>COMPONENTS.cache</code> to change where and how django-components caches JS and CSS files. (#946)</p> <p>Read more on Caching.</p> </li> <li> <p>Highlight coponents and slots in the UI - We've added two boolean settings <code>COMPONENTS.debug_highlight_components</code> and <code>COMPONENTS.debug_highlight_slots</code>, which can be independently set to <code>True</code>. First will wrap components in a blue border, the second will wrap slots in a red border. (#942)</p> <p>Read more on Troubleshooting.</p> </li> </ul>"},{"location":"release_notes/#refactor_1","title":"Refactor","text":"<ul> <li>Removed use of eval for node validation (#944)</li> </ul>"},{"location":"release_notes/#perf","title":"Perf","text":"<ul> <li> <p>Components can now be infinitely nested. (#936)</p> </li> <li> <p>Component input validation is now 6-7x faster on CPython and PyPy. This previously made up 10-30% of the total render time. (#945)</p> </li> </ul>"},{"location":"release_notes/#v0127","title":"v0.127","text":""},{"location":"release_notes/#fix_1","title":"Fix","text":"<ul> <li>Fix component rendering when using <code>{% cache %}</code> with remote cache and multiple web servers (#930)</li> </ul>"},{"location":"release_notes/#v0126","title":"v0.126","text":""},{"location":"release_notes/#refactor_2","title":"Refactor","text":"<ul> <li>Replaced BeautifulSoup4 with a custom HTML parser.</li> <li>The heuristic for inserting JS and CSS dependenies into the default place has changed.<ul> <li>JS is still inserted at the end of the <code>&lt;body&gt;</code>, and CSS at the end of <code>&lt;head&gt;</code>.</li> <li>However, we find end of <code>&lt;body&gt;</code> by searching for last occurrence of <code>&lt;/body&gt;</code></li> <li>And for the end of <code>&lt;head&gt;</code> we search for the first occurrence of <code>&lt;/head&gt;</code></li> </ul> </li> </ul>"},{"location":"release_notes/#v0125","title":"v0.125","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - We migrated from <code>EmilStenstrom/django-components</code> to <code>django-components/django-components</code>.</p> <p>Repo name and documentation URL changed. Package name remains the same.</p> <p>If you see any broken links or other issues, please report them in #922.</p>"},{"location":"release_notes/#feat_4","title":"Feat","text":"<ul> <li><code>@template_tag</code> and <code>BaseNode</code> - A decorator and a class that allow you to define   custom template tags that will behave similarly to django-components' own template tags.</li> </ul> <p>Read more on Template tags.</p> <p>Template tags defined with <code>@template_tag</code> and <code>BaseNode</code> will have the following features:</p> <ul> <li> <p>Accepting args, kwargs, and flags.</p> </li> <li> <p>Allowing literal lists and dicts as inputs as:</p> <p><code>key=[1, 2, 3]</code> or <code>key={\"a\": 1, \"b\": 2}</code>   - Using template tags tag inputs as:</p> <p><code>{% my_tag key=\"{% lorem 3 w %}\" / %}</code>   - Supporting the flat dictionary definition:</p> <p><code>attr:key=value</code>   - Spreading args and kwargs with <code>...</code>:</p> <p><code>{% my_tag ...args ...kwargs / %}</code>   - Being able to call the template tag as:</p> <p><code>{% my_tag %} ... {% endmy_tag %}</code> or <code>{% my_tag / %}</code></p> </li> </ul>"},{"location":"release_notes/#refactor_3","title":"Refactor","text":"<ul> <li> <p>Refactored template tag input validation. When you now call template tags like   <code>{% slot %}</code>, <code>{% fill %}</code>, <code>{% html_attrs %}</code>, and others, their inputs are now   validated the same way as Python function inputs are.</p> <p>So, for example</p> <pre><code>{% slot \"my_slot\" name=\"content\" / %}\n</code></pre> <p>will raise an error, because the positional argument <code>name</code> is given twice.</p> <p>NOTE: Special kwargs whose keys are not valid Python variable names are not affected by this change. So when you define:</p> <pre><code>{% component data-id=123 / %}\n</code></pre> <p>The <code>data-id</code> will still be accepted as a valid kwarg, assuming that your <code>get_context_data()</code> accepts <code>**kwargs</code>:</p> <pre><code>def get_context_data(self, **kwargs):\n    return {\n        \"data_id\": kwargs[\"data-id\"],\n    }\n</code></pre> </li> </ul>"},{"location":"release_notes/#v0124","title":"v0.124","text":""},{"location":"release_notes/#feat_5","title":"Feat","text":"<ul> <li> <p>Instead of inlining the JS and CSS under <code>Component.js</code> and <code>Component.css</code>, you can move     them to their own files, and link the JS/CSS files with <code>Component.js_file</code>  and <code>Component.css_file</code>.</p> <p>Even when you specify the JS/CSS with <code>Component.js_file</code> or <code>Component.css_file</code>, then you can still access the content under <code>Component.js</code> or <code>Component.css</code> - behind the scenes, the content of the JS/CSS files will be set to <code>Component.js</code> / <code>Component.css</code> upon first access.</p> <p>The same applies to <code>Component.template_file</code>, which will populate <code>Component.template</code> upon first access.</p> <p>With this change, the role of <code>Component.js/css</code> and the JS/CSS in <code>Component.Media</code> has changed:</p> <ul> <li>The JS/CSS defined in <code>Component.js/css</code> or <code>Component.js/css_file</code> is the \"main\" JS/CSS</li> <li>The JS/CSS defined in <code>Component.Media.js/css</code> are secondary or additional</li> </ul> <p>See the updated \"Getting Started\" tutorial</p> </li> </ul>"},{"location":"release_notes/#refactor_4","title":"Refactor","text":"<ul> <li> <p>The canonical way to define a template file was changed from <code>template_name</code> to <code>template_file</code>, to align with the rest of the API.</p> <p><code>template_name</code> remains for backwards compatibility. When you get / set <code>template_name</code>, internally this is proxied to <code>template_file</code>.</p> </li> <li> <p>The undocumented <code>Component.component_id</code> was removed. Instead, use <code>Component.id</code>. Changes:</p> <ul> <li>While <code>component_id</code> was unique every time you instantiated <code>Component</code>, the new <code>id</code> is unique every time you render the component (e.g. with <code>Component.render()</code>)</li> <li>The new <code>id</code> is available only during render, so e.g. from within <code>get_context_data()</code></li> </ul> </li> <li> <p>Component's HTML / CSS / JS are now resolved and loaded lazily. That is, if you specify <code>template_name</code>/<code>template_file</code>,   <code>js_file</code>, <code>css_file</code>, or <code>Media.js/css</code>, the file paths will be resolved only once you:</p> <ol> <li>Try to access component's HTML / CSS / JS, or</li> <li>Render the component.</li> </ol> <p>Read more on Accessing component's HTML / JS / CSS.</p> </li> <li> <p>Component inheritance:</p> <ul> <li>When you subclass a component, the JS and CSS defined on parent's <code>Media</code> class is now inherited by the child component.</li> <li>You can disable or customize Media inheritance by setting <code>extend</code> attribute on the <code>Component.Media</code> nested class. This work similarly to Django's <code>Media.extend</code>.</li> <li>When child component defines either <code>template</code> or <code>template_file</code>, both of parent's <code>template</code> and <code>template_file</code> are ignored. The same applies to <code>js_file</code> and <code>css_file</code>.</li> </ul> </li> <li> <p>Autodiscovery now ignores files and directories that start with an underscore (<code>_</code>), except <code>__init__.py</code></p> </li> <li> <p>The Signals emitted by or during the use of django-components are now documented, together the <code>template_rendered</code> signal.</p> </li> </ul>"},{"location":"release_notes/#v0123","title":"v0.123","text":""},{"location":"release_notes/#fix_2","title":"Fix","text":"<ul> <li>Fix edge cases around rendering components whose templates used the <code>{% extends %}</code> template tag (#859)</li> </ul>"},{"location":"release_notes/#v0122","title":"v0.122","text":""},{"location":"release_notes/#feat_6","title":"Feat","text":"<ul> <li>Add support for HTML fragments. HTML fragments can be rendered by passing <code>type=\"fragment\"</code> to <code>Component.render()</code> or <code>Component.render_to_response()</code>. Read more on how to use HTML fragments with HTMX, AlpineJS, or vanillaJS.</li> </ul>"},{"location":"release_notes/#v0121","title":"v0.121","text":""},{"location":"release_notes/#fix_3","title":"Fix","text":"<ul> <li>Fix the use of Django template filters (<code>|lower:\"etc\"</code>) with component inputs #855.</li> </ul>"},{"location":"release_notes/#v0120","title":"v0.120","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.121 to fix bugs introduced in v0.119.</p>"},{"location":"release_notes/#fix_4","title":"Fix","text":"<ul> <li>Fix the use of translation strings <code>_(\"bla\")</code> as inputs to components #849.</li> </ul>"},{"location":"release_notes/#v0119","title":"v0.119","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - This release introduced bugs #849, #855. Please update to v0.121.</p>"},{"location":"release_notes/#fix_5","title":"Fix","text":"<ul> <li>Fix compatibility with custom subclasses of Django's <code>Template</code> that need to access   <code>origin</code> or other initialization arguments. (https://github.com/django-components/django-components/pull/828)</li> </ul>"},{"location":"release_notes/#refactor_5","title":"Refactor","text":"<ul> <li>Compatibility with <code>django-debug-toolbar-template-profiler</code>:</li> <li> <p>Monkeypatching of Django's <code>Template</code> now happens at <code>AppConfig.ready()</code> (https://github.com/django-components/django-components/pull/825)</p> </li> <li> <p>Internal parsing of template tags tag was updated. No API change. (https://github.com/django-components/django-components/pull/827)</p> </li> </ul>"},{"location":"release_notes/#v0118","title":"v0.118","text":""},{"location":"release_notes/#feat_7","title":"Feat","text":"<ul> <li>Add support for <code>context_processors</code> and <code>RenderContext</code> inside component templates</li> </ul> <p><code>Component.render()</code> and <code>Component.render_to_response()</code> now accept an extra kwarg <code>request</code>.</p> <pre><code>```py\ndef my_view(request)\n    return MyTable.render_to_response(\n        request=request\n    )\n```\n</code></pre> <ul> <li> <p>When you pass in <code>request</code>, the component will use <code>RenderContext</code> instead of <code>Context</code>.     Thus the context processors will be applied to the context.</p> </li> <li> <p>NOTE: When you pass in both <code>request</code> and <code>context</code> to <code>Component.render()</code>, and <code>context</code> is already an instance of <code>Context</code>, the <code>request</code> kwarg will be ignored.</p> </li> </ul>"},{"location":"release_notes/#v0117","title":"v0.117","text":""},{"location":"release_notes/#fix_6","title":"Fix","text":"<ul> <li>The HTML parser no longer erronously inserts <code>&lt;html&gt;&lt;head&gt;&lt;body&gt;</code> on some occasions, and   no longer tries to close unclosed HTML tags.</li> </ul>"},{"location":"release_notes/#refactor_6","title":"Refactor","text":"<ul> <li>Replaced Selectolax with BeautifulSoup4 as project dependencies.</li> </ul>"},{"location":"release_notes/#v0116","title":"v0.116","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_7","title":"Fix","text":"<ul> <li>Fix the order of execution of JS scripts:</li> <li>Scripts in <code>Component.Media.js</code> are executed in the order they are defined</li> <li> <p>Scripts in <code>Component.js</code> are executed AFTER <code>Media.js</code> scripts</p> </li> <li> <p>Fix compatibility with AlpineJS</p> </li> <li>Scripts in <code>Component.Media.js</code> are now again inserted as <code>&lt;script&gt;</code> tags</li> <li>By default, <code>Component.Media.js</code> are inserted as synchronous <code>&lt;script&gt;</code> tags,     so the AlpineJS components registered in the <code>Media.js</code> scripts will now again     run BEFORE the core AlpineJS script.</li> </ul> <p>AlpineJS can be configured like so:</p> <p>Option 1 - AlpineJS loaded in <code>&lt;head&gt;</code> with <code>defer</code> attribute:   <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    {% component_css_dependencies %}\n    &lt;script defer src=\"https://unpkg.com/alpinejs\"&gt;&lt;/script&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component 'my_alpine_component' / %}\n    {% component_js_dependencies %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre></p> <p>Option 2 - AlpineJS loaded in <code>&lt;body&gt;</code> AFTER <code>{% component_js_depenencies %}</code>:   <pre><code>&lt;html&gt;\n    &lt;head&gt;\n        {% component_css_dependencies %}\n    &lt;/head&gt;\n    &lt;body&gt;\n        {% component 'my_alpine_component' / %}\n        {% component_js_dependencies %}\n\n        &lt;script src=\"https://unpkg.com/alpinejs\"&gt;&lt;/script&gt;\n    &lt;/body&gt;\n&lt;/html&gt;\n</code></pre></p>"},{"location":"release_notes/#v0115","title":"v0.115","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_8","title":"Fix","text":"<ul> <li>Fix integration with ManifestStaticFilesStorage on Windows by resolving component filepaths   (like <code>Component.template_name</code>) to POSIX paths.</li> </ul>"},{"location":"release_notes/#v0114","title":"v0.114","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_9","title":"Fix","text":"<ul> <li>Prevent rendering Slot tags during fill discovery stage to fix a case when a component inside a slot   fill tried to access provided data too early.</li> </ul>"},{"location":"release_notes/#v0113","title":"v0.113","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_10","title":"Fix","text":"<ul> <li>Ensure consistent order of scripts in <code>Component.Media.js</code></li> </ul>"},{"location":"release_notes/#v0112","title":"v0.112","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_11","title":"Fix","text":"<ul> <li>Allow components to accept default fill even if no default slot was encountered during rendering</li> </ul>"},{"location":"release_notes/#v0111","title":"v0.111","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#fix_12","title":"Fix","text":"<ul> <li>Prevent rendering Component tags during fill discovery stage to fix a case when a component inside the default slot   tried to access provided data too early.</li> </ul>"},{"location":"release_notes/#v0110","title":"\ud83d\udea8\ud83d\udce2 v0.110","text":"<p>\u26a0\ufe0f Attention \u26a0\ufe0f - Please update to v0.117 to fix known bugs. See #791 and #789 and #818.</p>"},{"location":"release_notes/#general","title":"General","text":""},{"location":"release_notes/#breaking-changes","title":"\ud83d\udea8\ud83d\udce2 BREAKING CHANGES","text":"<ul> <li> <p>Installation changes:</p> <ul> <li>If your components include JS or CSS, you now must use the middleware and add django-components' URLs to your <code>urlpatterns</code> (See \"Adding support for JS and CSS\")</li> </ul> </li> <li> <p>Component typing signature changed from</p> <pre><code>Component[Args, Kwargs, Data, Slots]\n</code></pre> <p>to</p> <pre><code>Component[Args, Kwargs, Slots, Data, JsData, CssData]\n</code></pre> </li> <li> <p>If you rendered a component A with <code>Component.render()</code> and then inserted that into another component B, now you must pass <code>render_dependencies=False</code> to component A:</p> <pre><code>prerendered_a = CompA.render(\n    args=[...],\n    kwargs={...},\n    render_dependencies=False,\n)\n\nhtml = CompB.render(\n    kwargs={\n        content=prerendered_a,\n    },\n)\n</code></pre> </li> </ul>"},{"location":"release_notes/#feat_8","title":"Feat","text":"<ul> <li>Intellisense and mypy validation for settings:</li> </ul> <p>Instead of defining the <code>COMPONENTS</code> settings as a plain dict, you can use <code>ComponentsSettings</code>:</p> <pre><code># settings.py\nfrom django_components import ComponentsSettings\n\nCOMPONENTS = ComponentsSettings(\n    autodiscover=True,\n    ...\n)\n</code></pre> <ul> <li>Use <code>get_component_dirs()</code> and <code>get_component_files()</code> to get the same list of dirs / files that would be imported by <code>autodiscover()</code>, but without actually importing them.</li> </ul>"},{"location":"release_notes/#refactor_7","title":"Refactor","text":"<ul> <li> <p>For advanced use cases, use can omit the middleware and instead manage component JS and CSS dependencies yourself with <code>render_dependencies</code></p> </li> <li> <p>The <code>ComponentRegistry</code> settings <code>RegistrySettings</code>   were lowercased to align with the global settings:</p> </li> <li><code>RegistrySettings.CONTEXT_BEHAVIOR</code> -&gt; <code>RegistrySettings.context_behavior</code></li> <li><code>RegistrySettings.TAG_FORMATTER</code> -&gt; <code>RegistrySettings.tag_formatter</code></li> </ul> <p>The old uppercase settings <code>CONTEXT_BEHAVIOR</code> and <code>TAG_FORMATTER</code> are deprecated and will be removed in v1.</p> <ul> <li> <p>The setting <code>reload_on_template_change</code> was renamed to   <code>reload_on_file_change</code>.   And now it properly triggers server reload when any file in the component dirs change. The old name <code>reload_on_template_change</code>   is deprecated and will be removed in v1.</p> </li> <li> <p>The setting <code>forbidden_static_files</code> was renamed to   <code>static_files_forbidden</code>   to align with <code>static_files_allowed</code>   The old name <code>forbidden_static_files</code> is deprecated and will be removed in v1.</p> </li> </ul>"},{"location":"release_notes/#tags","title":"Tags","text":""},{"location":"release_notes/#breaking-changes_1","title":"\ud83d\udea8\ud83d\udce2 BREAKING CHANGES","text":"<ul> <li> <p><code>{% component_dependencies %}</code> tag was removed. Instead, use <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code></p> <ul> <li> <p>The combined tag was removed to encourage the best practice of putting JS scripts at the end of <code>&lt;body&gt;</code>, and CSS styles inside <code>&lt;head&gt;</code>.</p> <p>On the other hand, co-locating JS script and CSS styles can lead to a flash of unstyled content, as either JS scripts will block the rendering, or CSS will load too late.</p> </li> </ul> </li> <li> <p>The undocumented keyword arg <code>preload</code> of <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code> tags was removed.   This will be replaced with HTML fragment support.</p> </li> </ul>"},{"location":"release_notes/#fix_13","title":"Fix","text":"<ul> <li>Allow using forward slash (<code>/</code>) when defining custom TagFormatter,   e.g. <code>{% MyComp %}..{% /MyComp %}</code>.</li> </ul>"},{"location":"release_notes/#refactor_8","title":"Refactor","text":"<ul> <li><code>{% component_dependencies %}</code> tags are now OPTIONAL - If your components use JS and CSS, but you don't use <code>{% component_dependencies %}</code> tags, the JS and CSS will now be, by default, inserted at the end of <code>&lt;body&gt;</code> and at the end of <code>&lt;head&gt;</code> respectively.</li> </ul>"},{"location":"release_notes/#slots","title":"Slots","text":""},{"location":"release_notes/#feat_9","title":"Feat","text":"<ul> <li>Fills can now be defined within loops (<code>{% for %}</code>) or other tags (like <code>{% with %}</code>),   or even other templates using <code>{% include %}</code>.</li> </ul> <p>Following is now possible</p> <pre><code>{% component \"table\" %}\n  {% for slot_name in slots %}\n    {% fill name=slot_name %}\n    {% endfill %}\n  {% endfor %}\n{% endcomponent %}\n</code></pre> <ul> <li>If you need to access the data or the default content of a default fill, you can   set the <code>name</code> kwarg to <code>\"default\"</code>.</li> </ul> <p>Previously, a default fill would be defined simply by omitting the <code>{% fill %}</code> tags:</p> <pre><code>{% component \"child\" %}\n  Hello world\n{% endcomponent %}\n</code></pre> <p>But in that case you could not access the slot data or the default content, like it's possible   for named fills:</p> <pre><code>{% component \"child\" %}\n  {% fill name=\"header\" data=\"data\" %}\n    Hello {{ data.user.name }}\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <p>Now, you can specify default tag by using <code>name=\"default\"</code>:</p> <pre><code>{% component \"child\" %}\n  {% fill name=\"default\" data=\"data\" %}\n    Hello {{ data.user.name }}\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <ul> <li>When inside <code>get_context_data()</code> or other component methods, the default fill   can now be accessed as <code>Component.input.slots[\"default\"]</code>, e.g.:</li> </ul> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        default_slot = self.input.slots[\"default\"]\n        ...\n</code></pre> <ul> <li>You can now dynamically pass all slots to a child component. This is similar to   passing all slots in Vue:</li> </ul> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"slots\": self.input.slots,\n        }\n\n    template: \"\"\"\n      &lt;div&gt;\n        {% component \"child\" %}\n          {% for slot_name in slots %}\n            {% fill name=slot_name data=\"data\" %}\n              {% slot name=slot_name ...data / %}\n            {% endfill %}\n          {% endfor %}\n        {% endcomponent %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre>"},{"location":"release_notes/#fix_14","title":"Fix","text":"<ul> <li> <p>Slots defined with <code>{% fill %}</code> tags are now properly accessible via <code>self.input.slots</code> in <code>get_context_data()</code></p> </li> <li> <p>Do not raise error if multiple slots with same name are flagged as default</p> </li> <li> <p>Slots can now be defined within loops (<code>{% for %}</code>) or other tags (like <code>{% with %}</code>),   or even other templates using <code>{% include %}</code>.</p> </li> </ul> <p>Previously, following would cause the kwarg <code>name</code> to be an empty string:</p> <pre><code>{% for slot_name in slots %}\n  {% slot name=slot_name %}\n{% endfor %}\n</code></pre>"},{"location":"release_notes/#refactor_9","title":"Refactor","text":"<ul> <li>When you define multiple slots with the same name inside a template,   you now have to set the <code>default</code> and <code>required</code> flags individually.</li> </ul> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"image\" default required %}Image here{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"image\" default required %}Image here{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>This means you can also have multiple slots with the same name but   different conditions.</p> <p>E.g. in this example, we have a component that renders a user avatar   - a small circular image with a profile picture of name initials.</p> <p>If the component is given <code>image_src</code> or <code>name_initials</code> variables,   the <code>image</code> slot is optional. But if neither of those are provided,   you MUST fill the <code>image</code> slot.</p> <pre><code>&lt;div class=\"avatar\"&gt;\n    {% if image_src %}\n        {% slot \"image\" default %}\n            &lt;img src=\"{{ image_src }}\" /&gt;\n        {% endslot %}\n    {% elif name_initials %}\n        {% slot \"image\" default required %}\n            &lt;div style=\"\n                border-radius: 25px;\n                width: 50px;\n                height: 50px;\n                background: blue;\n            \"&gt;\n                {{ name_initials }}\n            &lt;/div&gt;\n        {% endslot %}\n    {% else %}\n        {% slot \"image\" default required / %}\n    {% endif %}\n&lt;/div&gt;\n</code></pre> <ul> <li>The slot fills that were passed to a component and which can be accessed as <code>Component.input.slots</code>   can now be passed through the Django template, e.g. as inputs to other tags.</li> </ul> <p>Internally, django-components handles slot fills as functions.</p> <p>Previously, if you tried to pass a slot fill within a template, Django would try to call it as a function.</p> <p>Now, something like this is possible:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"child_slot\": self.input.slots[\"child_slot\"],\n        }\n\n    template: \"\"\"\n      &lt;div&gt;\n        {% component \"child\" content=child_slot / %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre> <p>NOTE: Using <code>{% slot %}</code> and <code>{% fill %}</code> tags is still the preferred method, but the approach above   may be necessary in some complex or edge cases.</p> <ul> <li>The <code>is_filled</code> variable (and the <code>{{ component_vars.is_filled }}</code> context variable) now returns   <code>False</code> when you try to access a slot name which has not been defined:</li> </ul> <p>Before:</p> <pre><code>{{ component_vars.is_filled.header }} -&gt; True\n{{ component_vars.is_filled.footer }} -&gt; False\n{{ component_vars.is_filled.nonexist }} -&gt; \"\" (empty string)\n</code></pre> <p>After:   <pre><code>{{ component_vars.is_filled.header }} -&gt; True\n{{ component_vars.is_filled.footer }} -&gt; False\n{{ component_vars.is_filled.nonexist }} -&gt; False\n</code></pre></p> <ul> <li> <p>Components no longer raise an error if there are extra slot fills</p> </li> <li> <p>Components will raise error when a slot is doubly-filled. </p> </li> </ul> <p>E.g. if we have a component with a default slot:</p> <pre><code>{% slot name=\"content\" default / %}\n</code></pre> <p>Now there is two ways how we can target this slot: Either using <code>name=\"default\"</code>   or <code>name=\"content\"</code>.</p> <p>In case you specify BOTH, the component will raise an error:</p> <pre><code>{% component \"child\" %}\n  {% fill slot=\"default\" %}\n    Hello from default slot\n  {% endfill %}\n  {% fill slot=\"content\" data=\"data\" %}\n    Hello from content slot\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"release_notes/#v0100","title":"\ud83d\udea8\ud83d\udce2 v0.100","text":""},{"location":"release_notes/#breaking-changes_2","title":"BREAKING CHANGES","text":"<ul> <li> <p><code>django_components.safer_staticfiles</code> app was removed. It is no longer needed.</p> </li> <li> <p>Installation changes:</p> <ul> <li>Instead of defining component directories in <code>STATICFILES_DIRS</code>, set them to <code>COMPONENTS.dirs</code>.</li> <li> <p>You now must define <code>STATICFILES_FINDERS</code></p> </li> <li> <p>See here how to migrate your settings.py</p> </li> </ul> </li> </ul>"},{"location":"release_notes/#feat_10","title":"Feat","text":"<ul> <li>Beside the top-level <code>/components</code> directory, you can now define also app-level components dirs, e.g. <code>[app]/components</code>   (See <code>COMPONENTS.app_dirs</code>).</li> </ul>"},{"location":"release_notes/#refactor_10","title":"Refactor","text":"<ul> <li>When you call <code>as_view()</code> on a component instance, that instance will be passed to <code>View.as_view()</code></li> </ul>"},{"location":"release_notes/#v097","title":"v0.97","text":""},{"location":"release_notes/#fix_15","title":"Fix","text":"<ul> <li>Fixed template caching. You can now also manually create cached templates with <code>cached_template()</code></li> </ul>"},{"location":"release_notes/#refactor_11","title":"Refactor","text":"<ul> <li> <p>The previously undocumented <code>get_template</code> was made private.</p> </li> <li> <p>In it's place, there's a new <code>get_template</code>, which supersedes <code>get_template_string</code> (will be removed in v1). The new <code>get_template</code> is the same as <code>get_template_string</code>, except   it allows to return either a string or a Template instance.</p> </li> <li> <p>You now must use only one of <code>template</code>, <code>get_template</code>, <code>template_name</code>, or <code>get_template_name</code>.</p> </li> </ul>"},{"location":"release_notes/#v096","title":"v0.96","text":""},{"location":"release_notes/#feat_11","title":"Feat","text":"<ul> <li> <p>Run-time type validation for Python 3.11+ - If the <code>Component</code> class is typed, e.g. <code>Component[Args, Kwargs, ...]</code>, the args, kwargs, slots, and data are validated against the given types. (See Runtime input validation with types)</p> </li> <li> <p>Render hooks - Set <code>on_render_before</code> and <code>on_render_after</code> methods on <code>Component</code> to intercept or modify the template or context before rendering, or the rendered result afterwards. (See Component hooks)</p> </li> <li> <p><code>component_vars.is_filled</code> context variable can be accessed from within <code>on_render_before</code> and <code>on_render_after</code> hooks as <code>self.is_filled.my_slot</code></p> </li> </ul>"},{"location":"release_notes/#095","title":"0.95","text":""},{"location":"release_notes/#feat_12","title":"Feat","text":"<ul> <li>Added support for dynamic components, where the component name is passed as a variable. (See Dynamic components)</li> </ul>"},{"location":"release_notes/#refactor_12","title":"Refactor","text":"<ul> <li>Changed <code>Component.input</code> to raise <code>RuntimeError</code> if accessed outside of render context. Previously it returned <code>None</code> if unset.</li> </ul>"},{"location":"release_notes/#v094","title":"v0.94","text":""},{"location":"release_notes/#feat_13","title":"Feat","text":"<ul> <li> <p>django_components now automatically configures Django to support multi-line tags. (See Multi-line tags)</p> </li> <li> <p>New setting <code>reload_on_template_change</code>. Set this to <code>True</code> to reload the dev server on changes to component template files. (See Reload dev server on component file changes)</p> </li> </ul>"},{"location":"release_notes/#v093","title":"v0.93","text":""},{"location":"release_notes/#feat_14","title":"Feat","text":"<ul> <li> <p>Spread operator <code>...dict</code> inside template tags. (See Spread operator)</p> </li> <li> <p>Use template tags inside string literals in component inputs. (See Use template tags inside component inputs)</p> </li> <li> <p>Dynamic slots, fills and provides - The <code>name</code> argument for these can now be a variable, a template expression, or via spread operator</p> </li> <li> <p>Component library authors can now configure <code>CONTEXT_BEHAVIOR</code> and <code>TAG_FORMATTER</code> settings independently from user settings.</p> </li> </ul>"},{"location":"release_notes/#v092","title":"\ud83d\udea8\ud83d\udce2 v0.92","text":""},{"location":"release_notes/#breaking-changes_3","title":"BREAKING CHANGES","text":"<ul> <li><code>Component</code> class is no longer a subclass of <code>View</code>. To configure the <code>View</code> class, set the <code>Component.View</code> nested class. HTTP methods like <code>get</code> or <code>post</code> can still be defined directly on <code>Component</code> class, and <code>Component.as_view()</code> internally calls <code>Component.View.as_view()</code>. (See Modifying the View class)</li> </ul>"},{"location":"release_notes/#feat_15","title":"Feat","text":"<ul> <li> <p>The inputs (args, kwargs, slots, context, ...) that you pass to <code>Component.render()</code> can be accessed from within <code>get_context_data</code>, <code>get_template</code> and <code>get_template_name</code> via <code>self.input</code>. (See Accessing data passed to the component)</p> </li> <li> <p>Typing: <code>Component</code> class supports generics that specify types for <code>Component.render</code> (See Adding type hints with Generics)</p> </li> </ul>"},{"location":"release_notes/#v090","title":"v0.90","text":""},{"location":"release_notes/#feat_16","title":"Feat","text":"<ul> <li> <p>All tags (<code>component</code>, <code>slot</code>, <code>fill</code>, ...) now support \"self-closing\" or \"inline\" form, where you can omit the closing tag:</p> <pre><code>{# Before #}\n{% component \"button\" %}{% endcomponent %}\n{# After #}\n{% component \"button\" / %}\n</code></pre> </li> <li> <p>All tags now support the \"dictionary key\" or \"aggregate\" syntax (<code>kwarg:key=val</code>):</p> <pre><code>{% component \"button\" attrs:class=\"hidden\" %}\n</code></pre> </li> <li> <p>You can change how the components are written in the template with TagFormatter.</p> <p>The default is <code>django_components.component_formatter</code>:</p> <pre><code>{% component \"button\" href=\"...\" disabled %}\n    Click me!\n{% endcomponent %}\n</code></pre> <p>While <code>django_components.shorthand_component_formatter</code> allows you to write components like so:</p> <pre><code>{% button href=\"...\" disabled %}\n    Click me!\n{% endbutton %}\n</code></pre> </li> </ul>"},{"location":"release_notes/#v085","title":"\ud83d\udea8\ud83d\udce2 v0.85","text":""},{"location":"release_notes/#breaking-changes_4","title":"BREAKING CHANGES","text":"<ul> <li> <p>Autodiscovery module resolution changed. Following undocumented behavior was removed:</p> <ul> <li> <p>Previously, autodiscovery also imported any <code>[app]/components.py</code> files, and used <code>SETTINGS_MODULE</code> to search for component dirs.</p> <p>To migrate from:</p> <ul> <li> <p><code>[app]/components.py</code> - Define each module in <code>COMPONENTS.libraries</code> setting,     or import each module inside the <code>AppConfig.ready()</code> hook in respective <code>apps.py</code> files.</p> </li> <li> <p><code>SETTINGS_MODULE</code> - Define component dirs using <code>STATICFILES_DIRS</code></p> </li> </ul> </li> <li> <p>Previously, autodiscovery handled relative files in <code>STATICFILES_DIRS</code>. To align with Django, <code>STATICFILES_DIRS</code> now must be full paths (Django docs).</p> </li> </ul> </li> </ul>"},{"location":"release_notes/#v081","title":"\ud83d\udea8\ud83d\udce2 v0.81","text":""},{"location":"release_notes/#breaking-changes_5","title":"BREAKING CHANGES","text":"<ul> <li>The order of arguments to <code>render_to_response</code> has changed, to align with the (now public) <code>render</code> method of <code>Component</code> class.</li> </ul>"},{"location":"release_notes/#feat_17","title":"Feat","text":"<ul> <li> <p><code>Component.render()</code> is public and documented</p> </li> <li> <p>Slots passed <code>render_to_response</code> and <code>render</code> can now be rendered also as functions.</p> </li> </ul>"},{"location":"release_notes/#v080","title":"v0.80","text":""},{"location":"release_notes/#feat_18","title":"Feat","text":"<ul> <li>Vue-like provide/inject with the <code>{% provide %}</code> tag and <code>inject()</code> method.</li> </ul>"},{"location":"release_notes/#v079","title":"\ud83d\udea8\ud83d\udce2 v0.79","text":""},{"location":"release_notes/#breaking-changes_6","title":"BREAKING CHANGES","text":"<ul> <li>Default value for the <code>COMPONENTS.context_behavior</code> setting was changes from <code>\"isolated\"</code> to <code>\"django\"</code>. If you did not set this value explicitly before, this may be a breaking change. See the rationale for change here.</li> </ul>"},{"location":"release_notes/#v077","title":"\ud83d\udea8\ud83d\udce2 v0.77","text":""},{"location":"release_notes/#breaking","title":"BREAKING","text":"<ul> <li> <p>The syntax for accessing default slot content has changed from</p> <pre><code>{% fill \"my_slot\" as \"alias\" %}\n    {{ alias.default }}\n{% endfill %}\n</code></pre> <p>to</p> <pre><code>{% fill \"my_slot\" default=\"alias\" %}\n    {{ alias }}\n{% endfill %}\n</code></pre> </li> </ul>"},{"location":"release_notes/#v074","title":"v0.74","text":""},{"location":"release_notes/#feat_19","title":"Feat","text":"<ul> <li> <p><code>{% html_attrs %}</code> tag for formatting data as HTML attributes</p> </li> <li> <p><code>prefix:key=val</code> construct for passing dicts to components</p> </li> </ul>"},{"location":"release_notes/#v070","title":"\ud83d\udea8\ud83d\udce2 v0.70","text":""},{"location":"release_notes/#breaking-changes_7","title":"BREAKING CHANGES","text":"<ul> <li> <p><code>{% if_filled \"my_slot\" %}</code> tags were replaced with <code>{{ component_vars.is_filled.my_slot }}</code> variables.</p> </li> <li> <p>Simplified settings - <code>slot_context_behavior</code> and <code>context_behavior</code> were merged. See the documentation for more details.</p> </li> </ul>"},{"location":"release_notes/#v067","title":"v0.67","text":""},{"location":"release_notes/#refactor_13","title":"Refactor","text":"<ul> <li>Changed the default way how context variables are resolved in slots. See the documentation for more details.</li> </ul>"},{"location":"release_notes/#v050","title":"\ud83d\udea8\ud83d\udce2 v0.50","text":""},{"location":"release_notes/#breaking-changes_8","title":"BREAKING CHANGES","text":"<ul> <li> <p><code>{% component_block %}</code> is now <code>{% component %}</code>, and <code>{% component %}</code> blocks need an ending <code>{% endcomponent %}</code> tag.</p> <p>The new <code>python manage.py upgradecomponent</code> command can be used to upgrade a directory (use <code>--path</code> argument to point to each dir) of templates that use components to the new syntax automatically.</p> <p>This change is done to simplify the API in anticipation of a 1.0 release of django_components. After 1.0 we intend to be stricter with big changes like this in point releases.</p> </li> </ul>"},{"location":"release_notes/#v034","title":"v0.34","text":""},{"location":"release_notes/#feat_20","title":"Feat","text":"<ul> <li>Components as views, which allows you to handle requests and render responses from within a component. See the documentation for more details.</li> </ul>"},{"location":"release_notes/#v028","title":"v0.28","text":""},{"location":"release_notes/#feat_21","title":"Feat","text":"<ul> <li>'implicit' slot filling and the <code>default</code> option for <code>slot</code> tags.</li> </ul>"},{"location":"release_notes/#v027","title":"v0.27","text":""},{"location":"release_notes/#feat_22","title":"Feat","text":"<ul> <li>A second installable app <code>django_components.safer_staticfiles</code>. It provides the same behavior as <code>django.contrib.staticfiles</code> but with extra security guarantees (more info below in Security Notes).</li> </ul>"},{"location":"release_notes/#v026","title":"\ud83d\udea8\ud83d\udce2 v0.26","text":""},{"location":"release_notes/#breaking-changes_9","title":"BREAKING CHANGES","text":"<ul> <li> <p>Changed the syntax for <code>{% slot %}</code> tags. From now on, we separate defining a slot (<code>{% slot %}</code>) from filling a slot with content (<code>{% fill %}</code>). This means you will likely need to change a lot of slot tags to fill.</p> <p>We understand this is annoying, but it's the only way we can get support for nested slots that fill in other slots, which is a very nice feature to have access to. Hoping that this will feel worth it!</p> </li> </ul>"},{"location":"release_notes/#v022","title":"v0.22","text":""},{"location":"release_notes/#feat_23","title":"Feat","text":"<ul> <li> <p>All files inside components subdirectores are autoimported to simplify setup.</p> <p>An existing project might start to get <code>AlreadyRegistered</code> errors because of this. To solve this, either remove your custom loading of components, or set <code>\"autodiscover\": False</code> in <code>settings.COMPONENTS</code>.</p> </li> </ul>"},{"location":"release_notes/#v017","title":"v0.17","text":""},{"location":"release_notes/#breaking-changes_10","title":"BREAKING CHANGES","text":"<ul> <li> <p>Renamed <code>Component.context</code> and <code>Component.template</code> to <code>get_context_data</code> and <code>get_template_name</code>. The old methods still work, but emit a deprecation warning.</p> <p>This change was done to sync naming with Django's class based views, and make using django-components more familiar to Django users. <code>Component.context</code> and <code>Component.template</code> will be removed when version 1.0 is released.</p> </li> </ul>"},{"location":"concepts/advanced/authoring_component_libraries/","title":"Authoring component libraries","text":"<p>You can publish and share your components for others to use. Below you will find the steps to do so.</p> <p>For live examples, see the Community examples.</p>"},{"location":"concepts/advanced/authoring_component_libraries/#writing-component-libraries","title":"Writing component libraries","text":"<ol> <li> <p>Create a Django project with a similar structure:</p> <pre><code>project/\n  |--  myapp/\n    |--  __init__.py\n    |--  apps.py\n    |--  templates/\n      |--  table/\n        |--  table.py\n        |--  table.js\n        |--  table.css\n        |--  table.html\n    |--  menu.py   &lt;--- single-file component\n  |--  templatetags/\n    |--  __init__.py\n    |--  mytags.py\n</code></pre> </li> <li> <p>Create custom <code>Library</code>     and <code>ComponentRegistry</code> instances in <code>mytags.py</code></p> <p>This will be the entrypoint for using the components inside Django templates.</p> <p>Remember that Django requires the <code>Library</code> instance to be accessible under the <code>register</code> variable (See Django docs):</p> <pre><code>from django.template import Library\nfrom django_components import ComponentRegistry, RegistrySettings\n\nregister = library = django.template.Library()\ncomp_registry = ComponentRegistry(\n    library=library,\n    settings=RegistrySettings(\n        context_behavior=\"isolated\",\n        tag_formatter=\"django_components.component_formatter\",\n    ),\n)\n</code></pre> <p>As you can see above, this is also the place where we configure how our components should behave, using the <code>settings</code> argument. If omitted, default settings are used.</p> <p>For library authors, we recommend setting <code>context_behavior</code> to <code>\"isolated\"</code>, so that the state cannot leak into the components, and so the components' behavior is configured solely through the inputs. This means that the components will be more predictable and easier to debug.</p> <p>Next, you can decide how will others use your components by setting the <code>tag_formatter</code> options.</p> <p>If omitted or set to <code>\"django_components.component_formatter\"</code>, your components will be used like this:</p> <pre><code>{% component \"table\" items=items headers=headers %}\n{% endcomponent %}\n</code></pre> <p>Or you can use <code>\"django_components.component_shorthand_formatter\"</code> to use components like so:</p> <pre><code>{% table items=items headers=headers %}\n{% endtable %}\n</code></pre> <p>Or you can define a custom TagFormatter.</p> <p>Either way, these settings will be scoped only to your components. So, in the user code, there may be components side-by-side that use different formatters:</p> <pre><code>{% load mytags %}\n\n{# Component from your library \"mytags\", using the \"shorthand\" formatter #}\n{% table items=items headers=header %}\n{% endtable %}\n\n{# User-created components using the default settings #}\n{% component \"my_comp\" title=\"Abc...\" %}\n{% endcomponent %}\n</code></pre> </li> <li> <p>Write your components and register them with your instance of <code>ComponentRegistry</code></p> <p>There's one difference when you are writing components that are to be shared, and that's that the components must be explicitly registered with your instance of <code>ComponentRegistry</code> from the previous step.</p> <p>For better user experience, you can also define the types for the args, kwargs, slots and data.</p> <p>It's also a good idea to have a common prefix for your components, so they can be easily distinguished from users' components. In the example below, we use the prefix <code>my_</code> / <code>My</code>.</p> <pre><code>from typing import Dict, NotRequired, Optional, Tuple, TypedDict\n\nfrom django_components import Component, SlotFunc, register, types\n\nfrom myapp.templatetags.mytags import comp_registry\n\n# Define the types\nclass EmptyDict(TypedDict):\n    pass\n\ntype MyMenuArgs = Tuple[int, str]\n\nclass MyMenuSlots(TypedDict):\n    default: NotRequired[Optional[SlotFunc[EmptyDict]]]\n\nclass MyMenuProps(TypedDict):\n    vertical: NotRequired[bool]\n    klass: NotRequired[str]\n    style: NotRequired[str]\n\n# Define the component\n# NOTE: Don't forget to set the `registry`!\n@register(\"my_menu\", registry=comp_registry)\nclass MyMenu(Component[MyMenuArgs, MyMenuProps, MyMenuSlots, Any, Any, Any]):\n    def get_context_data(\n        self,\n        *args,\n        attrs: Optional[Dict] = None,\n    ):\n        return {\n            \"attrs\": attrs,\n        }\n\n    template: types.django_html = \"\"\"\n        {# Load django_components template tags #}\n        {% load component_tags %}\n\n        &lt;div {% html_attrs attrs class=\"my-menu\" %}&gt;\n            &lt;div class=\"my-menu__content\"&gt;\n                {% slot \"default\" default / %}\n            &lt;/div&gt;\n        &lt;/div&gt;\n    \"\"\"\n</code></pre> </li> <li> <p>Import the components in <code>apps.py</code></p> <p>Normally, users rely on autodiscovery and <code>COMPONENTS.dirs</code> to load the component files.</p> <p>Since you, as the library author, are not in control of the file system, it is recommended to load the components manually.</p> <p>We recommend doing this in the <code>AppConfig.ready()</code> hook of your <code>apps.py</code>:</p> <pre><code>from django.apps import AppConfig\n\nclass MyAppConfig(AppConfig):\n    default_auto_field = \"django.db.models.BigAutoField\"\n    name = \"myapp\"\n\n    # This is the code that gets run when user adds myapp\n    # to Django's INSTALLED_APPS\n    def ready(self) -&gt; None:\n        # Import the components that you want to make available\n        # inside the templates.\n        from myapp.templates import (\n            menu,\n            table,\n        )\n</code></pre> <p>Note that you can also include any other startup logic within <code>AppConfig.ready()</code>.</p> </li> </ol> <p>And that's it! The next step is to publish it.</p>"},{"location":"concepts/advanced/authoring_component_libraries/#publishing-component-libraries","title":"Publishing component libraries","text":"<p>Once you are ready to share your library, you need to build a distribution and then publish it to PyPI.</p> <p>django_components uses the <code>build</code> utility to build a distribution:</p> <pre><code>python -m build --sdist --wheel --outdir dist/ .\n</code></pre> <p>And to publish to PyPI, you can use <code>twine</code> (See Python user guide)</p> <pre><code>twine upload --repository pypi dist/* -u __token__ -p &lt;PyPI_TOKEN&gt;\n</code></pre> <p>Notes on publishing:</p> <ul> <li>If you use components where the HTML / CSS / JS files are separate, you may need to define   <code>MANIFEST.in</code>   to include those files with the distribution   (see user guide).</li> </ul>"},{"location":"concepts/advanced/authoring_component_libraries/#installing-and-using-component-libraries","title":"Installing and using component libraries","text":"<p>After the package has been published, all that remains is to install it in other django projects:</p> <ol> <li> <p>Install the package:</p> <pre><code>pip install myapp django_components\n</code></pre> </li> <li> <p>Add the package to <code>INSTALLED_APPS</code></p> <pre><code>INSTALLED_APPS = [\n    ...\n    \"django_components\",\n    \"myapp\",\n]\n</code></pre> </li> <li> <p>Optionally add the template tags to the <code>builtins</code>,    so you don't have to call <code>{% load mytags %}</code> in every template:</p> <pre><code>TEMPLATES = [\n    {\n        ...,\n        'OPTIONS': {\n            'builtins': [\n                'myapp.templatetags.mytags',\n            ]\n        },\n    },\n]\n</code></pre> </li> <li> <p>And, at last, you can use the components in your own project!</p> <pre><code>{% my_menu title=\"Abc...\" %}\n    Hello World!\n{% endmy_menu %}\n</code></pre> </li> </ol>"},{"location":"concepts/advanced/component_registry/","title":"Registering components","text":"<p>In previous examples you could repeatedly see us using <code>@register()</code> to \"register\" the components. In this section we dive deeper into what it actually means and how you can manage (add or remove) components.</p> <p>As a reminder, we may have a component like this:</p> <pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"template.html\"\n\n    # This component takes one parameter, a date string to show in the template\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n</code></pre> <p>which we then render in the template as:</p> <pre><code>{% component \"calendar\" date=\"1970-01-01\" %}\n{% endcomponent %}\n</code></pre> <p>As you can see, <code>@register</code> links up the component class with the <code>{% component %}</code> template tag. So when the template tag comes across a component called <code>\"calendar\"</code>, it can look up it's class and instantiate it.</p>"},{"location":"concepts/advanced/component_registry/#what-is-componentregistry","title":"What is ComponentRegistry","text":"<p>The <code>@register</code> decorator is a shortcut for working with the <code>ComponentRegistry</code>.</p> <p><code>ComponentRegistry</code> manages which components can be used in the template tags.</p> <p>Each <code>ComponentRegistry</code> instance is associated with an instance of Django's <code>Library</code>. And Libraries are inserted into Django template using the <code>{% load %}</code> tags.</p> <p>The <code>@register</code> decorator accepts an optional kwarg <code>registry</code>, which specifies, the <code>ComponentRegistry</code> to register components into. If omitted, the default <code>ComponentRegistry</code> instance defined in django_components is used.</p> <pre><code>my_registry = ComponentRegistry()\n\n@register(registry=my_registry)\nclass MyComponent(Component):\n    ...\n</code></pre> <p>The default <code>ComponentRegistry</code> is associated with the <code>Library</code> that you load when you call <code>{% load component_tags %}</code> inside your template, or when you add <code>django_components.templatetags.component_tags</code> to the template builtins.</p> <p>So when you register or unregister a component to/from a component registry, then behind the scenes the registry automatically adds/removes the component's template tags to/from the Library, so you can call the component from within the templates such as <code>{% component \"my_comp\" %}</code>.</p>"},{"location":"concepts/advanced/component_registry/#working-with-componentregistry","title":"Working with ComponentRegistry","text":"<p>The default <code>ComponentRegistry</code> instance can be imported as:</p> <pre><code>from django_components import registry\n</code></pre> <p>You can use the registry to manually add/remove/get components:</p> <pre><code>from django_components import registry\n\n# Register components\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\n\n# Get all or single\nregistry.all()  # {\"button\": ButtonComponent, \"card\": CardComponent}\nregistry.get(\"card\")  # CardComponent\n\n# Check if component is registered\nregistry.has(\"button\")  # True\n\n# Unregister single component\nregistry.unregister(\"card\")\n\n# Unregister all components\nregistry.clear()\n</code></pre>"},{"location":"concepts/advanced/component_registry/#registering-components-to-custom-componentregistry","title":"Registering components to custom ComponentRegistry","text":"<p>If you are writing a component library to be shared with others, you may want to manage your own instance of <code>ComponentRegistry</code> and register components onto a different <code>Library</code> instance than the default one.</p> <p>The <code>Library</code> instance can be set at instantiation of <code>ComponentRegistry</code>. If omitted, then the default Library instance from django_components is used.</p> <pre><code>from django.template import Library\nfrom django_components import ComponentRegistry\n\nmy_library = Library(...)\nmy_registry = ComponentRegistry(library=my_library)\n</code></pre> <p>When you have defined your own <code>ComponentRegistry</code>, you can either register the components with <code>my_registry.register()</code>, or pass the registry to the <code>@component.register()</code> decorator via the <code>registry</code> kwarg:</p> <pre><code>from path.to.my.registry import my_registry\n\n@register(\"my_component\", registry=my_registry)\nclass MyComponent(Component):\n    ...\n</code></pre> <p>NOTE: The Library instance can be accessed under <code>library</code> attribute of <code>ComponentRegistry</code>.</p>"},{"location":"concepts/advanced/component_registry/#componentregistry-settings","title":"ComponentRegistry settings","text":"<p>When you are creating an instance of <code>ComponentRegistry</code>, you can define the components' behavior within the template.</p> <p>The registry accepts these settings:</p> <ul> <li><code>context_behavior</code></li> <li><code>tag_formatter</code></li> </ul> <pre><code>from django.template import Library\nfrom django_components import ComponentRegistry, RegistrySettings\n\nregister = library = django.template.Library()\ncomp_registry = ComponentRegistry(\n    library=library,\n    settings=RegistrySettings(\n        context_behavior=\"isolated\",\n        tag_formatter=\"django_components.component_formatter\",\n    ),\n)\n</code></pre> <p>These settings are the same as the ones you can set for django_components.</p> <p>In fact, when you set <code>COMPONENT.tag_formatter</code> or <code>COMPONENT.context_behavior</code>, these are forwarded to the default <code>ComponentRegistry</code>.</p> <p>This makes it possible to have multiple registries with different settings in one projects, and makes sharing of component libraries possible.</p>"},{"location":"concepts/advanced/extensions/","title":"Extensions","text":"<p>New in version 0.131</p> <p>Django-components functionality can be extended with \"extensions\". Extensions allow for powerful customization and integrations. They can:</p> <ul> <li>Tap into lifecycle events, such as when a component is created, deleted, registered, or unregistered.</li> <li>Add new attributes and methods to the components under an extension-specific nested class.</li> <li>Define custom commands that can be executed via the Django management command interface.</li> </ul>"},{"location":"concepts/advanced/extensions/#setting-up-extensions","title":"Setting up extensions","text":"<p>Extensions are configured in the Django settings under <code>COMPONENTS.extensions</code>.</p> <p>Extensions can be set by either as an import string or by passing in a class:</p> <pre><code># settings.py\n\nclass MyExtension(ComponentExtension):\n    name = \"my_extension\"\n\n    class ExtensionClass(ComponentExtension.ExtensionClass):\n        ...\n\nCOMPONENTS = ComponentsSettings(\n    extensions=[\n        MyExtension,\n        \"another_app.extensions.AnotherExtension\",\n        \"my_app.extensions.ThirdExtension\",\n    ],\n)\n</code></pre>"},{"location":"concepts/advanced/extensions/#lifecycle-hooks","title":"Lifecycle hooks","text":"<p>Extensions can define methods to hook into lifecycle events, such as:</p> <ul> <li>Component creation or deletion</li> <li>Un/registering a component</li> <li>Creating or deleting a registry</li> <li>Pre-processing data passed to a component on render</li> <li>Post-processing data returned from <code>get_context_data()</code>   and others.</li> </ul> <p>See the full list in Extension Hooks Reference.</p>"},{"location":"concepts/advanced/extensions/#configuring-extensions-per-component","title":"Configuring extensions per component","text":"<p>Each extension has a corresponding nested class within the <code>Component</code> class. These allow to configure the extensions on a per-component basis.</p> <p>Note</p> <p>Accessing the component instance from inside the nested classes:</p> <p>Each method of the nested classes has access to the <code>component</code> attribute, which points to the component instance.</p> <pre><code>class MyTable(Component):\n    class View:\n        def get(self, request):\n            # `self.component` points to the instance of `MyTable` Component.\n            return self.component.get(request)\n</code></pre>"},{"location":"concepts/advanced/extensions/#example-component-as-view","title":"Example: Component as View","text":"<p>The Components as Views feature is actually implemented as an extension that is configured by a <code>View</code> nested class.</p> <p>You can override the <code>get</code>, <code>post</code>, etc methods to customize the behavior of the component as a view:</p> <pre><code>class MyTable(Component):\n    class View:\n        def get(self, request):\n            return self.component.get(request)\n\n        def post(self, request):\n            return self.component.post(request)\n\n        ...\n</code></pre>"},{"location":"concepts/advanced/extensions/#example-storybook-integration","title":"Example: Storybook integration","text":"<p>The Storybook integration (work in progress) is an extension that is configured by a <code>Storybook</code> nested class.</p> <p>You can override methods such as <code>title</code>, <code>parameters</code>, etc, to customize how to generate a Storybook JSON file from the component.</p> <pre><code>class MyTable(Component):\n    class Storybook:\n        def title(self):\n            return self.component.__class__.__name__\n\n        def parameters(self) -&gt; Parameters:\n            return {\n                \"server\": {\n                    \"id\": self.component.__class__.__name__,\n                }\n            }\n\n        def stories(self) -&gt; List[StoryAnnotations]:\n            return []\n\n        ...\n</code></pre>"},{"location":"concepts/advanced/extensions/#accessing-extensions-in-components","title":"Accessing extensions in components","text":"<p>Above, we've configured extensions <code>View</code> and <code>Storybook</code> for the <code>MyTable</code> component.</p> <p>You can access the instances of these extension classes in the component instance.</p> <p>For example, the View extension is available as <code>self.view</code>:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, request):\n        # `self.view` points to the instance of `View` extension.\n        return {\n            \"view\": self.view,\n        }\n</code></pre> <p>And the Storybook extension is available as <code>self.storybook</code>:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, request):\n        # `self.storybook` points to the instance of `Storybook` extension.\n        return {\n            \"title\": self.storybook.title(),\n        }\n</code></pre> <p>Thus, you can use extensions to add methods or attributes that will be available to all components in their component context.</p>"},{"location":"concepts/advanced/extensions/#writing-extensions","title":"Writing extensions","text":"<p>Creating extensions in django-components involves defining a class that inherits from <code>ComponentExtension</code>. This class can implement various lifecycle hooks and define new attributes or methods to be added to components.</p>"},{"location":"concepts/advanced/extensions/#defining-an-extension","title":"Defining an extension","text":"<p>To create an extension, define a class that inherits from <code>ComponentExtension</code> and implement the desired hooks.</p> <ul> <li>Each extension MUST have a <code>name</code> attribute. The name MUST be a valid Python identifier.</li> <li>The extension MAY implement any of the hook methods.</li> <li>Each hook method receives a context object with relevant data.</li> </ul> <pre><code>from django_components.extension import ComponentExtension, OnComponentClassCreatedContext\n\nclass MyExtension(ComponentExtension):\n    name = \"my_extension\"\n\n    def on_component_class_created(self, ctx: OnComponentClassCreatedContext) -&gt; None:\n        # Custom logic for when a component class is created\n        ctx.component_cls.my_attr = \"my_value\"\n</code></pre>"},{"location":"concepts/advanced/extensions/#defining-the-extension-class","title":"Defining the extension class","text":"<p>In previous sections we've seen the <code>View</code> and <code>Storybook</code> extensions classes that were nested within the <code>Component</code> class:</p> <pre><code>class MyComponent(Component):\n    class View:\n        ...\n\n    class Storybook:\n        ...\n</code></pre> <p>These can be understood as component-specific overrides or configuration.</p> <p>The nested extension classes like <code>View</code> or <code>Storybook</code> will actually subclass from a base extension class as defined on the <code>ComponentExtension.ExtensionClass</code>.</p> <p>This is how extensions define the \"default\" behavior of their nested extension classes.</p> <p>For example, the <code>View</code> base extension class defines the handlers for GET, POST, etc:</p> <pre><code>from django_components.extension import ComponentExtension\n\nclass ViewExtension(ComponentExtension):\n    name = \"view\"\n\n    # The default behavior of the `View` extension class.\n    class ExtensionClass(ComponentExtension.ExtensionClass):\n        def get(self, request):\n            return self.component.get(request)\n\n        def post(self, request):\n            return self.component.post(request)\n\n        ...\n</code></pre> <p>In any component that then defines a nested <code>View</code> extension class, the <code>View</code> extension class will actually subclass from the <code>ViewExtension.ExtensionClass</code> class.</p> <p>In other words, when you define a component like this:</p> <pre><code>class MyTable(Component):\n    class View:\n        def get(self, request):\n            # Do something\n            ...\n</code></pre> <p>It will actually be implemented as if the <code>View</code> class subclassed from base class <code>ViewExtension.ExtensionClass</code>:</p> <pre><code>class MyTable(Component):\n    class View(ViewExtension.ExtensionClass):\n        def get(self, request):\n            # Do something\n            ...\n</code></pre> <p>Warning</p> <p>When writing an extension, the <code>ExtensionClass</code> MUST subclass the base class <code>ComponentExtension.ExtensionClass</code>.</p> <p>This base class ensures that the extension class will have access to the component instance.</p>"},{"location":"concepts/advanced/extensions/#registering-extensions","title":"Registering extensions","text":"<p>Once the extension is defined, it needs to be registered in the Django settings to be used by the application.</p> <p>Extensions can be given either as an extension class, or its import string:</p> <pre><code># settings.py\nCOMPONENTS = {\n    \"extensions\": [\n        \"my_app.extensions.MyExtension\",\n    ],\n}\n</code></pre> <p>Or by reference:</p> <pre><code># settings.py\nfrom my_app.extensions import MyExtension\n\nCOMPONENTS = {\n    \"extensions\": [\n        MyExtension,\n    ],\n}\n</code></pre>"},{"location":"concepts/advanced/extensions/#full-example-custom-logging-extension","title":"Full example: Custom logging extension","text":"<p>To tie it all together, here's an example of a custom logging extension that logs when components are created, deleted, or rendered:</p> <ul> <li>Each component can specify which color to use for the logging by setting <code>Component.ColorLogger.color</code>.</li> <li>The extension will log the component name and color when the component is created, deleted, or rendered.</li> </ul> <pre><code>from django_components.extension import (\n    ComponentExtension,\n    OnComponentClassCreatedContext,\n    OnComponentClassDeletedContext,\n    OnComponentInputContext,\n)\n\nclass ColorLoggerExtensionClass(ComponentExtension.ExtensionClass):\n    color: str\n\n\nclass ColorLoggerExtension(ComponentExtension):\n    name = \"color_logger\"\n\n    # All `Component.ColorLogger` classes will inherit from this class.\n    ExtensionClass = ColorLoggerExtensionClass\n\n    # These hooks don't have access to the Component instance, only to the Component class,\n    # so we access the color as `Component.ColorLogger.color`.\n    def on_component_class_created(self, ctx: OnComponentClassCreatedContext) -&gt; None:\n        log.info(\n            f\"Component {ctx.component_cls} created.\",\n            color=ctx.component_cls.ColorLogger.color,\n        )\n\n    def on_component_class_deleted(self, ctx: OnComponentClassDeletedContext) -&gt; None:\n        log.info(\n            f\"Component {ctx.component_cls} deleted.\",\n            color=ctx.component_cls.ColorLogger.color,\n        )\n\n    # This hook has access to the Component instance, so we access the color\n    # as `self.component.color_logger.color`.\n    def on_component_input(self, ctx: OnComponentInputContext) -&gt; None:\n        log.info(\n            f\"Rendering component {ctx.component_cls}.\",\n            color=ctx.component.color_logger.color,\n        )\n</code></pre> <p>To use the <code>ColorLoggerExtension</code>, add it to your settings:</p> <pre><code># settings.py\nCOMPONENTS = {\n    \"extensions\": [\n        ColorLoggerExtension,\n    ],\n}\n</code></pre> <p>Once registered, in any component, you can define a <code>ColorLogger</code> attribute:</p> <pre><code>class MyComponent(Component):\n    class ColorLogger:\n        color = \"red\"\n</code></pre> <p>This will log the component name and color when the component is created, deleted, or rendered.</p>"},{"location":"concepts/advanced/extensions/#utility-functions","title":"Utility functions","text":"<p>django-components provides a few utility functions to help with writing extensions:</p> <ul> <li><code>all_components()</code> - returns a list of all created component classes.</li> <li><code>all_registries()</code> - returns a list of all created registry instances.</li> </ul>"},{"location":"concepts/advanced/extensions/#accessing-the-component-class-from-within-an-extension","title":"Accessing the component class from within an extension","text":"<p>When you are writing the extension class that will be nested inside a Component class, e.g.</p> <pre><code>class MyTable(Component):\n    class MyExtension:\n        def some_method(self):\n            ...\n</code></pre> <p>You can access the owner Component class (<code>MyTable</code>) from within methods of the extension class (<code>MyExtension</code>) by using the <code>component_class</code> attribute:</p> <pre><code>class MyTable(Component):\n    class MyExtension:\n        def some_method(self):\n            print(self.component_class)\n</code></pre> <p>Here is how the <code>component_class</code> attribute may be used with our <code>ColorLogger</code> extension shown above:</p> <pre><code>class ColorLoggerExtensionClass(ComponentExtension.ExtensionClass):\n    color: str\n\n    def log(self, msg: str) -&gt; None:\n        print(f\"{self.component_class.name}: {msg}\")\n\n\nclass ColorLoggerExtension(ComponentExtension):\n    name = \"color_logger\"\n\n    # All `Component.ColorLogger` classes will inherit from this class.\n    ExtensionClass = ColorLoggerExtensionClass\n</code></pre>"},{"location":"concepts/advanced/extensions/#extension-commands","title":"Extension Commands","text":"<p>Extensions in django-components can define custom commands that can be executed via the Django management command interface. This allows for powerful automation and customization capabilities.</p> <p>For example, if you have an extension that defines a command that prints \"Hello world\", you can run the command with:</p> <pre><code>python manage.py components ext run my_ext hello\n</code></pre> <p>Where:</p> <ul> <li><code>python manage.py components</code> - is the Django entrypoint</li> <li><code>ext run</code> - is the subcommand to run extension commands</li> <li><code>my_ext</code> - is the extension name</li> <li><code>hello</code> - is the command name</li> </ul>"},{"location":"concepts/advanced/extensions/#defining-commands","title":"Defining Commands","text":"<p>To define a command, subclass from <code>ComponentCommand</code>. This subclass should define:</p> <ul> <li><code>name</code> - the command's name</li> <li><code>help</code> - the command's help text</li> <li><code>handle</code> - the logic to execute when the command is run</li> </ul> <pre><code>from django_components import ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n\n    def handle(self, *args, **kwargs):\n        print(\"Hello, world!\")\n\nclass MyExt(ComponentExtension):\n    name = \"my_ext\"\n    commands = [HelloCommand]\n</code></pre>"},{"location":"concepts/advanced/extensions/#defining-command-arguments-and-options","title":"Defining Command Arguments and Options","text":"<p>Commands can accept positional arguments and options (e.g. <code>--foo</code>), which are defined using the <code>arguments</code> attribute of the <code>ComponentCommand</code> class.</p> <p>The arguments are parsed with <code>argparse</code> into a dictionary of arguments and options. These are then available as keyword arguments to the <code>handle</code> method of the command.</p> <pre><code>from django_components import CommandArg, ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n\n    arguments = [\n        # Positional argument\n        CommandArg(\n            name_or_flags=\"name\",\n            help=\"The name to say hello to\",\n        ),\n        # Optional argument\n        CommandArg(\n            name_or_flags=[\"--shout\", \"-s\"],\n            action=\"store_true\",\n            help=\"Shout the hello\",\n        ),\n    ]\n\n    def handle(self, name: str, *args, **kwargs):\n        shout = kwargs.get(\"shout\", False)\n        msg = f\"Hello, {name}!\"\n        if shout:\n            msg = msg.upper()\n        print(msg)\n</code></pre> <p>You can run the command with arguments and options:</p> <pre><code>python manage.py components ext run my_ext hello John --shout\n&gt;&gt;&gt; HELLO, JOHN!\n</code></pre> <p>Note</p> <p>Command definitions are parsed with <code>argparse</code>, so you can use all the features of <code>argparse</code> to define your arguments and options.</p> <p>See the argparse documentation for more information.</p> <p>django-components defines types as <code>CommandArg</code>, <code>CommandArgGroup</code>, <code>CommandSubcommand</code>, and <code>CommandParserInput</code> to help with type checking.</p> <p>Note</p> <p>If a command doesn't have the <code>handle</code> method defined, the command will print a help message and exit.</p>"},{"location":"concepts/advanced/extensions/#grouping-arguments","title":"Grouping Arguments","text":"<p>Arguments can be grouped using <code>CommandArgGroup</code> to provide better organization and help messages.</p> <p>Read more on argparse argument groups.</p> <pre><code>from django_components import CommandArg, CommandArgGroup, ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n\n    # Argument parsing is managed by `argparse`.\n    arguments = [\n        # Positional argument\n        CommandArg(\n            name_or_flags=\"name\",\n            help=\"The name to say hello to\",\n        ),\n        # Optional argument\n        CommandArg(\n            name_or_flags=[\"--shout\", \"-s\"],\n            action=\"store_true\",\n            help=\"Shout the hello\",\n        ),\n        # When printing the command help message, `--bar` and `--baz`\n        # will be grouped under \"group bar\".\n        CommandArgGroup(\n            title=\"group bar\",\n            description=\"Group description.\",\n            arguments=[\n                CommandArg(\n                    name_or_flags=\"--bar\",\n                    help=\"Bar description.\",\n                ),\n                CommandArg(\n                    name_or_flags=\"--baz\",\n                    help=\"Baz description.\",\n                ),\n            ],\n        ),\n    ]\n\n    def handle(self, name: str, *args, **kwargs):\n        shout = kwargs.get(\"shout\", False)\n        msg = f\"Hello, {name}!\"\n        if shout:\n            msg = msg.upper()\n        print(msg)\n</code></pre>"},{"location":"concepts/advanced/extensions/#subcommands","title":"Subcommands","text":"<p>Extensions can define subcommands, allowing for more complex command structures.</p> <p>Subcommands are defined similarly to root commands, as subclasses of <code>ComponentCommand</code> class.</p> <p>However, instead of defining the subcommands in the <code>commands</code> attribute of the extension, you define them in the <code>subcommands</code> attribute of the parent command:</p> <pre><code>from django_components import CommandArg, CommandArgGroup, ComponentCommand, ComponentExtension\n\nclass ChildCommand(ComponentCommand):\n    name = \"child\"\n    help = \"Child command\"\n\n    def handle(self, *args, **kwargs):\n        print(\"Child command\")\n\nclass ParentCommand(ComponentCommand):\n    name = \"parent\"\n    help = \"Parent command\"\n    subcommands = [\n        ChildCommand,\n    ]\n\n    def handle(self, *args, **kwargs):\n        print(\"Parent command\")\n</code></pre> <p>In this example, we can run two commands.</p> <p>Either the parent command:</p> <pre><code>python manage.py components ext run parent\n&gt;&gt;&gt; Parent command\n</code></pre> <p>Or the child command:</p> <pre><code>python manage.py components ext run parent child\n&gt;&gt;&gt; Child command\n</code></pre> <p>Warning</p> <p>Subcommands are independent of the parent command. When a subcommand runs, the parent command is NOT executed.</p> <p>As such, if you want to pass arguments to both the parent and child commands, e.g.:</p> <pre><code>python manage.py components ext run parent --foo child --bar\n</code></pre> <p>You should instead pass all the arguments to the subcommand:</p> <pre><code>python manage.py components ext run parent child --foo --bar\n</code></pre>"},{"location":"concepts/advanced/extensions/#print-command-help","title":"Print command help","text":"<p>By default, all commands will print their help message when run with the <code>--help</code> / <code>-h</code> flag.</p> <pre><code>python manage.py components ext run my_ext --help\n</code></pre> <p>The help message prints out all the arguments and options available for the command, as well as any subcommands.</p>"},{"location":"concepts/advanced/extensions/#testing-commands","title":"Testing Commands","text":"<p>Commands can be tested using Django's <code>call_command()</code> function, which allows you to simulate running the command in tests.</p> <pre><code>from django.core.management import call_command\n\ncall_command('components', 'ext', 'run', 'my_ext', 'hello', '--name', 'John')\n</code></pre> <p>To capture the output of the command, you can use the <code>StringIO</code> module to redirect the output to a string:</p> <pre><code>from io import StringIO\n\nout = StringIO()\nwith patch(\"sys.stdout\", new=out):\n    call_command('components', 'ext', 'run', 'my_ext', 'hello', '--name', 'John')\noutput = out.getvalue()\n</code></pre> <p>And to temporarily set the extensions, you can use the <code>@djc_test</code> decorator.</p> <p>Thus, a full test example can then look like this:</p> <pre><code>from io import StringIO\nfrom unittest.mock import patch\n\nfrom django.core.management import call_command\nfrom django_components.testing import djc_test\n\n@djc_test(\n    components_settings={\n        \"extensions\": [\n            \"my_app.extensions.MyExtension\",\n        ],\n    },\n)\ndef test_hello_command(self):\n    out = StringIO()\n    with patch(\"sys.stdout\", new=out):\n        call_command('components', 'ext', 'run', 'my_ext', 'hello', '--name', 'John')\n    output = out.getvalue()\n    assert output == \"Hello, John!\\n\"\n</code></pre>"},{"location":"concepts/advanced/extensions/#extension-urls","title":"Extension URLs","text":"<p>Extensions can define custom views and endpoints that can be accessed through the Django application.</p> <p>To define URLs for an extension, set them in the <code>urls</code> attribute of your <code>ComponentExtension</code> class. Each URL is defined using the <code>URLRoute</code> class, which specifies the path, handler, and optional name for the route.</p> <p>Here's an example of how to define URLs within an extension:</p> <pre><code>from django_components.extension import ComponentExtension, URLRoute\nfrom django.http import HttpResponse\n\ndef my_view(request):\n    return HttpResponse(\"Hello from my extension!\")\n\nclass MyExtension(ComponentExtension):\n    name = \"my_extension\"\n\n    urls = [\n        URLRoute(path=\"my-view/\", handler=my_view, name=\"my_view\"),\n        URLRoute(path=\"another-view/&lt;int:id&gt;/\", handler=my_view, name=\"another_view\"),\n    ]\n</code></pre> <p>Warning</p> <p>The <code>URLRoute</code> objects are different from objects created with Django's <code>django.urls.path()</code>. Do NOT use <code>URLRoute</code> objects in Django's <code>urlpatterns</code> and vice versa!</p> <p>django-components uses a custom <code>URLRoute</code> class to define framework-agnostic routing rules.</p> <p>As of v0.131, <code>URLRoute</code> objects are directly converted to Django's <code>URLPattern</code> and <code>URLResolver</code> objects.</p>"},{"location":"concepts/advanced/extensions/#accessing-extension-urls","title":"Accessing Extension URLs","text":"<p>The URLs defined in an extension are available under the path</p> <pre><code>/components/ext/&lt;extension_name&gt;/\n</code></pre> <p>For example, if you have defined a URL with the path <code>my-view/&lt;str:name&gt;/</code> in an extension named <code>my_extension</code>, it can be accessed at:</p> <pre><code>/components/ext/my_extension/my-view/john/\n</code></pre>"},{"location":"concepts/advanced/extensions/#nested-urls","title":"Nested URLs","text":"<p>Extensions can also define nested URLs to allow for more complex routing structures.</p> <p>To define nested URLs, set the <code>children</code> attribute of the <code>URLRoute</code> object to a list of child <code>URLRoute</code> objects:</p> <pre><code>class MyExtension(ComponentExtension):\n    name = \"my_extension\"\n\n    urls = [\n        URLRoute(\n            path=\"parent/\",\n            name=\"parent_view\",\n            children=[\n                URLRoute(path=\"child/&lt;str:name&gt;/\", handler=my_view, name=\"child_view\"),\n            ],\n        ),\n    ]\n</code></pre> <p>In this example, the URL</p> <pre><code>/components/ext/my_extension/parent/child/john/\n</code></pre> <p>would call the <code>my_view</code> handler with the parameter <code>name</code> set to <code>\"John\"</code>.</p>"},{"location":"concepts/advanced/extensions/#passing-kwargs-and-other-extra-fields-to-url-routes","title":"Passing kwargs and other extra fields to URL routes","text":"<p>The <code>URLRoute</code> class is framework-agnostic, so that extensions could be used with non-Django frameworks in the future.</p> <p>However, that means that there may be some extra fields that Django's <code>django.urls.path()</code> accepts, but which are not defined on the <code>URLRoute</code> object.</p> <p>To address this, the <code>URLRoute</code> object has an <code>extra</code> attribute, which is a dictionary that can be used to pass any extra kwargs to <code>django.urls.path()</code>:</p> <pre><code>URLRoute(\n    path=\"my-view/&lt;str:name&gt;/\",\n    handler=my_view,\n    name=\"my_view\",\n    extra={\"kwargs\": {\"foo\": \"bar\"} },\n)\n</code></pre> <p>Is the same as:</p> <pre><code>django.urls.path(\n    \"my-view/&lt;str:name&gt;/\",\n    view=my_view,\n    name=\"my_view\",\n    kwargs={\"foo\": \"bar\"},\n)\n</code></pre> <p>because <code>URLRoute</code> is converted to Django's route like so:</p> <pre><code>django.urls.path(\n    route.path,\n    view=route.handler,\n    name=route.name,\n    **route.extra,\n)\n</code></pre>"},{"location":"concepts/advanced/hooks/","title":"Lifecycle hooks","text":"<p>New in version 0.96</p> <p>Component hooks are functions that allow you to intercept the rendering process at specific positions.</p>"},{"location":"concepts/advanced/hooks/#available-hooks","title":"Available hooks","text":"<ul> <li><code>on_render_before</code></li> </ul> <pre><code>def on_render_before(\n    self: Component,\n    context: Context,\n    template: Template\n) -&gt; None:\n</code></pre> <p>Hook that runs just before the component's template is rendered.</p> <p>You can use this hook to access or modify the context or the template:</p> <pre><code>def on_render_before(self, context, template) -&gt; None:\n    # Insert value into the Context\n    context[\"from_on_before\"] = \":)\"\n\n    # Append text into the Template\n    template.nodelist.append(TextNode(\"FROM_ON_BEFORE\"))\n</code></pre> <ul> <li><code>on_render_after</code></li> </ul> <pre><code>def on_render_after(\n    self: Component,\n    context: Context,\n    template: Template,\n    content: str\n) -&gt; None | str | SafeString:\n</code></pre> <p>Hook that runs just after the component's template was rendered.   It receives the rendered output as the last argument.</p> <p>You can use this hook to access the context or the template, but modifying   them won't have any effect.</p> <p>To override the content that gets rendered, you can return a string or SafeString from this hook:</p> <pre><code>def on_render_after(self, context, template, content):\n    # Prepend text to the rendered content\n    return \"Chocolate cookie recipe: \" + content\n</code></pre>"},{"location":"concepts/advanced/hooks/#component-hooks-example","title":"Component hooks example","text":"<p>You can use hooks together with provide / inject to create components that accept a list of items via a slot.</p> <p>In the example below, each <code>tab_item</code> component will be rendered on a separate tab page, but they are all defined in the default slot of the <code>tabs</code> component.</p> <p>See here for how it was done</p> <pre><code>{% component \"tabs\" %}\n  {% component \"tab_item\" header=\"Tab 1\" %}\n    &lt;p&gt;\n      hello from tab 1\n    &lt;/p&gt;\n    {% component \"button\" %}\n      Click me!\n    {% endcomponent %}\n  {% endcomponent %}\n\n  {% component \"tab_item\" header=\"Tab 2\" %}\n    Hello this is tab 2\n  {% endcomponent %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/advanced/html_fragments/","title":"HTML fragments","text":"<p>Django-components provides a seamless integration with HTML fragments (HTML over the wire), whether you're using HTMX, AlpineJS, or vanilla JavaScript.</p> <p>When you define a component that has extra JS or CSS, and you use django-components to render the fragment, django-components will:</p> <ul> <li>Automatically load the associated JS and CSS</li> <li>Ensure that JS is loaded and executed only once even if the fragment is inserted multiple times</li> </ul> <p>Info</p> <p>What are HTML fragments and \"HTML over the wire\"?</p> <p>It is one of the methods for updating the state in the browser UI upon user interaction.</p> <p>How it works is that:</p> <ol> <li>User makes an action - clicks a button or submits a form</li> <li>The action causes a request to be made from the client to the server.</li> <li>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).</li> <li>A library like HTMX, AlpineJS, or custom function inserts the new HTML into    the correct place.</li> </ol>"},{"location":"concepts/advanced/html_fragments/#document-and-fragment-types","title":"Document and fragment types","text":"<p>Components support two modes of rendering - As a \"document\" or as a \"fragment\".</p> <p>What's the difference?</p>"},{"location":"concepts/advanced/html_fragments/#document-mode","title":"Document mode","text":"<p>Document mode assumes that the rendered components will be embedded into the HTML of the initial page load. This means that:</p> <ul> <li>The JS and CSS is embedded into the HTML as <code>&lt;script&gt;</code> and <code>&lt;style&gt;</code> tags   (see JS and CSS output locations)</li> <li>Django-components injects a JS script for managing JS and CSS assets</li> </ul> <p>A component is rendered as a \"document\" when:</p> <ul> <li>It is embedded inside a template as <code>{% component %}</code></li> <li>It is rendered with <code>Component.render()</code> or <code>Component.render_to_response()</code>   with the <code>type</code> kwarg set to <code>\"document\"</code> (default)</li> </ul> <p>Example:</p> <pre><code>MyTable.render(\n    kwargs={...},\n)\n\n# or\n\nMyTable.render(\n    kwargs={...},\n    type=\"document\",\n)\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#fragment-mode","title":"Fragment mode","text":"<p>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:</p> <ul> <li>JS and CSS is not directly embedded to avoid duplicately executing the same JS scripts.   So template tags like <code>{% component_js_dependencies %}</code>   inside of fragments are ignored.</li> <li>Instead, django-components appends the fragment's content with a JSON <code>&lt;script&gt;</code> to trigger a call   to its asset manager JS script, which will load the JS and CSS smartly.</li> <li>The asset manager JS script is assumed to be already loaded on the page.</li> </ul> <p>A component is rendered as \"fragment\" when:</p> <ul> <li>It is rendered with <code>Component.render()</code>   or <code>Component.render_to_response()</code>   with the <code>type</code> kwarg set to <code>\"fragment\"</code></li> </ul> <p>Example:</p> <pre><code>MyTable.render(\n    kwargs={...},\n    type=\"fragment\",\n)\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#live-examples","title":"Live examples","text":"<p>For live interactive examples, start our demo project (<code>sampleproject</code>).</p> <p>Then navigate to these URLs:</p> <ul> <li><code>/fragment/base/alpine</code></li> <li><code>/fragment/base/htmx</code></li> <li><code>/fragment/base/js</code></li> </ul>"},{"location":"concepts/advanced/html_fragments/#example-htmx","title":"Example - HTMX","text":""},{"location":"concepts/advanced/html_fragments/#1-define-document-html","title":"1. Define document HTML","text":"[root]/components/demo.py<pre><code>from django_components import Component, types\n\n# HTML into which a fragment will be loaded using HTMX\nclass MyPage(Component):\n    def get(self, request):\n        return self.render_to_response()\n\n    template = \"\"\"\n        {% load component_tags %}\n        &lt;!DOCTYPE html&gt;\n        &lt;html&gt;\n            &lt;head&gt;\n                {% component_css_dependencies %}\n                &lt;script src=\"https://unpkg.com/htmx.org@1.9.12\"&gt;&lt;/script&gt;\n            &lt;/head&gt;\n            &lt;body&gt;\n                &lt;div id=\"target\"&gt;OLD&lt;/div&gt;\n\n                &lt;button\n                    hx-get=\"/mypage/frag\"\n                    hx-swap=\"outerHTML\"\n                    hx-target=\"#target\"\n                &gt;\n                  Click me!\n                &lt;/button&gt;\n\n                {% component_js_dependencies %}\n            &lt;/body&gt;\n        &lt;/html&gt;\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#2-define-fragment-html","title":"2. Define fragment HTML","text":"[root]/components/demo.py<pre><code>class Frag(Component):\n    def get(self, request):\n        return self.render_to_response(\n            # IMPORTANT: Don't forget `type=\"fragment\"`\n            type=\"fragment\",\n        )\n\n    template = \"\"\"\n        &lt;div class=\"frag\"&gt;\n            123\n            &lt;span id=\"frag-text\"&gt;&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    js = \"\"\"\n        document.querySelector('#frag-text').textContent = 'xxx';\n    \"\"\"\n\n    css = \"\"\"\n        .frag {\n            background: blue;\n        }\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#3-create-view-and-urls","title":"3. Create view and URLs","text":"[app]/urls.py<pre><code>from django.urls import path\n\nfrom components.demo import MyPage, Frag\n\nurlpatterns = [\n    path(\"mypage/\", MyPage.as_view())\n    path(\"mypage/frag\", Frag.as_view()),\n]\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#example-alpinejs","title":"Example - AlpineJS","text":""},{"location":"concepts/advanced/html_fragments/#1-define-document-html_1","title":"1. Define document HTML","text":"[root]/components/demo.py<pre><code>from django_components import Component, types\n\n# HTML into which a fragment will be loaded using AlpineJS\nclass MyPage(Component):\n    def get(self, request):\n        return self.render_to_response()\n\n    template = \"\"\"\n        {% load component_tags %}\n        &lt;!DOCTYPE html&gt;\n        &lt;html&gt;\n            &lt;head&gt;\n                {% component_css_dependencies %}\n                &lt;script defer src=\"https://unpkg.com/alpinejs\"&gt;&lt;/script&gt;\n            &lt;/head&gt;\n            &lt;body x-data=\"{\n                htmlVar: 'OLD',\n                loadFragment: function () {\n                    const url = '/mypage/frag';\n                    fetch(url)\n                        .then(response =&gt; response.text())\n                        .then(html =&gt; {\n                            this.htmlVar = html;\n                        });\n                }\n            }\"&gt;\n                &lt;div id=\"target\" x-html=\"htmlVar\"&gt;OLD&lt;/div&gt;\n\n                &lt;button @click=\"loadFragment\"&gt;\n                  Click me!\n                &lt;/button&gt;\n\n                {% component_js_dependencies %}\n            &lt;/body&gt;\n        &lt;/html&gt;\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#2-define-fragment-html_1","title":"2. Define fragment HTML","text":"[root]/components/demo.py<pre><code>class Frag(Component):\n    def get(self, request):\n        # IMPORTANT: Don't forget `type=\"fragment\"`\n        return self.render_to_response(\n            type=\"fragment\",\n        )\n\n    # NOTE: We wrap the actual fragment in a template tag with x-if=\"false\" to prevent it\n    #       from being rendered until we have registered the component with AlpineJS.\n    template = \"\"\"\n        &lt;template x-if=\"false\" data-name=\"frag\"&gt;\n            &lt;div class=\"frag\"&gt;\n                123\n                &lt;span x-data=\"frag\" x-text=\"fragVal\"&gt;\n                &lt;/span&gt;\n            &lt;/div&gt;\n        &lt;/template&gt;\n    \"\"\"\n\n    js = \"\"\"\n        Alpine.data('frag', () =&gt; ({\n            fragVal: 'xxx',\n        }));\n\n        // Now that the component has been defined in AlpineJS, we can \"activate\"\n        // all instances where we use the `x-data=\"frag\"` directive.\n        document.querySelectorAll('[data-name=\"frag\"]').forEach((el) =&gt; {\n            el.setAttribute('x-if', 'true');\n        });\n    \"\"\"\n\n    css = \"\"\"\n        .frag {\n            background: blue;\n        }\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#3-create-view-and-urls_1","title":"3. Create view and URLs","text":"[app]/urls.py<pre><code>from django.urls import path\n\nfrom components.demo import MyPage, Frag\n\nurlpatterns = [\n    path(\"mypage/\", MyPage.as_view())\n    path(\"mypage/frag\", Frag.as_view()),\n]\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#example-vanilla-js","title":"Example - Vanilla JS","text":""},{"location":"concepts/advanced/html_fragments/#1-define-document-html_2","title":"1. Define document HTML","text":"[root]/components/demo.py<pre><code>from django_components import Component, types\n\n# HTML into which a fragment will be loaded using JS\nclass MyPage(Component):\n    def get(self, request):\n        return self.render_to_response()\n\n    template = \"\"\"\n        {% load component_tags %}\n        &lt;!DOCTYPE html&gt;\n        &lt;html&gt;\n            &lt;head&gt;\n                {% component_css_dependencies %}\n            &lt;/head&gt;\n            &lt;body&gt;\n                &lt;div id=\"target\"&gt;OLD&lt;/div&gt;\n\n                &lt;button&gt;\n                  Click me!\n                &lt;/button&gt;\n                &lt;script&gt;\n                    const url = `/mypage/frag`;\n                    document.querySelector('#loader').addEventListener('click', function () {\n                        fetch(url)\n                            .then(response =&gt; response.text())\n                            .then(html =&gt; {\n                                document.querySelector('#target').outerHTML = html;\n                            });\n                    });\n                &lt;/script&gt;\n\n                {% component_js_dependencies %}\n            &lt;/body&gt;\n        &lt;/html&gt;\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#2-define-fragment-html_2","title":"2. Define fragment HTML","text":"[root]/components/demo.py<pre><code>class Frag(Component):\n    def get(self, request):\n        return self.render_to_response(\n            # IMPORTANT: Don't forget `type=\"fragment\"`\n            type=\"fragment\",\n        )\n\n    template = \"\"\"\n        &lt;div class=\"frag\"&gt;\n            123\n            &lt;span id=\"frag-text\"&gt;&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    js = \"\"\"\n        document.querySelector('#frag-text').textContent = 'xxx';\n    \"\"\"\n\n    css = \"\"\"\n        .frag {\n            background: blue;\n        }\n    \"\"\"\n</code></pre>"},{"location":"concepts/advanced/html_fragments/#3-create-view-and-urls_2","title":"3. Create view and URLs","text":"[app]/urls.py<pre><code>from django.urls import path\n\nfrom components.demo import MyPage, Frag\n\nurlpatterns = [\n    path(\"mypage/\", MyPage.as_view())\n    path(\"mypage/frag\", Frag.as_view()),\n]\n</code></pre>"},{"location":"concepts/advanced/provide_inject/","title":"Prop drilling and provide / inject","text":"<p>New in version 0.80:</p> <p>Django components supports the provide / inject or ContextProvider pattern with the combination of:</p> <ol> <li><code>{% provide %}</code> tag</li> <li><code>inject()</code> method of the <code>Component</code> class</li> </ol>"},{"location":"concepts/advanced/provide_inject/#what-is-prop-drilling","title":"What is \"prop drilling\"?","text":"<p>Prop drilling refers to a scenario in UI development where you need to pass data through many layers of a component tree to reach the nested components that actually need the data.</p> <p>Normally, you'd use props to send data from a parent component to its children. However, this straightforward method becomes cumbersome and inefficient if the data has to travel through many levels or if several components scattered at different depths all need the same piece of information.</p> <p>This results in a situation where the intermediate components, which don't need the data for their own functioning, end up having to manage and pass along these props. This clutters the component tree and makes the code verbose and harder to manage.</p> <p>A neat solution to avoid prop drilling is using the \"provide and inject\" technique.</p> <p>With provide / inject, a parent component acts like a data hub for all its descendants. This setup allows any component, no matter how deeply nested it is, to access the required data directly from this centralized provider without having to messily pass props down the chain. This approach significantly cleans up the code and makes it easier to maintain.</p> <p>This feature is inspired by Vue's Provide / Inject and React's Context / useContext.</p>"},{"location":"concepts/advanced/provide_inject/#how-to-use-provide-inject","title":"How to use provide / inject","text":"<p>As the name suggest, using provide / inject consists of 2 steps</p> <ol> <li>Providing data</li> <li>Injecting provided data</li> </ol> <p>For examples of advanced uses of provide / inject, see this discussion.</p>"},{"location":"concepts/advanced/provide_inject/#using-provide-tag","title":"Using <code>{% provide %}</code> tag","text":"<p>First we use the <code>{% provide %}</code> tag to define the data we want to \"provide\" (make available).</p> <pre><code>{% provide \"my_data\" key=\"hi\" another=123 %}\n    {% component \"child\" / %}  &lt;--- Can access \"my_data\"\n{% endprovide %}\n\n{% component \"child\" / %}  &lt;--- Cannot access \"my_data\"\n</code></pre> <p>Notice that the <code>provide</code> tag REQUIRES a name as a first argument. This is the key by which we can then access the data passed to this tag.</p> <p><code>provide</code> tag name must resolve to a valid identifier (AKA a valid Python variable name).</p> <p>Once you've set the name, you define the data you want to \"provide\" by passing it as keyword arguments. This is similar to how you pass data to the <code>{% with %}</code> tag.</p> <p>NOTE: Kwargs passed to <code>{% provide %}</code> are NOT added to the context. In the example below, the <code>{{ key }}</code> won't render anything:</p> <pre><code>{% provide \"my_data\" key=\"hi\" another=123 %}\n    {{ key }}\n{% endprovide %}\n</code></pre> <p>Similarly to slots and fills, also provide's name argument can be set dynamically via a variable, a template expression, or a spread operator:</p> <pre><code>{% provide name=name ... %}\n    ...\n{% provide %}\n&lt;/table&gt;\n</code></pre>"},{"location":"concepts/advanced/provide_inject/#using-inject-method","title":"Using <code>inject()</code> method","text":"<p>To \"inject\" (access) the data defined on the <code>provide</code> tag, you can use the <code>inject()</code> method inside of <code>get_context_data()</code>.</p> <p>For a component to be able to \"inject\" some data, the component (<code>{% component %}</code> tag) must be nested inside the <code>{% provide %}</code> tag.</p> <p>In the example from previous section, we've defined two kwargs: <code>key=\"hi\" another=123</code>. That means that if we now inject <code>\"my_data\"</code>, we get an object with 2 attributes - <code>key</code> and <code>another</code>.</p> <pre><code>class ChildComponent(Component):\n    def get_context_data(self):\n        my_data = self.inject(\"my_data\")\n        print(my_data.key)     # hi\n        print(my_data.another) # 123\n        return {}\n</code></pre> <p>First argument to <code>inject</code> is the key (or name) of the provided data. This must match the string that you used in the <code>provide</code> tag. If no provider with given key is found, <code>inject</code> raises a <code>KeyError</code>.</p> <p>To avoid the error, you can pass a second argument to <code>inject</code> to which will act as a default value, similar to <code>dict.get(key, default)</code>:</p> <pre><code>class ChildComponent(Component):\n    def get_context_data(self):\n        my_data = self.inject(\"invalid_key\", DEFAULT_DATA)\n        assert my_data == DEFAUKT_DATA\n        return {}\n</code></pre> <p>The instance returned from <code>inject()</code> is a subclass of <code>NamedTuple</code>, so the instance is immutable. This ensures that the data returned from <code>inject</code> will always have all the keys that were passed to the <code>provide</code> tag.</p> <p>NOTE: <code>inject()</code> works strictly only in <code>get_context_data</code>. If you try to call it from elsewhere, it will raise an error.</p>"},{"location":"concepts/advanced/provide_inject/#full-example","title":"Full example","text":"<pre><code>@register(\"child\")\nclass ChildComponent(Component):\n    template = \"\"\"\n        &lt;div&gt; {{ my_data.key }} &lt;/div&gt;\n        &lt;div&gt; {{ my_data.another }} &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self):\n        my_data = self.inject(\"my_data\", \"default\")\n        return {\"my_data\": my_data}\n\ntemplate_str = \"\"\"\n    {% load component_tags %}\n    {% provide \"my_data\" key=\"hi\" another=123 %}\n        {% component \"child\" / %}\n    {% endprovide %}\n\"\"\"\n</code></pre> <p>renders:</p> <pre><code>&lt;div&gt;hi&lt;/div&gt;\n&lt;div&gt;123&lt;/div&gt;\n</code></pre>"},{"location":"concepts/advanced/rendering_js_css/","title":"Rendering JS / CSS","text":""},{"location":"concepts/advanced/rendering_js_css/#js-and-css-output-locations","title":"JS and CSS output locations","text":"<p>If:</p> <ol> <li>Your components use JS and CSS via any of:<ul> <li><code>Component.css</code></li> <li><code>Component.js</code></li> <li><code>Component.Media.css</code></li> <li><code>Component.Media.js</code></li> </ul> </li> <li>And you use the <code>ComponentDependencyMiddleware</code> middleware</li> </ol> <p>Then, by default, the components' JS and CSS will be automatically inserted into the HTML:</p> <ul> <li>CSS styles will be inserted at the end of the <code>&lt;head&gt;</code></li> <li>JS scripts will be inserted at the end of the <code>&lt;body&gt;</code></li> </ul> <p>If you want to place the dependencies elsewhere in the HTML, you can override the locations by inserting following Django template tags:</p> <ul> <li><code>{% component_js_dependencies %}</code> - Set new location(s) for JS scripts</li> <li><code>{% component_css_dependencies %}</code> - Set new location(s) for CSS styles</li> </ul> <p>So if you have a component with JS and CSS:</p> <pre><code>from django_components import Component, types\n\nclass MyButton(Component):\n    template: types.django_html = \"\"\"\n        &lt;button class=\"my-button\"&gt;\n            Click me!\n        &lt;/button&gt;\n    \"\"\"\n    js: types.js = \"\"\"\n        for (const btnEl of document.querySelectorAll(\".my-button\")) {\n            btnEl.addEventListener(\"click\", () =&gt; {\n                console.log(\"BUTTON CLICKED!\");\n            });\n        }\n    \"\"\"\n    css: types.css \"\"\"\n        .my-button {\n            background: green;\n        }\n    \"\"\"\n\n    class Media:\n        js = [\"/extra/script.js\"]\n        css = [\"/extra/style.css\"]\n</code></pre> <p>Then the JS from <code>MyButton.js</code> and <code>MyButton.Media.js</code> will be rendered at the default place, or in <code>{% component_js_dependencies %}</code>.</p> <p>And the CSS from <code>MyButton.css</code> and <code>MyButton.Media.css</code> will be rendered at the default place, or in <code>{% component_css_dependencies %}</code>.</p> <p>And if you don't specify <code>{% component_dependencies %}</code> tags, it is the equivalent of:</p> <pre><code>&lt;!doctype html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    &lt;title&gt;MyPage&lt;/title&gt;\n    ...\n    {% component_css_dependencies %}\n  &lt;/head&gt;\n  &lt;body&gt;\n    &lt;main&gt;\n      ...\n    &lt;/main&gt;\n    {% component_js_dependencies %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre>"},{"location":"concepts/advanced/rendering_js_css/#setting-up-the-middleware","title":"Setting up the middleware","text":"<p><code>ComponentDependencyMiddleware</code> is a Django middleware designed to manage and inject CSS / JS dependencies of rendered components dynamically. It ensures that only the necessary stylesheets and scripts are loaded in your HTML responses, based on the components used in your Django templates.</p> <p>To set it up, add the middleware to your <code>MIDDLEWARE</code> in <code>settings.py</code>:</p> <pre><code>MIDDLEWARE = [\n    # ... other middleware classes ...\n    'django_components.middleware.ComponentDependencyMiddleware'\n    # ... other middleware classes ...\n]\n</code></pre>"},{"location":"concepts/advanced/rendering_js_css/#render_dependencies-and-rendering-js-css-without-the-middleware","title":"<code>render_dependencies</code> and rendering JS / CSS without the middleware","text":"<p>For most scenarios, using the <code>ComponentDependencyMiddleware</code> middleware will be just fine.</p> <p>However, this section is for you if you want to:</p> <ul> <li>Render HTML that will NOT be sent as a server response</li> <li>Insert pre-rendered HTML into another component</li> <li>Render HTML fragments (partials)</li> </ul> <p>Every time there is an HTML string that has parts which were rendered using components, and any of those components has JS / CSS, then this HTML string MUST be processed with <code>render_dependencies()</code>.</p> <p>It is actually <code>render_dependencies()</code> that finds all used components in the HTML string, and inserts the component's JS and CSS into <code>{% component_dependencies %}</code> tags, or at the default locations.</p>"},{"location":"concepts/advanced/rendering_js_css/#render-js-css-without-the-middleware","title":"Render JS / CSS without the middleware","text":"<p>The truth is that the <code>ComponentDependencyMiddleware</code> middleware just calls <code>render_dependencies()</code>, passing in the HTML content. So if you render a template that contained <code>{% component %}</code> tags, you MUST pass the result through <code>render_dependencies()</code>. And the middleware is just one of the options.</p> <p>Here is how you can achieve the same, without the middleware, using <code>render_dependencies()</code>:</p> <pre><code>from django.template.base import Template\nfrom django.template.context import Context\nfrom django_component import render_dependencies\n\ntemplate = Template(\"\"\"\n    {% load component_tags %}\n    &lt;!doctype html&gt;\n    &lt;html&gt;\n    &lt;head&gt;\n        &lt;title&gt;MyPage&lt;/title&gt;\n    &lt;/head&gt;\n    &lt;body&gt;\n        &lt;main&gt;\n            {% component \"my_button\" %}\n                Click me!\n            {% endcomponent %}\n        &lt;/main&gt;\n    &lt;/body&gt;\n    &lt;/html&gt;\n\"\"\")\n\nrendered = template.render(Context())\nrendered = render_dependencies(rendered)\n</code></pre> <p>Same applies if you render a template using Django's <code>django.shortcuts.render</code>:</p> <pre><code>from django.shortcuts import render\n\ndef my_view(request):\n    rendered = render(request, \"pages/home.html\")\n    rendered = render_dependencies(rendered)\n    return rendered\n</code></pre> <p>Alternatively, when you render HTML with <code>Component.render()</code> or <code>Component.render_to_response()</code>, these, by default, call <code>render_dependencies()</code> for you, so you don't have to:</p> <pre><code>from django_components import Component\n\nclass MyButton(Component):\n    ...\n\n# No need to call `render_dependencies()`\nrendered = MyButton.render()\n</code></pre>"},{"location":"concepts/advanced/rendering_js_css/#inserting-pre-rendered-html-into-another-component","title":"Inserting pre-rendered HTML into another component","text":"<p>In previous section we've shown that <code>render_dependencies()</code> does NOT need to be called when you render a component via <code>Component.render()</code>.</p> <p>API of django_components makes it possible to compose components in a \"React-like\" way, where we pre-render a piece of HTML and then insert it into a larger structure.</p> <p>To do this, you must add <code>render_dependencies=False</code> to the nested components:</p> <pre><code>card_actions = CardActions.render(\n    kwargs={\"editable\": editable},\n    render_dependencies=False,\n)\n\ncard = Card.render(\n    slots={\"actions\": card_actions},\n    render_dependencies=False,\n)\n\npage = MyPage.render(\n    slots={\"card\": card},\n)\n</code></pre> <p>Why is <code>render_dependencies=False</code> required?</p> <p>This is a technical limitation of the current implementation.</p> <p>As mentioned earlier, each time we call <code>Component.render()</code>, we also call <code>render_dependencies()</code>.</p> <p>However, there is a problem here - When we call <code>render_dependencies()</code> inside <code>CardActions.render()</code>, we extract and REMOVE the info on components' JS and CSS from the HTML. But the template of <code>CardActions</code> contains no <code>{% component_depedencies %}</code> tags, and nor <code>&lt;head&gt;</code> nor <code>&lt;body&gt;</code> HTML tags. So the component's JS and CSS will NOT be inserted, and will be lost.</p> <p>To work around this, you must set <code>render_dependencies=False</code> when rendering pieces of HTML with <code>Component.render()</code> and inserting them into larger structures.</p>"},{"location":"concepts/advanced/rendering_js_css/#summary","title":"Summary","text":"<ol> <li>Every time you render HTML that contained components, you have to call <code>render_dependencies()</code>    on the rendered output.</li> <li>There are several ways to call <code>render_dependencies()</code>:<ul> <li>Using the <code>ComponentDependencyMiddleware</code> middleware</li> <li>Rendering the HTML by calling <code>Component.render()</code> with <code>render_dependencies=True</code> (default)</li> <li>Rendering the HTML by calling <code>Component.render_to_response()</code> (always renders dependencies)</li> <li>Directly passing rendered HTML to <code>render_dependencies()</code></li> </ul> </li> <li>If you pre-render one component to pass it into another, the pre-rendered component must be rendered with    <code>render_dependencies=False</code>.</li> </ol>"},{"location":"concepts/advanced/tag_formatter/","title":"Tag formatters","text":""},{"location":"concepts/advanced/tag_formatter/#customizing-component-tags-with-tagformatter","title":"Customizing component tags with TagFormatter","text":"<p>New in version 0.89</p> <p>By default, components are rendered using the pair of <code>{% component %}</code> / <code>{% endcomponent %}</code> template tags:</p> <pre><code>{% component \"button\" href=\"...\" disabled %}\nClick me!\n{% endcomponent %}\n\n{# or #}\n\n{% component \"button\" href=\"...\" disabled / %}\n</code></pre> <p>You can change this behaviour in the settings under the <code>COMPONENTS.tag_formatter</code>.</p> <p>For example, if you set the tag formatter to</p> <p><code>django_components.component_shorthand_formatter</code></p> <p>then the components' names will be used as the template tags:</p> <pre><code>{% button href=\"...\" disabled %}\n  Click me!\n{% endbutton %}\n\n{# or #}\n\n{% button href=\"...\" disabled / %}\n</code></pre>"},{"location":"concepts/advanced/tag_formatter/#available-tagformatters","title":"Available TagFormatters","text":"<p>django_components provides following predefined TagFormatters:</p> <ul> <li><code>ComponentFormatter</code> (<code>django_components.component_formatter</code>)</li> </ul> <p>Default</p> <p>Uses the <code>component</code> and <code>endcomponent</code> tags, and the component name is gives as the first positional argument.</p> <p>Example as block:</p> <pre><code>{% component \"button\" href=\"...\" %}\n    {% fill \"content\" %}\n        ...\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>Example as inlined tag:</p> <pre><code>{% component \"button\" href=\"...\" / %}\n</code></pre> <ul> <li><code>ShorthandComponentFormatter</code> (<code>django_components.component_shorthand_formatter</code>)</li> </ul> <p>Uses the component name as start tag, and <code>end&lt;component_name&gt;</code>   as an end tag.</p> <p>Example as block:</p> <pre><code>{% button href=\"...\" %}\n    Click me!\n{% endbutton %}\n</code></pre> <p>Example as inlined tag:</p> <pre><code>{% button href=\"...\" / %}\n</code></pre>"},{"location":"concepts/advanced/tag_formatter/#writing-your-own-tagformatter","title":"Writing your own TagFormatter","text":""},{"location":"concepts/advanced/tag_formatter/#background","title":"Background","text":"<p>First, let's discuss how TagFormatters work, and how components are rendered in django_components.</p> <p>When you render a component with <code>{% component %}</code> (or your own tag), the following happens:</p> <ol> <li><code>component</code> must be registered as a Django's template tag</li> <li>Django triggers django_components's tag handler for tag <code>component</code>.</li> <li>The tag handler passes the tag contents for pre-processing to <code>TagFormatter.parse()</code>.</li> </ol> <p>So if you render this:</p> <pre><code>{% component \"button\" href=\"...\" disabled %}\n{% endcomponent %}\n</code></pre> <p>Then <code>TagFormatter.parse()</code> will receive a following input:</p> <pre><code>[\"component\", '\"button\"', 'href=\"...\"', 'disabled']\n</code></pre> <ol> <li><code>TagFormatter</code> extracts the component name and the remaining input.</li> </ol> <p>So, given the above, <code>TagFormatter.parse()</code> returns the following:</p> <pre><code>TagResult(\n    component_name=\"button\",\n    tokens=['href=\"...\"', 'disabled']\n)\n</code></pre> <ol> <li>The tag handler resumes, using the tokens returned from <code>TagFormatter</code>.</li> </ol> <p>So, continuing the example, at this point the tag handler practically behaves as if you rendered:</p> <pre><code>{% component href=\"...\" disabled %}\n</code></pre> <ol> <li>Tag handler looks up the component <code>button</code>, and passes the args, kwargs, and slots to it.</li> </ol>"},{"location":"concepts/advanced/tag_formatter/#tagformatter","title":"TagFormatter","text":"<p><code>TagFormatter</code> handles following parts of the process above:</p> <ul> <li> <p>Generates start/end tags, given a component. This is what you then call from within your template as <code>{% component %}</code>.</p> </li> <li> <p>When you <code>{% component %}</code>, tag formatter pre-processes the tag contents, so it can link back the custom template tag to the right component.</p> </li> </ul> <p>To do so, subclass from <code>TagFormatterABC</code> and implement following method:</p> <ul> <li><code>start_tag</code></li> <li><code>end_tag</code></li> <li><code>parse</code></li> </ul> <p>For example, this is the implementation of <code>ShorthandComponentFormatter</code></p> <pre><code>class ShorthandComponentFormatter(TagFormatterABC):\n    # Given a component name, generate the start template tag\n    def start_tag(self, name: str) -&gt; str:\n        return name  # e.g. 'button'\n\n    # Given a component name, generate the start template tag\n    def end_tag(self, name: str) -&gt; str:\n        return f\"end{name}\"  # e.g. 'endbutton'\n\n    # Given a tag, e.g.\n    # `{% button href=\"...\" disabled %}`\n    #\n    # The parser receives:\n    # `['button', 'href=\"...\"', 'disabled']`\n    def parse(self, tokens: List[str]) -&gt; TagResult:\n        tokens = [*tokens]\n        name = tokens.pop(0)\n        return TagResult(\n            name,  # e.g. 'button'\n            tokens  # e.g. ['href=\"...\"', 'disabled']\n        )\n</code></pre> <p>That's it! And once your <code>TagFormatter</code> is ready, don't forget to update the settings!</p>"},{"location":"concepts/advanced/template_tags/","title":"Custom template tags","text":"<p>Template tags introduced by django-components, such as <code>{% component %}</code> and <code>{% slot %}</code>, offer additional features over the default Django template tags:</p> <ul> <li>Self-closing tags <code>{% mytag / %}</code></li> <li>Allowing the use of <code>:</code>, <code>-</code> (and more) in keys</li> <li>Spread operator <code>...</code></li> <li>Using template tags as inputs to other template tags</li> <li>Flat definition of dictionaries <code>attr:key=val</code></li> <li>Function-like input validation</li> </ul> <p>You too can easily create custom template tags that use the above features.</p>"},{"location":"concepts/advanced/template_tags/#defining-template-tags-with-template_tag","title":"Defining template tags with <code>@template_tag</code>","text":"<p>The simplest way to create a custom template tag is using the <code>template_tag</code> decorator. This decorator allows you to define a template tag by just writing a function that returns the rendered content.</p> <pre><code>from django.template import Context, Library\nfrom django_components import BaseNode, template_tag\n\nlibrary = Library()\n\n@template_tag(\n    library,\n    tag=\"mytag\",\n    end_tag=\"endmytag\",\n    allowed_flags=[\"required\"]\n)\ndef mytag(node: BaseNode, context: Context, name: str, **kwargs) -&gt; str:\n    return f\"Hello, {name}!\"\n</code></pre> <p>This will allow you to use the tag in your templates like this:</p> <pre><code>{% mytag name=\"John\" %}\n{% endmytag %}\n\n{# or with self-closing syntax #}\n{% mytag name=\"John\" / %}\n\n{# or with flags #}\n{% mytag name=\"John\" required %}\n{% endmytag %}\n</code></pre>"},{"location":"concepts/advanced/template_tags/#parameters","title":"Parameters","text":"<p>The <code>@template_tag</code> decorator accepts the following parameters:</p> <ul> <li><code>library</code>: The Django template library to register the tag with</li> <li><code>tag</code>: The name of the template tag (e.g. <code>\"mytag\"</code> for <code>{% mytag %}</code>)</li> <li><code>end_tag</code>: Optional. The name of the end tag (e.g. <code>\"endmytag\"</code> for <code>{% endmytag %}</code>)</li> <li><code>allowed_flags</code>: Optional. List of flags that can be used with the tag (e.g. <code>[\"required\"]</code> for <code>{% mytag required %}</code>)</li> </ul>"},{"location":"concepts/advanced/template_tags/#function-signature","title":"Function signature","text":"<p>The function decorated with <code>@template_tag</code> must accept at least two arguments:</p> <ol> <li><code>node</code>: The node instance (we'll explain this in detail in the next section)</li> <li><code>context</code>: The Django template context</li> </ol> <p>Any additional parameters in your function's signature define what inputs your template tag accepts. For example:</p> <pre><code>@template_tag(library, tag=\"greet\")\ndef greet(\n    node: BaseNode,\n    context: Context,\n    name: str,                    # required positional argument\n    count: int = 1,              # optional positional argument\n    *,                           # keyword-only arguments marker\n    msg: str,                    # required keyword argument\n    mode: str = \"default\",       # optional keyword argument\n) -&gt; str:\n    return f\"{msg}, {name}!\" * count\n</code></pre> <p>This allows the tag to be used like:</p> <pre><code>{# All parameters #}\n{% greet \"John\" count=2 msg=\"Hello\" mode=\"custom\" %}\n\n{# Only required parameters #}\n{% greet \"John\" msg=\"Hello\" %}\n\n{# Missing required parameter - will raise error #}\n{% greet \"John\" %}  {# Error: missing 'msg' #}\n</code></pre> <p>When you pass input to a template tag, it behaves the same way as if you passed the input to a function:</p> <ul> <li>If required parameters are missing, an error is raised</li> <li>If unexpected parameters are passed, an error is raised</li> </ul> <p>To accept keys that are not valid Python identifiers (e.g. <code>data-id</code>), or would conflict with Python keywords (e.g. <code>is</code>), you can use the <code>**kwargs</code> syntax:</p> <pre><code>@template_tag(library, tag=\"greet\")\ndef greet(\n    node: BaseNode,\n    context: Context,\n    **kwargs,\n) -&gt; str:\n    attrs = kwargs.copy()\n    is_var = attrs.pop(\"is\", None)\n    attrs_str = \" \".join(f'{k}=\"{v}\"' for k, v in attrs.items())\n\n    return mark_safe(f\"\"\"\n        &lt;div {attrs_str}&gt;\n            Hello, {is_var}!\n        &lt;/div&gt;\n    \"\"\")\n</code></pre> <p>This allows you to use the tag like this:</p> <pre><code>{% greet is=\"John\" data-id=\"123\" %}\n</code></pre>"},{"location":"concepts/advanced/template_tags/#defining-template-tags-with-basenode","title":"Defining template tags with <code>BaseNode</code>","text":"<p>For more control over your template tag, you can subclass <code>BaseNode</code> directly instead of using the decorator. This gives you access to additional features like the node's internal state and parsing details.</p> <pre><code>from django_components import BaseNode\n\nclass GreetNode(BaseNode):\n    tag = \"greet\"\n    end_tag = \"endgreet\"\n    allowed_flags = [\"required\"]\n\n    def render(self, context: Context, name: str, **kwargs) -&gt; str:\n        # Access node properties\n        if self.flags[\"required\"]:\n            return f\"Required greeting: Hello, {name}!\"\n        return f\"Hello, {name}!\"\n\n# Register the node\nGreetNode.register(library)\n</code></pre>"},{"location":"concepts/advanced/template_tags/#node-properties","title":"Node properties","text":"<p>When using <code>BaseNode</code>, you have access to several useful properties:</p> <ul> <li><code>node_id</code>: A unique identifier for this node instance</li> <li><code>flags</code>: Dictionary of flag values (e.g. <code>{\"required\": True}</code>)</li> <li><code>params</code>: List of raw parameters passed to the tag</li> <li><code>nodelist</code>: The template nodes between the start and end tags</li> <li><code>active_flags</code>: List of flags that are currently set to True</li> </ul> <p>This is what the <code>node</code> parameter in the <code>@template_tag</code> decorator gives you access to - it's the instance of the node class that was automatically created for your template tag.</p>"},{"location":"concepts/advanced/template_tags/#rendering-content-between-tags","title":"Rendering content between tags","text":"<p>When your tag has an end tag, you can access and render the content between the tags using <code>nodelist</code>:</p> <pre><code>class WrapNode(BaseNode):\n    tag = \"wrap\"\n    end_tag = \"endwrap\"\n\n    def render(self, context: Context, tag: str = \"div\", **attrs) -&gt; str:\n        # Render the content between tags\n        inner = self.nodelist.render(context)\n        attrs_str = \" \".join(f'{k}=\"{v}\"' for k, v in attrs.items())\n        return f\"&lt;{tag} {attrs_str}&gt;{inner}&lt;/{tag}&gt;\"\n\n# Usage:\n{% wrap tag=\"section\" class=\"content\" %}\n    Hello, world!\n{% endwrap %}\n</code></pre>"},{"location":"concepts/advanced/template_tags/#unregistering-nodes","title":"Unregistering nodes","text":"<p>You can unregister a node from a library using the <code>unregister</code> method:</p> <pre><code>GreetNode.unregister(library)\n</code></pre> <p>This is particularly useful in testing when you want to clean up after registering temporary tags.</p>"},{"location":"concepts/advanced/testing/","title":"Testing","text":"<p>New in version 0.131</p> <p>The <code>@djc_test</code> decorator is a powerful tool for testing components created with <code>django-components</code>. It ensures that each test is properly isolated, preventing components registered in one test from affecting others.</p>"},{"location":"concepts/advanced/testing/#usage","title":"Usage","text":"<p>The <code>@djc_test</code> decorator can be applied to functions, methods, or classes. When applied to a class, it recursively decorates all methods starting with <code>test_</code>, including those in nested classes. This allows for comprehensive testing of component behavior.</p>"},{"location":"concepts/advanced/testing/#applying-to-a-function","title":"Applying to a Function","text":"<p>To apply <code>djc_test</code> to a function, simply decorate the function as shown below:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\n@djc_test\ndef test_my_component():\n    @register(\"my_component\")\n    class MyComponent(Component):\n        template = \"...\"\n    ...\n</code></pre>"},{"location":"concepts/advanced/testing/#applying-to-a-class","title":"Applying to a Class","text":"<p>When applied to a class, <code>djc_test</code> decorates each <code>test_</code> method individually:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\n@djc_test\nclass TestMyComponent:\n    def test_something(self):\n        ...\n\n    class Nested:\n        def test_something_else(self):\n            ...\n</code></pre> <p>This is equivalent to applying the decorator to each method individually:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\nclass TestMyComponent:\n    @djc_test\n    def test_something(self):\n        ...\n\n    class Nested:\n        @djc_test\n        def test_something_else(self):\n            ...\n</code></pre>"},{"location":"concepts/advanced/testing/#arguments","title":"Arguments","text":"<p>See the API reference for <code>@djc_test</code> for more details.</p>"},{"location":"concepts/advanced/testing/#setting-up-django","title":"Setting Up Django","text":"<p>Before using <code>djc_test</code>, ensure Django is set up:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\n@djc_test\ndef test_my_component():\n    ...\n</code></pre>"},{"location":"concepts/advanced/testing/#example-parametrizing-context-behavior","title":"Example: Parametrizing Context Behavior","text":"<p>You can parametrize the context behavior using <code>djc_test</code>:</p> <pre><code>from django_components.testing import djc_test\n\n@djc_test(\n    # Settings applied to all cases\n    components_settings={\n        \"app_dirs\": [\"custom_dir\"],\n    },\n    # Parametrized settings\n    parametrize=(\n        [\"components_settings\"],\n        [\n            [{\"context_behavior\": \"django\"}],\n            [{\"context_behavior\": \"isolated\"}],\n        ],\n        [\"django\", \"isolated\"],\n    )\n)\ndef test_context_behavior(components_settings):\n    rendered = MyComponent().render()\n    ...\n</code></pre>"},{"location":"concepts/advanced/typing_and_validation/","title":"Typing and validation","text":""},{"location":"concepts/advanced/typing_and_validation/#adding-type-hints-with-generics","title":"Adding type hints with Generics","text":"<p>New in version 0.92</p> <p>The <code>Component</code> class optionally accepts type parameters that allow you to specify the types of args, kwargs, slots, and data:</p> <pre><code>class Button(Component[Args, Kwargs, Slots, Data, JsData, CssData]):\n    ...\n</code></pre> <ul> <li><code>Args</code> - Must be a <code>Tuple</code> or <code>Any</code></li> <li><code>Kwargs</code> - Must be a <code>TypedDict</code> or <code>Any</code></li> <li><code>Data</code> - Must be a <code>TypedDict</code> or <code>Any</code></li> <li><code>Slots</code> - Must be a <code>TypedDict</code> or <code>Any</code></li> </ul> <p>Here's a full example:</p> <pre><code>from typing import NotRequired, Tuple, TypedDict, SlotContent, SlotFunc\n\n# Positional inputs\nArgs = Tuple[int, str]\n\n# Kwargs inputs\nclass Kwargs(TypedDict):\n    variable: str\n    another: int\n    maybe_var: NotRequired[int] # May be ommited\n\n# Data returned from `get_context_data`\nclass Data(TypedDict):\n    variable: str\n\n# The data available to the `my_slot` scoped slot\nclass MySlotData(TypedDict):\n    value: int\n\n# Slots\nclass Slots(TypedDict):\n    # Use SlotFunc for slot functions.\n    # The generic specifies the `data` dictionary\n    my_slot: NotRequired[SlotFunc[MySlotData]]\n    # SlotContent == Union[str, SafeString]\n    another_slot: SlotContent\n\nclass Button(Component[Args, Kwargs, Slots, Data, JsData, CssData]):\n    def get_context_data(self, variable, another):\n        return {\n            \"variable\": variable,\n        }\n</code></pre> <p>When you then call <code>Component.render</code> or <code>Component.render_to_response</code>, you will get type hints:</p> <pre><code>Button.render(\n    # Error: First arg must be `int`, got `float`\n    args=(1.25, \"abc\"),\n    # Error: Key \"another\" is missing\n    kwargs={\n        \"variable\": \"text\",\n    },\n)\n</code></pre>"},{"location":"concepts/advanced/typing_and_validation/#usage-for-python-311","title":"Usage for Python &lt;3.11","text":"<p>On Python 3.8-3.10, use <code>typing_extensions</code></p> <pre><code>from typing_extensions import TypedDict, NotRequired\n</code></pre> <p>Additionally on Python 3.8-3.9, also import <code>annotations</code>:</p> <pre><code>from __future__ import annotations\n</code></pre> <p>Moreover, on 3.10 and less, you may not be able to use <code>NotRequired</code>, and instead you will need to mark either all keys are required, or all keys as optional, using TypeDict's <code>total</code> kwarg.</p> <p>See PEP-655 for more info.</p>"},{"location":"concepts/advanced/typing_and_validation/#passing-additional-args-or-kwargs","title":"Passing additional args or kwargs","text":"<p>You may have a function that supports any number of args or kwargs:</p> <pre><code>def get_context_data(self, *args, **kwargs):\n    ...\n</code></pre> <p>This is not supported with the typed components.</p> <p>As a workaround:</p> <ul> <li>For <code>*args</code>, set a positional argument that accepts a list of values:</li> </ul> <pre><code># Tuple of one member of list of strings\nArgs = Tuple[List[str]]\n</code></pre> <ul> <li>For <code>*kwargs</code>, set a keyword argument that accepts a dictionary of values:</li> </ul> <pre><code>class Kwargs(TypedDict):\n    variable: str\n    another: int\n    # Pass any extra keys under `extra`\n    extra: Dict[str, any]\n</code></pre>"},{"location":"concepts/advanced/typing_and_validation/#handling-no-args-or-no-kwargs","title":"Handling no args or no kwargs","text":"<p>To declare that a component accepts no Args, Kwargs, etc, you can use <code>EmptyTuple</code> and <code>EmptyDict</code> types:</p> <pre><code>from django_components import Component, EmptyDict, EmptyTuple\n\nArgs = EmptyTuple\nKwargs = Data = Slots = EmptyDict\n\nclass Button(Component[Args, Kwargs, Slots, Data, JsData, CssData]):\n    ...\n</code></pre>"},{"location":"concepts/advanced/typing_and_validation/#runtime-input-validation-with-types","title":"Runtime input validation with types","text":"<p>New in version 0.96</p> <p>NOTE: Kwargs, slots, and data validation is supported only for Python &gt;=3.11</p> <p>In Python 3.11 and later, when you specify the component types, you will get also runtime validation of the inputs you pass to <code>Component.render</code> or <code>Component.render_to_response</code>.</p> <p>So, using the example from before, if you ignored the type errors and still ran the following code:</p> <pre><code>Button.render(\n    # Error: First arg must be `int`, got `float`\n    args=(1.25, \"abc\"),\n    # Error: Key \"another\" is missing\n    kwargs={\n        \"variable\": \"text\",\n    },\n)\n</code></pre> <p>This would raise a <code>TypeError</code>:</p> <pre><code>Component 'Button' expected positional argument at index 0 to be &lt;class 'int'&gt;, got 1.25 of type &lt;class 'float'&gt;\n</code></pre> <p>In case you need to skip these errors, you can either set the faulty member to <code>Any</code>, e.g.:</p> <pre><code># Changed `int` to `Any`\nArgs = Tuple[Any, str]\n</code></pre> <p>Or you can replace <code>Args</code> with <code>Any</code> altogether, to skip the validation of args:</p> <pre><code># Replaced `Args` with `Any`\nclass Button(Component[Any, Kwargs, Slots, Data, JsData, CssData]):\n    ...\n</code></pre> <p>Same applies to kwargs, data, and slots.</p>"},{"location":"concepts/fundamentals/access_component_input/","title":"Accessing component inputs","text":"<p>When you call <code>Component.render</code> or <code>Component.render_to_response</code>, the inputs to these methods can be accessed from within the instance under <code>self.input</code>.</p> <p>This means that you can use <code>self.input</code> inside:</p> <ul> <li><code>get_context_data</code></li> <li><code>get_template_name</code></li> <li><code>get_template</code></li> <li><code>on_render_before</code></li> <li><code>on_render_after</code></li> </ul> <p><code>self.input</code> is only defined during the execution of <code>Component.render</code>, and raises a <code>RuntimeError</code> when called outside of this context.</p> <p><code>self.input</code> has the same fields as the input to <code>Component.render</code>:</p> <pre><code>class TestComponent(Component):\n    def get_context_data(self, var1, var2, variable, another, **attrs):\n        assert self.input.args == (123, \"str\")\n        assert self.input.kwargs == {\"variable\": \"test\", \"another\": 1}\n        assert self.input.slots == {\"my_slot\": \"MY_SLOT\"}\n        assert isinstance(self.input.context, Context)\n\n        return {\n            \"variable\": variable,\n        }\n\nrendered = TestComponent.render(\n    kwargs={\"variable\": \"test\", \"another\": 1},\n    args=(123, \"str\"),\n    slots={\"my_slot\": \"MY_SLOT\"},\n)\n</code></pre> <p>NOTE: The slots in <code>self.input.slots</code> are normalized to slot functions.</p>"},{"location":"concepts/fundamentals/autodiscovery/","title":"Autodiscovery","text":"<p>Every component that you want to use in the template with the <code>{% component %}</code> tag needs to be registered with the <code>ComponentRegistry</code>. Normally, we use the <code>@register</code> decorator for that:</p> <pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    ...\n</code></pre> <p>But for the component to be registered, the code needs to be executed - and for that, the file needs to be imported as a module.</p> <p>One way to do that is by importing all your components in <code>apps.py</code>:</p> <pre><code>from django.apps import AppConfig\n\nclass MyAppConfig(AppConfig):\n    name = \"my_app\"\n\n    def ready(self) -&gt; None:\n        from components.card.card import Card\n        from components.list.list import List\n        from components.menu.menu import Menu\n        from components.button.button import Button\n        ...\n</code></pre> <p>However, there's a simpler way!</p> <p>By default, the Python files in the <code>COMPONENTS.dirs</code> directories (and app-level <code>[app]/components/</code>) are auto-imported in order to auto-register the components.</p> <p>Autodiscovery occurs when Django is loaded, during the <code>AppConfig.ready</code> hook of the <code>apps.py</code> file.</p> <p>If you are using autodiscovery, keep a few points in mind:</p> <ul> <li>Avoid defining any logic on the module-level inside the <code>components</code> dir, that you would not want to run anyway.</li> <li>Components inside the auto-imported files still need to be registered with <code>@register</code></li> <li>Auto-imported component files must be valid Python modules, they must use suffix <code>.py</code>, and module name should follow PEP-8.</li> <li>Subdirectories and files starting with an underscore <code>_</code> (except <code>__init__.py</code>) are ignored.</li> </ul> <p>Autodiscovery can be disabled in the settings.</p>"},{"location":"concepts/fundamentals/autodiscovery/#manually-trigger-autodiscovery","title":"Manually trigger autodiscovery","text":"<p>Autodiscovery can be also triggered manually, using the <code>autodiscover</code> function. This is useful if you want to run autodiscovery at a custom point of the lifecycle:</p> <pre><code>from django_components import autodiscover\n\nautodiscover()\n</code></pre> <p>To get the same list of modules that <code>autodiscover()</code> would return, but without importing them, use <code>get_component_files()</code>:</p> <pre><code>from django_components import get_component_files\n\nmodules = get_component_files(\".py\")\n</code></pre>"},{"location":"concepts/fundamentals/component_context_scope/","title":"Component context and scope","text":"<p>By default, context variables are passed down the template as in regular Django - deeper scopes can access the variables from the outer scopes. So if you have several nested forloops, then inside the deep-most loop you can access variables defined by all previous loops.</p> <p>With this in mind, the <code>{% component %}</code> tag behaves similarly to <code>{% include %}</code> tag - inside the component tag, you can access all variables that were defined outside of it.</p> <p>And just like with <code>{% include %}</code>, if you don't want a specific component template to have access to the parent context, add <code>only</code> to the <code>{% component %}</code> tag:</p> <pre><code>{% component \"calendar\" date=\"2015-06-19\" only / %}\n</code></pre> <p>NOTE: <code>{% csrf_token %}</code> tags need access to the top-level context, and they will not function properly if they are rendered in a component that is called with the <code>only</code> modifier.</p> <p>If you find yourself using the <code>only</code> modifier often, you can set the context_behavior option to <code>\"isolated\"</code>, which automatically applies the <code>only</code> modifier. This is useful if you want to make sure that components don't accidentally access the outer context.</p> <p>Components can also access the outer context in their context methods like <code>get_context_data</code> by accessing the property <code>self.outer_context</code>.</p>"},{"location":"concepts/fundamentals/component_context_scope/#example-of-accessing-outer-context","title":"Example of Accessing Outer Context","text":"<pre><code>&lt;div&gt;\n  {% component \"calender\" / %}\n&lt;/div&gt;\n</code></pre> <p>Assuming that the rendering context has variables such as <code>date</code>, you can use <code>self.outer_context</code> to access them from within <code>get_context_data</code>. Here's how you might implement it:</p> <pre><code>class Calender(Component):\n\n    ...\n\n    def get_context_data(self):\n        outer_field = self.outer_context[\"date\"]\n        return {\n            \"date\": outer_fields,\n        }\n</code></pre> <p>However, as a best practice, it\u2019s recommended not to rely on accessing the outer context directly through <code>self.outer_context</code>. Instead, explicitly pass the variables to the component. For instance, continue passing the variables in the component tag as shown in the previous examples.</p>"},{"location":"concepts/fundamentals/component_context_scope/#context-behavior","title":"Context behavior","text":"<p>django_components supports both Django and Vue-like behavior when it comes to passing data to and through components. This can be configured in context_behavior.</p> <p>This has two modes:</p> <ul> <li> <p><code>\"django\"</code></p> <p>The default Django template behavior.</p> <p>Inside the <code>{% fill %}</code> tag, the context variables you can access are a union of:</p> <ul> <li>All the variables that were OUTSIDE the fill tag, including any\\   <code>{% with %}</code> tags.</li> <li>Any loops (<code>{% for ... %}</code>)   that the <code>{% fill %}</code> tag is part of.</li> <li>Data returned from <code>Component.get_context_data()</code>   of the component that owns the fill tag.</li> </ul> </li> <li> <p><code>\"isolated\"</code></p> <p>Similar behavior to Vue or React, this is useful if you want to make sure that components don't accidentally access variables defined outside of the component.</p> <p>Inside the <code>{% fill %}</code> tag, you can ONLY access variables from 2 places:</p> <ul> <li>Any loops (<code>{% for ... %}</code>)   that the <code>{% fill %}</code> tag is part of.</li> <li><code>Component.get_context_data()</code>   of the component which defined the template (AKA the \"root\" component).</li> </ul> </li> </ul> <p>Warning</p> <p>Notice that the component whose <code>get_context_data()</code> we use inside <code>{% fill %}</code> is NOT the same across the two modes!</p> <p>Consider this example:</p> <pre><code>class Outer(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% component \"inner\" %}\n          {% fill \"content\" %}\n            {{ my_var }}\n          {% endfill %}\n        {% endcomponent %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre> <ul> <li> <p><code>\"django\"</code> - <code>my_var</code> has access to data from <code>get_context_data()</code> of both <code>Inner</code> and <code>Outer</code>.   If there are variables defined in both, then <code>Inner</code> overshadows <code>Outer</code>.</p> </li> <li> <p><code>\"isolated\"</code> - <code>my_var</code> has access to data from <code>get_context_data()</code> of ONLY <code>Outer</code>.</p> </li> </ul>"},{"location":"concepts/fundamentals/component_context_scope/#example-django","title":"Example \"django\"","text":"<p>Given this template:</p> <pre><code>@register(\"root_comp\")\nclass RootComp(Component):\n    template = \"\"\"\n        {% with cheese=\"feta\" %}\n            {% component 'my_comp' %}\n                {{ my_var }}  # my_var\n                {{ cheese }}  # cheese\n            {% endcomponent %}\n        {% endwith %}\n    \"\"\"\n\n    def get_context_data(self):\n        return { \"my_var\": 123 }\n</code></pre> <p>Then if <code>get_context_data()</code> of the component <code>\"my_comp\"</code> returns following data:</p> <pre><code>{ \"my_var\": 456 }\n</code></pre> <p>Then the template will be rendered as:</p> <pre><code>456   # my_var\nfeta  # cheese\n</code></pre> <p>Because <code>\"my_comp\"</code> overshadows the outer variable <code>\"my_var\"</code>, so <code>{{ my_var }}</code> equals <code>456</code>.</p> <p>And variable <code>\"cheese\"</code> equals <code>feta</code>, because the fill CAN access all the data defined in the outer layers, like the <code>{% with %}</code> tag.</p>"},{"location":"concepts/fundamentals/component_context_scope/#example-isolated","title":"Example \"isolated\"","text":"<p>Given this template:</p> <pre><code>class RootComp(Component):\n    template = \"\"\"\n        {% with cheese=\"feta\" %}\n            {% component 'my_comp' %}\n                {{ my_var }}  # my_var\n                {{ cheese }}  # cheese\n            {% endcomponent %}\n        {% endwith %}\n    \"\"\"\n\n    def get_context_data(self):\n        return { \"my_var\": 123 }\n</code></pre> <p>Then if <code>get_context_data()</code> of the component <code>\"my_comp\"</code> returns following data:</p> <pre><code>{ \"my_var\": 456 }\n</code></pre> <p>Then the template will be rendered as:</p> <pre><code>123   # my_var\n    # cheese\n</code></pre> <p>Because variables <code>\"my_var\"</code> and <code>\"cheese\"</code> are searched only inside <code>RootComponent.get_context_data()</code>. But since <code>\"cheese\"</code> is not defined there, it's empty.</p> <p>Info</p> <p>Notice that the variables defined with the <code>{% with %}</code> tag are ignored inside the <code>{% fill %}</code> tag with the <code>\"isolated\"</code> mode.</p>"},{"location":"concepts/fundamentals/components_as_views/","title":"Components as views","text":"<p>New in version 0.34</p> <p>Note: Since 0.92, Component no longer subclasses View. To configure the View class, set the nested <code>Component.View</code> class</p> <p>Components can now be used as views:</p> <ul> <li> <p>Components define the <code>Component.as_view()</code> class method that can be used the same as <code>View.as_view()</code>.</p> </li> <li> <p>By default, you can define GET, POST or other HTTP handlers directly on the Component, same as you do with View. For example, you can override <code>get</code> and <code>post</code> to handle GET and POST requests, respectively.</p> </li> <li> <p>In addition, <code>Component</code> now has a <code>render_to_response</code> method that renders the component template based on the provided context and slots' data and returns an <code>HttpResponse</code> object.</p> </li> </ul>"},{"location":"concepts/fundamentals/components_as_views/#component-as-view-example","title":"Component as view example","text":"<p>Here's an example of a calendar component defined as a view:</p> <pre><code># In a file called [project root]/components/calendar.py\nfrom django_components import Component, ComponentView, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n\n    template = \"\"\"\n        &lt;div class=\"calendar-component\"&gt;\n            &lt;div class=\"header\"&gt;\n                {% slot \"header\" / %}\n            &lt;/div&gt;\n            &lt;div class=\"body\"&gt;\n                Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n            &lt;/div&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    # Handle GET requests\n    def get(self, request, *args, **kwargs):\n        context = {\n            \"date\": request.GET.get(\"date\", \"2020-06-06\"),\n        }\n        slots = {\n            \"header\": \"Calendar header\",\n        }\n        # Return HttpResponse with the rendered content\n        return self.render_to_response(\n            context=context,\n            slots=slots,\n        )\n</code></pre> <p>Then, to use this component as a view, you should create a <code>urls.py</code> file in your components directory, and add a path to the component's view:</p> <pre><code># In a file called [project root]/components/urls.py\nfrom django.urls import path\nfrom components.calendar.calendar import Calendar\n\nurlpatterns = [\n    path(\"calendar/\", Calendar.as_view()),\n]\n</code></pre> <p><code>Component.as_view()</code> is a shorthand for calling <code>View.as_view()</code> and passing the component instance as one of the arguments.</p> <p>Remember to add <code>__init__.py</code> to your components directory, so that Django can find the <code>urls.py</code> file.</p> <p>Finally, include the component's urls in your project's <code>urls.py</code> file:</p> <pre><code># In a file called [project root]/urls.py\nfrom django.urls import include, path\n\nurlpatterns = [\n    path(\"components/\", include(\"components.urls\")),\n]\n</code></pre> <p>Note: Slots content are automatically escaped by default to prevent XSS attacks. To disable escaping, set <code>escape_slots_content=False</code> in the <code>render_to_response</code> method. If you do so, you should make sure that any content you pass to the slots is safe, especially if it comes from user input.</p> <p>If you're planning on passing an HTML string, check Django's use of <code>format_html</code> and <code>mark_safe</code>.</p>"},{"location":"concepts/fundamentals/components_as_views/#modifying-the-view-class","title":"Modifying the View class","text":"<p>The View class that handles the requests is defined on <code>Component.View</code>.</p> <p>When you define a GET or POST handlers on the <code>Component</code> class, like so:</p> <pre><code>class MyComponent(Component):\n    def get(self, request, *args, **kwargs):\n        return self.render_to_response(\n            context={\n                \"date\": request.GET.get(\"date\", \"2020-06-06\"),\n            },\n        )\n\n    def post(self, request, *args, **kwargs) -&gt; HttpResponse:\n        variable = request.POST.get(\"variable\")\n        return self.render_to_response(\n            kwargs={\"variable\": variable}\n        )\n</code></pre> <p>Then the request is still handled by <code>Component.View.get()</code> or <code>Component.View.post()</code> methods. However, by default, <code>Component.View.get()</code> points to <code>Component.get()</code>, and so on.</p> <pre><code>class ComponentView(View):\n    component: Component = None\n    ...\n\n    def get(self, request, *args, **kwargs):\n        return self.component.get(request, *args, **kwargs)\n\n    def post(self, request, *args, **kwargs):\n        return self.component.post(request, *args, **kwargs)\n\n    ...\n</code></pre> <p>If you want to define your own <code>View</code> class, you need to:</p> <ol> <li>Set the class as <code>Component.View</code></li> <li>Subclass from <code>ComponentView</code>, so the View instance has access to the component instance.</li> </ol> <p>In the example below, we added extra logic into <code>View.setup()</code>.</p> <p>Note that the POST handler is still defined at the top. This is because <code>View</code> subclasses <code>ComponentView</code>, which defines the <code>post()</code> method that calls <code>Component.post()</code>.</p> <p>If you were to overwrite the <code>View.post()</code> method, then <code>Component.post()</code> would be ignored.</p> <pre><code>from django_components import Component, ComponentView\n\nclass MyComponent(Component):\n\n    def post(self, request, *args, **kwargs) -&gt; HttpResponse:\n        variable = request.POST.get(\"variable\")\n        return self.component.render_to_response(\n            kwargs={\"variable\": variable}\n        )\n\n    class View(ComponentView):\n        def setup(self, request, *args, **kwargs):\n            super(request, *args, **kwargs)\n\n            do_something_extra(request, *args, **kwargs)\n</code></pre>"},{"location":"concepts/fundamentals/components_in_python/","title":"Components in Python","text":"<p>New in version 0.81</p> <p>Components can be rendered outside of Django templates, calling them as regular functions (\"React-style\").</p> <p>The component class defines <code>render</code> and <code>render_to_response</code> class methods. These methods accept positional args, kwargs, and slots, offering the same flexibility as the <code>{% component %}</code> tag:</p> <pre><code>class SimpleComponent(Component):\n    template = \"\"\"\n        {% load component_tags %}\n        hello: {{ hello }}\n        foo: {{ foo }}\n        kwargs: {{ kwargs|safe }}\n        slot_first: {% slot \"first\" required / %}\n    \"\"\"\n\n    def get_context_data(self, arg1, arg2, **kwargs):\n        return {\n            \"hello\": arg1,\n            \"foo\": arg2,\n            \"kwargs\": kwargs,\n        }\n\nrendered = SimpleComponent.render(\n    args=[\"world\", \"bar\"],\n    kwargs={\"kw1\": \"test\", \"kw2\": \"ooo\"},\n    slots={\"first\": \"FIRST_SLOT\"},\n    context={\"from_context\": 98},\n)\n</code></pre> <p>Renders:</p> <pre><code>hello: world\nfoo: bar\nkwargs: {'kw1': 'test', 'kw2': 'ooo'}\nslot_first: FIRST_SLOT\n</code></pre>"},{"location":"concepts/fundamentals/components_in_python/#inputs-of-render-and-render_to_response","title":"Inputs of <code>render</code> and <code>render_to_response</code>","text":"<p>Both <code>render</code> and <code>render_to_response</code> accept the same input:</p> <pre><code>Component.render(\n    context: Mapping | django.template.Context | None = None,\n    args: List[Any] | None = None,\n    kwargs: Dict[str, Any] | None = None,\n    slots: Dict[str, str | SafeString | SlotFunc] | None = None,\n    escape_slots_content: bool = True\n) -&gt; str:\n</code></pre> <ul> <li> <p><code>args</code> - Positional args for the component. This is the same as calling the component   as <code>{% component \"my_comp\" arg1 arg2 ... %}</code></p> </li> <li> <p><code>kwargs</code> - Keyword args for the component. This is the same as calling the component   as <code>{% component \"my_comp\" key1=val1 key2=val2 ... %}</code></p> </li> <li> <p><code>slots</code> - Component slot fills. This is the same as pasing <code>{% fill %}</code> tags to the component.   Accepts a dictionary of <code>{ slot_name: slot_content }</code> where <code>slot_content</code> can be a string   or <code>SlotFunc</code>.</p> </li> <li> <p><code>escape_slots_content</code> - Whether the content from <code>slots</code> should be escaped. <code>True</code> by default to prevent XSS attacks. If you disable escaping, you should make sure that any content you pass to the slots is safe, especially if it comes from user input.</p> </li> <li> <p><code>context</code> - A context (dictionary or Django's Context) within which the component   is rendered. The keys on the context can be accessed from within the template.</p> </li> <li> <p>NOTE: In \"isolated\" mode, context is NOT accessible, and data MUST be passed via     component's args and kwargs.</p> </li> <li> <p><code>request</code> - A Django request object. This is used to enable Django template <code>context_processors</code> to run,   allowing for template tags like <code>{% csrf_token %}</code> and variables like <code>{{ debug }}</code>.  </p> </li> <li>Similar behavior can be achieved with provide / inject.</li> <li>This is used internally to convert <code>context</code> to a RequestContext. It does nothing if <code>context</code> is already      a <code>Context</code> instance.</li> </ul>"},{"location":"concepts/fundamentals/components_in_python/#slotfunc","title":"<code>SlotFunc</code>","text":"<p>When rendering components with slots in <code>render</code> or <code>render_to_response</code>, you can pass either a string or a function.</p> <p>The function has following signature:</p> <pre><code>def render_func(\n   context: Context,\n   data: Dict[str, Any],\n   slot_ref: SlotRef,\n) -&gt; str | SafeString:\n    return nodelist.render(ctx)\n</code></pre> <ul> <li><code>context</code> - Django's Context available to the Slot Node.</li> <li><code>data</code> - Data passed to the <code>{% slot %}</code> tag. See Scoped Slots.</li> <li><code>slot_ref</code> - The default slot content. See Accessing original content of slots.</li> <li>NOTE: The slot is lazily evaluated. To render the slot, convert it to string with <code>str(slot_ref)</code>.</li> </ul> <p>Example:</p> <pre><code>def footer_slot(ctx, data, slot_ref):\n   return f\"\"\"\n      SLOT_DATA: {data['abc']}\n      ORIGINAL: {slot_ref}\n   \"\"\"\n\nMyComponent.render_to_response(\n    slots={\n        \"footer\": footer_slot,\n   },\n)\n</code></pre>"},{"location":"concepts/fundamentals/components_in_python/#response-class-of-render_to_response","title":"Response class of <code>render_to_response</code>","text":"<p>While <code>render</code> method returns a plain string, <code>render_to_response</code> wraps the rendered content in a \"Response\" class. By default, this is <code>django.http.HttpResponse</code>.</p> <p>If you want to use a different Response class in <code>render_to_response</code>, set the <code>Component.response_class</code> attribute:</p> <pre><code>class MyResponse(HttpResponse):\n    def __init__(self, *args, **kwargs) -&gt; None:\n        super().__init__(*args, **kwargs)\n        # Configure response\n        self.headers = ...\n        self.status = ...\n\nclass SimpleComponent(Component):\n    response_class = MyResponse\n    template: types.django_html = \"HELLO\"\n\nresponse = SimpleComponent.render_to_response()\nassert isinstance(response, MyResponse)\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/","title":"Defining HTML / JS / CSS files","text":"<p>As you could have seen in the tutorial, there's multiple ways how you can associate HTML / JS / CSS with a component:</p> <ul> <li>You can set <code>Component.template</code>,   <code>Component.css</code> and   <code>Component.js</code> to define the main HTML / CSS / JS for a component   as inlined code.</li> <li>You can set <code>Component.template_file</code>,   <code>Component.css_file</code> and   <code>Component.js_file</code> to define the main HTML / CSS / JS   for a component in separate files.</li> <li>You can link additional CSS / JS files using   <code>Component.Media.js</code>   and <code>Component.Media.css</code>.</li> </ul> <p>Warning</p> <p>You cannot use both inlined code and separate file for a single language type:</p> <ul> <li>You can only either set <code>Component.template</code> or <code>Component.template_file</code></li> <li>You can only either set <code>Component.css</code> or <code>Component.css_file</code></li> <li>You can only either set <code>Component.js</code> or <code>Component.js_file</code></li> </ul> <p>However, you can freely mix these for different languages:</p> <pre><code>class MyTable(Component):\n    template: types.django_html = \"\"\"\n      &lt;div class=\"welcome\"&gt;\n        Hi there!\n      &lt;/div&gt;\n    \"\"\"\n    js_file = \"my_table.js\"\n    css_file = \"my_table.css\"\n</code></pre> <p>Note</p> <p>django-component's management of files is inspired by Django's <code>Media</code> class.</p> <p>To be familiar with how Django handles static files, we recommend reading also:</p> <ul> <li>How to manage static files (e.g. images, JavaScript, CSS)</li> </ul>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#defining-file-paths-relative-to-component","title":"Defining file paths relative to component","text":"<p>As seen in the getting started example, to associate HTML / JS / CSS files with a component, you can set them as <code>Component.template_file</code>, <code>Component.js_file</code> and <code>Component.css_file</code> respectively:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"template.html\"\n    css_file = \"style.css\"\n    js_file = \"script.js\"\n</code></pre> <p>In the example above, we defined the files relative to the directory where the component file is defined.</p> <p>Alternatively, you can specify the file paths relative to the directories set in <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code>.</p> <p>If you specify the paths relative to component's directory, django-componenents does the conversion automatically for you.</p> <p>Thus, assuming that <code>COMPONENTS.dirs</code> contains path <code>[project root]/components</code>, the example above is the same as writing:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar/template.html\"\n    css_file = \"calendar/style.css\"\n    js_file = \"calendar/script.js\"\n</code></pre> <p>Important</p> <p>File path resolution in-depth</p> <p>At component class creation, django-components checks all file paths defined on the component (e.g. <code>Component.template_file</code>).</p> <p>For each file path, it checks if the file path is relative to the component's directory. And such file exists, the component's file path is re-written to be defined relative to a first matching directory in <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code>.</p> <p>Example:</p> [root]/components/mytable/mytable.py<pre><code>class MyTable(Component):\n    template_file = \"mytable.html\"\n</code></pre> <ol> <li>Component <code>MyTable</code> is defined in file <code>[root]/components/mytable/mytable.py</code>.</li> <li>The component's directory is thus <code>[root]/components/mytable/</code>.</li> <li>Because <code>MyTable.template_file</code> is <code>mytable.html</code>, django-components tries to     resolve it as <code>[root]/components/mytable/mytable.html</code>.</li> <li>django-components checks the filesystem. If there's no such file, nothing happens.</li> <li>If there IS such file, django-components tries to rewrite the path.</li> <li>django-components searches <code>COMPONENTS.dirs</code> and <code>COMPONENTS.app_dirs</code> for a first     directory that contains <code>[root]/components/mytable/mytable.html</code>.</li> <li>It comes across <code>[root]/components/</code>, which DOES contain the path to <code>mytable.html</code>.</li> <li>Thus, it rewrites <code>template_file</code> from <code>mytable.html</code> to <code>mytable/mytable.html</code>.</li> </ol> <p>NOTE: In case of ambiguity, the preference goes to resolving the files relative to the component's directory.</p>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#defining-additional-js-and-css-files","title":"Defining additional JS and CSS files","text":"<p>Each component can have only a single template, and single main JS and CSS. However, you can define additional JS or CSS using the nested <code>Component.Media</code> class.</p> <p>This <code>Media</code> class behaves similarly to Django's Media class:</p> <ul> <li>Paths are generally handled as static file paths, and resolved URLs are rendered to HTML with   <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A path that starts with <code>http</code>, <code>https</code>, or <code>/</code> is considered a URL, skipping the static file resolution.   This path is still rendered to HTML with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A <code>SafeString</code>,   or a function (with <code>__html__</code> method) is considered an already-formatted HTML tag, skipping both static file   resolution and rendering with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>You can set <code>extend</code> to configure     whether to inherit JS / CSS from parent components. See     Controlling Media Inheritance.</li> </ul> <p>However, there's a few differences from Django's Media class:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list,    or (CSS-only) a dictonary (See <code>ComponentMediaInput</code>).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>,    <code>SafeString</code>, or a function    (See <code>ComponentMediaInputPath</code>).</li> <li>Individual JS / CSS files can be glob patterns, e.g. <code>*.js</code> or <code>styles/**/*.css</code>.</li> <li>If you set <code>Media.extend</code> to a list,    it should be a list of <code>Component</code> classes.</li> </ol> <pre><code>class MyTable(Component):\n    class Media:\n        js = [\n            \"path/to/script.js\",\n            \"path/to/*.js\",  # Or as a glob\n            \"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\",  # AlpineJS\n        ]\n        css = {\n            \"all\": [\n                \"path/to/style.css\",\n                \"path/to/*.css\",  # Or as a glob\n                \"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\",  # TailwindCSS\n            ],\n            \"print\": [\"path/to/style2.css\"],\n        }\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#configuring-css-media-types","title":"Configuring CSS Media Types","text":"<p>You can define which stylesheets will be associated with which CSS Media types. You do so by defining CSS files as a dictionary.</p> <p>See the corresponding Django Documentation.</p> <p>Again, you can set either a single file or a list of files per media type:</p> <pre><code>class MyComponent(Component):\n    class Media:\n        css = {\n            \"all\": \"path/to/style1.css\",\n            \"print\": [\"path/to/style2.css\", \"path/to/style3.css\"],\n        }\n</code></pre> <p>Note</p> <p>When you define CSS as a string or a list, the <code>all</code> media type is implied.</p> <p>So these two examples are the same:</p> <pre><code>class MyComponent(Component):\n    class Media:\n        css = \"path/to/style1.css\"\n</code></pre> <pre><code>class MyComponent(Component):\n    class Media:\n        css = {\n            \"all\": [\"path/to/style1.css\"],\n        }\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#supported-types-for-file-paths","title":"Supported types for file paths","text":"<p>File paths can be any of:</p> <ul> <li><code>str</code></li> <li><code>bytes</code></li> <li><code>PathLike</code> (<code>__fspath__</code> method)</li> <li><code>SafeData</code> (<code>__html__</code> method)</li> <li><code>Callable</code> that returns any of the above, evaluated at class creation (<code>__new__</code>)</li> </ul> <p>See <code>ComponentMediaInputPath</code>.</p> <pre><code>from pathlib import Path\n\nfrom django.utils.safestring import mark_safe\n\nclass SimpleComponent(Component):\n    class Media:\n        css = [\n            mark_safe('&lt;link href=\"/static/calendar/style1.css\" rel=\"stylesheet\" /&gt;'),\n            Path(\"calendar/style1.css\"),\n            \"calendar/style2.css\",\n            b\"calendar/style3.css\",\n            lambda: \"calendar/style4.css\",\n        ]\n        js = [\n            mark_safe('&lt;script src=\"/static/calendar/script1.js\"&gt;&lt;/script&gt;'),\n            Path(\"calendar/script1.js\"),\n            \"calendar/script2.js\",\n            b\"calendar/script3.js\",\n            lambda: \"calendar/script4.js\",\n        ]\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#paths-as-objects","title":"Paths as objects","text":"<p>In the example above, you can see that when we used Django's <code>mark_safe()</code> to mark a string as a <code>SafeString</code>, we had to define the full <code>&lt;script&gt;</code>/<code>&lt;link&gt;</code> tag.</p> <p>This is an extension of Django's Paths as objects feature, where \"safe\" strings are taken as is, and accessed only at render time.</p> <p>Because of that, the paths defined as \"safe\" strings are NEVER resolved, neither relative to component's directory, nor relative to <code>COMPONENTS.dirs</code>.</p> <p>\"Safe\" strings can be used to lazily resolve a path, or to customize the <code>&lt;script&gt;</code> or <code>&lt;link&gt;</code> tag for individual paths:</p> <p>In the example below, we make use of \"safe\" strings to add <code>type=\"module\"</code> to the script tag that will fetch <code>calendar/script2.js</code>. In this case, we implemented a \"safe\" string by defining a <code>__html__</code> method.</p> <pre><code>class ModuleJsPath:\n    def __init__(self, static_path: str) -&gt; None:\n        self.static_path = static_path\n\n    def __html__(self):\n        full_path = static(self.static_path)\n        return format_html(\n            f'&lt;script type=\"module\" src=\"{full_path}\"&gt;&lt;/script&gt;'\n        )\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar/template.html\"\n\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n\n    class Media:\n        css = \"calendar/style1.css\"\n        js = [\n            # &lt;script&gt; tag constructed by Media class\n            \"calendar/script1.js\",\n            # Custom &lt;script&gt; tag\n            ModuleJsPath(\"calendar/script2.js\"),\n        ]\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#customize-how-paths-are-rendered-into-html-tags","title":"Customize how paths are rendered into HTML tags","text":"<p>Sometimes you may need to change how all CSS <code>&lt;link&gt;</code> or JS <code>&lt;script&gt;</code> tags are rendered for a given component. You can achieve this by providing your own subclass of Django's <code>Media</code> class to component's <code>media_class</code> attribute.</p> <p>Normally, the JS and CSS paths are passed to <code>Media</code> class, which decides how the paths are resolved and how the <code>&lt;link&gt;</code> and <code>&lt;script&gt;</code> tags are constructed.</p> <p>To change how the tags are constructed, you can override the <code>Media.render_js</code> and <code>Media.render_css</code> methods:</p> <pre><code>from django.forms.widgets import Media\nfrom django_components import Component, register\n\nclass MyMedia(Media):\n    # Same as original Media.render_js, except\n    # the `&lt;script&gt;` tag has also `type=\"module\"`\n    def render_js(self):\n        tags = []\n        for path in self._js:\n            if hasattr(path, \"__html__\"):\n                tag = path.__html__()\n            else:\n                tag = format_html(\n                    '&lt;script type=\"module\" src=\"{}\"&gt;&lt;/script&gt;',\n                    self.absolute_path(path)\n                )\n        return tags\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar/template.html\"\n    css_file = \"calendar/style.css\"\n    js_file = \"calendar/script.js\"\n\n    class Media:\n        css = \"calendar/style1.css\"\n        js = \"calendar/script2.js\"\n\n    # Override the behavior of Media class\n    media_class = MyMedia\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#accessing-components-html-js-css","title":"Accessing component's HTML / JS / CSS","text":"<p>Component's HTML / CSS / JS is resolved and loaded lazily.</p> <p>This means that, when you specify any of <code>template_file</code>, <code>js_file</code>, <code>css_file</code>, or <code>Media.js/css</code>, these file paths will be resolved only once you either:</p> <ol> <li> <p>Access any of the following attributes on the component:</p> <ul> <li><code>media</code>,  <code>template</code>,  <code>template_file</code>,  <code>js</code>,  <code>js_file</code>,  <code>css</code>,  <code>css_file</code></li> </ul> </li> <li> <p>Render the component.</p> </li> </ol> <p>Once the component's media files have been loaded once, they will remain in-memory on the Component class:</p> <ul> <li>HTML from <code>Component.template_file</code>   will be available under <code>Component.template</code></li> <li>CSS from <code>Component.css_file</code>   will be available under <code>Component.css</code></li> <li>JS from <code>Component.js_file</code>   will be available under <code>Component.js</code></li> </ul> <p>Thus, whether you define HTML via <code>Component.template_file</code> or <code>Component.template</code>, you can always access the HTML content under <code>Component.template</code>. And the same applies for JS and CSS.</p> <p>Example:</p> <pre><code># When we create Calendar component, the files like `calendar/template.html`\n# are not yet loaded!\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar/template.html\"\n    css_file = \"calendar/style.css\"\n    js_file = \"calendar/script.js\"\n\n    class Media:\n        css = \"calendar/style1.css\"\n        js = \"calendar/script2.js\"\n\n# It's only at this moment that django-components reads the files like `calendar/template.html`\nprint(Calendar.css)\n# Output:\n# .calendar {\n#   width: 200px;\n#   background: pink;\n# }\n</code></pre> <p>Warning</p> <p>Do NOT modify HTML / CSS / JS after it has been loaded</p> <p>django-components assumes that the component's media files like <code>js_file</code> or <code>Media.js/css</code> are static.</p> <p>If you need to dynamically change these media files, consider instead defining multiple Components.</p> <p>Modifying these files AFTER the component has been loaded at best does nothing. However, this is an untested behavior, which may lead to unexpected errors.</p>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#accessing-components-media-files","title":"Accessing component's Media files","text":"<p>To access the files that you defined under <code>Component.Media</code>, use <code>Component.media</code> (lowercase). This is consistent behavior with Django's Media class.</p> <pre><code>class MyComponent(Component):\n    class Media:\n        js = \"path/to/script.js\"\n        css = \"path/to/style.css\"\n\nprint(MyComponent.media)\n# Output:\n# &lt;script src=\"/static/path/to/script.js\"&gt;&lt;/script&gt;\n# &lt;link href=\"/static/path/to/style.css\" media=\"all\" rel=\"stylesheet\"&gt;\n</code></pre>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#componentmedia-vs-componentmedia","title":"<code>Component.Media</code> vs <code>Component.media</code>","text":"<p>When working with component media files, there are a few important concepts to understand:</p> <ul> <li> <p><code>Component.Media</code></p> <ul> <li>Is the \"raw\" media definition, or the input, which holds only the component's own media definition</li> <li>This class is NOT instantiated, it merely holds the JS / CSS files.</li> </ul> </li> <li> <p><code>Component.media</code></p> <ul> <li>Returns all resolved media files, including those inherited from parent components</li> <li>Is an instance of <code>Component.media_class</code></li> </ul> </li> </ul> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass ChildComponent(ParentComponent):\n    class Media:\n        js = [\"child.js\"]\n\n# Access only this component's media\nprint(ChildComponent.Media.js)  # [\"child.js\"]\n\n# Access all inherited media\nprint(ChildComponent.media._js)  # [\"parent.js\", \"child.js\"]\n</code></pre> <p>Note</p> <p>You should not manually modify <code>Component.media</code> or <code>Component.Media</code> after the component has been resolved, as this may lead to unexpected behavior.</p> <p>If you want to modify the class that is instantiated for <code>Component.media</code>, you can configure <code>Component.media_class</code> (See example).</p>"},{"location":"concepts/fundamentals/defining_js_css_html_files/#controlling-media-inheritance","title":"Controlling Media Inheritance","text":"<p>By default, the media files are inherited from the parent component.</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"parent.js\", \"script.js\"]\n</code></pre> <p>You can set the component NOT to inherit from the parent component by setting the <code>extend</code> attribute to <code>False</code>:</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        extend = False  # Don't inherit parent media\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"script.js\"]\n</code></pre> <p>Alternatively, you can specify which components to inherit from. In such case, the media files are inherited ONLY from the specified components, and NOT from the original parent components:</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        # Only inherit from these, ignoring the files from the parent\n        extend = [OtherComponent1, OtherComponent2]\n\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"script.js\", \"other1.js\", \"other2.js\"]\n</code></pre> <p>Info</p> <p>The <code>extend</code> behaves consistently with Django's Media class, with one exception:</p> <ul> <li>When you set <code>extend</code> to a list, the list is expected to contain Component classes (or other classes that have a nested <code>Media</code> class).</li> </ul>"},{"location":"concepts/fundamentals/html_attributes/","title":"HTML attributes","text":"<p>New in version 0.74:</p> <p>You can use the <code>html_attrs</code> tag to render HTML attributes, given a dictionary of values.</p> <p>So if you have a template:</p> <pre><code>&lt;div class=\"{{ classes }}\" data-id=\"{{ my_id }}\"&gt;\n&lt;/div&gt;\n</code></pre> <p>You can simplify it with <code>html_attrs</code> tag:</p> <pre><code>&lt;div {% html_attrs attrs %}&gt;\n&lt;/div&gt;\n</code></pre> <p>where <code>attrs</code> is:</p> <pre><code>attrs = {\n    \"class\": classes,\n    \"data-id\": my_id,\n}\n</code></pre> <p>This feature is inspired by <code>merge_attrs</code> tag of django-web-components and \"fallthrough attributes\" feature of Vue.</p>"},{"location":"concepts/fundamentals/html_attributes/#removing-atttributes","title":"Removing atttributes","text":"<p>Attributes that are set to <code>None</code> or <code>False</code> are NOT rendered.</p> <p>So given this input:</p> <pre><code>attrs = {\n    \"class\": \"text-green\",\n    \"required\": False,\n    \"data-id\": None,\n}\n</code></pre> <p>And template:</p> <pre><code>&lt;div {% html_attrs attrs %}&gt;\n&lt;/div&gt;\n</code></pre> <p>Then this renders:</p> <pre><code>&lt;div class=\"text-green\"&gt;&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/html_attributes/#boolean-attributes","title":"Boolean attributes","text":"<p>In HTML, boolean attributes are usually rendered with no value. Consider the example below where the first button is disabled and the second is not:</p> <pre><code>&lt;button disabled&gt;Click me!&lt;/button&gt; &lt;button&gt;Click me!&lt;/button&gt;\n</code></pre> <p>HTML rendering with <code>html_attrs</code> tag or <code>attributes_to_string</code> works the same way, where <code>key=True</code> is rendered simply as <code>key</code>, and <code>key=False</code> is not render at all.</p> <p>So given this input:</p> <pre><code>attrs = {\n    \"disabled\": True,\n    \"autofocus\": False,\n}\n</code></pre> <p>And template:</p> <pre><code>&lt;div {% html_attrs attrs %}&gt;\n&lt;/div&gt;\n</code></pre> <p>Then this renders:</p> <pre><code>&lt;div disabled&gt;&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/html_attributes/#default-attributes","title":"Default attributes","text":"<p>Sometimes you may want to specify default values for attributes. You can pass a second argument (or kwarg <code>defaults</code>) to set the defaults.</p> <pre><code>&lt;div {% html_attrs attrs defaults %}&gt;\n    ...\n&lt;/div&gt;\n</code></pre> <p>In the example above, if <code>attrs</code> contains e.g. the <code>class</code> key, <code>html_attrs</code> will render:</p> <p><code>class=\"{{ attrs.class }}\"</code></p> <p>Otherwise, <code>html_attrs</code> will render:</p> <p><code>class=\"{{ defaults.class }}\"</code></p>"},{"location":"concepts/fundamentals/html_attributes/#appending-attributes","title":"Appending attributes","text":"<p>For the <code>class</code> HTML attribute, it's common that we want to join multiple values, instead of overriding them. For example, if you're authoring a component, you may want to ensure that the component will ALWAYS have a specific class. Yet, you may want to allow users of your component to supply their own classes.</p> <p>We can achieve this by adding extra kwargs. These values will be appended, instead of overwriting the previous value.</p> <p>So if we have a variable <code>attrs</code>:</p> <pre><code>attrs = {\n    \"class\": \"my-class pa-4\",\n}\n</code></pre> <p>And on <code>html_attrs</code> tag, we set the key <code>class</code>:</p> <pre><code>&lt;div {% html_attrs attrs class=\"some-class\" %}&gt;\n&lt;/div&gt;\n</code></pre> <p>Then these will be merged and rendered as:</p> <pre><code>&lt;div data-value=\"my-class pa-4 some-class\"&gt;&lt;/div&gt;\n</code></pre> <p>To simplify merging of variables, you can supply the same key multiple times, and these will be all joined together:</p> <pre><code>{# my_var = \"class-from-var text-red\" #}\n&lt;div {% html_attrs attrs class=\"some-class another-class\" class=my_var %}&gt;\n&lt;/div&gt;\n</code></pre> <p>Renders:</p> <pre><code>&lt;div\n  data-value=\"my-class pa-4 some-class another-class class-from-var text-red\"\n&gt;&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/html_attributes/#rules-for-html_attrs","title":"Rules for <code>html_attrs</code>","text":"<ol> <li>Both <code>attrs</code> and <code>defaults</code> can be passed as positional args</li> </ol> <p><code>{% html_attrs attrs defaults key=val %}</code></p> <p>or as kwargs</p> <p><code>{% html_attrs key=val defaults=defaults attrs=attrs %}</code></p> <ol> <li> <p>Both <code>attrs</code> and <code>defaults</code> are optional (can be omitted)</p> </li> <li> <p>Both <code>attrs</code> and <code>defaults</code> are dictionaries, and we can define them the same way we define dictionaries for the <code>component</code> tag. So either as <code>attrs=attrs</code> or <code>attrs:key=value</code>.</p> </li> <li> <p>All other kwargs are appended and can be repeated.</p> </li> </ol>"},{"location":"concepts/fundamentals/html_attributes/#examples-for-html_attrs","title":"Examples for <code>html_attrs</code>","text":"<p>Assuming that:</p> <pre><code>class_from_var = \"from-var\"\n\nattrs = {\n    \"class\": \"from-attrs\",\n    \"type\": \"submit\",\n}\n\ndefaults = {\n    \"class\": \"from-defaults\",\n    \"role\": \"button\",\n}\n</code></pre> <p>Then:</p> <ul> <li>Empty tag  <code>{% html_attr %}</code></li> </ul> <p>renders (empty string):  <code></code></p> <ul> <li>Only kwargs  <code>{% html_attr class=\"some-class\" class=class_from_var data-id=\"123\" %}</code></li> </ul> <p>renders:  <code>class=\"some-class from-var\" data-id=\"123\"</code></p> <ul> <li>Only attrs  <code>{% html_attr attrs %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs\" type=\"submit\"</code></p> <ul> <li>Attrs as kwarg  <code>{% html_attr attrs=attrs %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs\" type=\"submit\"</code></p> <ul> <li>Only defaults (as kwarg)  <code>{% html_attr defaults=defaults %}</code></li> </ul> <p>renders:  <code>class=\"from-defaults\" role=\"button\"</code></p> <ul> <li>Attrs using the <code>prefix:key=value</code> construct  <code>{% html_attr attrs:class=\"from-attrs\" attrs:type=\"submit\" %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs\" type=\"submit\"</code></p> <ul> <li>Defaults using the <code>prefix:key=value</code> construct  <code>{% html_attr defaults:class=\"from-defaults\" %}</code></li> </ul> <p>renders:  <code>class=\"from-defaults\" role=\"button\"</code></p> <ul> <li>All together (1) - attrs and defaults as positional args:  <code>{% html_attrs attrs defaults class=\"added_class\" class=class_from_var data-id=123 %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs added_class from-var\" type=\"submit\" role=\"button\" data-id=123</code></p> <ul> <li>All together (2) - attrs and defaults as kwargs args:  <code>{% html_attrs class=\"added_class\" class=class_from_var data-id=123 attrs=attrs defaults=defaults %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs added_class from-var\" type=\"submit\" role=\"button\" data-id=123</code></p> <ul> <li>All together (3) - mixed:  <code>{% html_attrs attrs defaults:class=\"default-class\" class=\"added_class\" class=class_from_var data-id=123 %}</code></li> </ul> <p>renders:  <code>class=\"from-attrs added_class from-var\" type=\"submit\" data-id=123</code></p>"},{"location":"concepts/fundamentals/html_attributes/#full-example-for-html_attrs","title":"Full example for <code>html_attrs</code>","text":"<pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template: t.django_html = \"\"\"\n        &lt;div\n            {% html_attrs attrs\n                defaults:class=\"pa-4 text-red\"\n                class=\"my-comp-date\"\n                class=class_from_var\n                data-id=\"123\"\n            %}\n        &gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self, date: Date, attrs: dict):\n        return {\n            \"date\": date,\n            \"attrs\": attrs,\n            \"class_from_var\": \"extra-class\"\n        }\n\n@register(\"parent\")\nclass Parent(Component):\n    template: t.django_html = \"\"\"\n        {% component \"my_comp\"\n            date=date\n            attrs:class=\"pa-0 border-solid border-red\"\n            attrs:data-json=json_data\n            attrs:@click=\"(e) =&gt; onClick(e, 'from_parent')\"\n        / %}\n    \"\"\"\n\n    def get_context_data(self, date: Date):\n        return {\n            \"date\": datetime.now(),\n            \"json_data\": json.dumps({\"value\": 456})\n        }\n</code></pre> <p>Note: For readability, we've split the tags across multiple lines.</p> <p>Inside <code>MyComp</code>, we defined a default attribute</p> <p><code>defaults:class=\"pa-4 text-red\"</code></p> <p>So if <code>attrs</code> includes key <code>class</code>, the default above will be ignored.</p> <p><code>MyComp</code> also defines <code>class</code> key twice. It means that whether the <code>class</code> attribute is taken from <code>attrs</code> or <code>defaults</code>, the two <code>class</code> values will be appended to it.</p> <p>So by default, <code>MyComp</code> renders:</p> <pre><code>&lt;div class=\"pa-4 text-red my-comp-date extra-class\" data-id=\"123\"&gt;...&lt;/div&gt;\n</code></pre> <p>Next, let's consider what will be rendered when we call <code>MyComp</code> from <code>Parent</code> component.</p> <p><code>MyComp</code> accepts a <code>attrs</code> dictionary, that is passed to <code>html_attrs</code>, so the contents of that dictionary are rendered as the HTML attributes.</p> <p>In <code>Parent</code>, we make use of passing dictionary key-value pairs as kwargs to define individual attributes as if they were regular kwargs.</p> <p>So all kwargs that start with <code>attrs:</code> will be collected into an <code>attrs</code> dict.</p> <pre><code>    attrs:class=\"pa-0 border-solid border-red\"\n    attrs:data-json=json_data\n    attrs:@click=\"(e) =&gt; onClick(e, 'from_parent')\"\n</code></pre> <p>And <code>get_context_data</code> of <code>MyComp</code> will receive <code>attrs</code> input with following keys:</p> <pre><code>attrs = {\n    \"class\": \"pa-0 border-solid\",\n    \"data-json\": '{\"value\": 456}',\n    \"@click\": \"(e) =&gt; onClick(e, 'from_parent')\",\n}\n</code></pre> <p><code>attrs[\"class\"]</code> overrides the default value for <code>class</code>, whereas other keys will be merged.</p> <p>So in the end <code>MyComp</code> will render:</p> <pre><code>&lt;div\n  class=\"pa-0 border-solid my-comp-date extra-class\"\n  data-id=\"123\"\n  data-json='{\"value\": 456}'\n  @click=\"(e) =&gt; onClick(e, 'from_parent')\"\n&gt;\n  ...\n&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/html_attributes/#rendering-html-attributes-outside-of-templates","title":"Rendering HTML attributes outside of templates","text":"<p>If you need to use serialize HTML attributes outside of Django template and the <code>html_attrs</code> tag, you can use <code>attributes_to_string</code>:</p> <pre><code>from django_components.attributes import attributes_to_string\n\nattrs = {\n    \"class\": \"my-class text-red pa-4\",\n    \"data-id\": 123,\n    \"required\": True,\n    \"disabled\": False,\n    \"ignored-attr\": None,\n}\n\nattributes_to_string(attrs)\n# 'class=\"my-class text-red pa-4\" data-id=\"123\" required'\n</code></pre>"},{"location":"concepts/fundamentals/http_request/","title":"HTTP Request","text":"<p>The most common use of django-components is to render HTML for a given request. As such, there are a few features that are dependent on the request object.</p>"},{"location":"concepts/fundamentals/http_request/#passing-and-accessing-httprequest","title":"Passing and accessing HttpRequest","text":"<p>In regular Django templates, the request object is available only within the <code>RequestContext</code>.</p> <p>In Components, you can either use <code>RequestContext</code>, or pass the <code>request</code> object explicitly to <code>Component.render()</code> and <code>Component.render_to_response()</code>.</p> <p>When a component is nested in another, the child component uses parent's <code>request</code> object.</p> <p>You can access the request object under <code>Component.request</code>:</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        return {\n            'user_id': self.request.GET['user_id'],\n        }\n\n# \u2705 With request\nMyComponent.render(request=request)\nMyComponent.render(context=RequestContext(request, {}))\n\n# \u274c Without request\nMyComponent.render()\nMyComponent.render(context=Context({}))\n</code></pre>"},{"location":"concepts/fundamentals/http_request/#context-processors","title":"Context Processors","text":"<p>Components support Django's context processors.</p> <p>In regular Django templates, the context processors are applied only when the template is rendered with <code>RequestContext</code>.</p> <p>Components allow you to pass the <code>request</code> object explicitly. Thus, the context processors are applied to components either when:</p> <ul> <li>The component is rendered with <code>RequestContext</code> (Regular Django behavior)</li> <li>The component is rendered with a regular <code>Context</code> (or none), but you set the <code>request</code> kwarg     of <code>Component.render()</code>.</li> <li>The component is nested in another component that matches one of the two conditions above.</li> </ul> <pre><code># \u274c No context processors\nrendered = MyComponent.render()\nrendered = MyComponent.render(Context({}))\n\n# \u2705 With context processors\nrendered = MyComponent.render(request=request)\nrendered = MyComponent.render(Context({}), request=request)\nrendered = MyComponent.render(RequestContext(request, {}))\n</code></pre> <p>When a component is rendered within a template with <code>{% component %}</code> tag, context processors are available depending on whether the template is rendered with <code>RequestContext</code> or not.</p> <pre><code>template = Template(\"\"\"\n&lt;div&gt;\n  {% component \"MyComponent\" / %}\n&lt;/div&gt;\n\"\"\")\n\n# \u274c No context processors\nrendered = template.render(Context({}))\n\n# \u2705 With context processors\nrendered = template.render(RequestContext(request, {}))\n</code></pre>"},{"location":"concepts/fundamentals/http_request/#accessing-context-processors-data","title":"Accessing context processors data","text":"<p>The data from context processors is automatically available within the component's template.</p> <pre><code>class MyComponent(Component):\n    template = \"\"\"\n        &lt;div&gt;\n            {{ csrf_token }}\n        &lt;/div&gt;\n    \"\"\"\n\nMyComponent.render(request=request)\n</code></pre> <p>You can also access the context processors data from within <code>get_context_data()</code> and other methods under <code>Component.context_processors_data</code>.</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        csrf_token = self.context_processors_data['csrf_token']\n        return {\n            'csrf_token': csrf_token,\n        }\n</code></pre>"},{"location":"concepts/fundamentals/single_file_components/","title":"Single-file components","text":"<p>Components can be defined in a single file, which is useful for small components. To do this, you can use the <code>template</code>, <code>js</code>, and <code>css</code> class attributes instead of the <code>template_file</code>, <code>js_file</code>,  and <code>css_file</code>.</p> <p>For example, here's the calendar component from the Getting started tutorial, defined in a single file:</p> [project root]/components/calendar.py<pre><code>from django_components import Component, register, types\n\n@register(\"calendar\")\nclass Calendar(Component):\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n\n    template: types.django_html = \"\"\"\n        &lt;div class=\"calendar\"&gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css: types.css = \"\"\"\n        .calendar {\n            width: 200px;\n            background: pink;\n        }\n        .calendar span {\n            font-weight: bold;\n        }\n    \"\"\"\n\n    js: types.js = \"\"\"\n        (function(){\n            if (document.querySelector(\".calendar\")) {\n                document.querySelector(\".calendar\").onclick = () =&gt; {\n                    alert(\"Clicked calendar!\");\n                };\n            }\n        })()\n    \"\"\"\n</code></pre> <p>This makes it easy to create small components without having to create a separate template, CSS, and JS file.</p> <p>To add syntax highlighting to these snippets, head over to Syntax highlighting.</p>"},{"location":"concepts/fundamentals/slots/","title":"Slots","text":"<p>New in version 0.26:</p> <ul> <li>The <code>slot</code> tag now serves only to declare new slots inside the component template.</li> <li>To override the content of a declared slot, use the newly introduced <code>fill</code> tag instead.</li> <li>Whereas unfilled slots used to raise a warning, filling a slot is now optional by default.</li> <li>To indicate that a slot must be filled, the new <code>required</code> option should be added at the end of the <code>slot</code> tag.</li> </ul> <p>Components support something called 'slots'. When a component is used inside another template, slots allow the parent template to override specific parts of the child component by passing in different content. This mechanism makes components more reusable and composable. This behavior is similar to slots in Vue.</p> <p>In the example below we introduce two block tags that work hand in hand to make this work. These are...</p> <ul> <li><code>{% slot &lt;name&gt; %}</code>/<code>{% endslot %}</code>: Declares a new slot in the component template.</li> <li><code>{% fill &lt;name&gt; %}</code>/<code>{% endfill %}</code>: (Used inside a <code>{% component %}</code> tag pair.) Fills a declared slot with the specified content.</li> </ul> <p>Let's update our calendar component to support more customization. We'll add <code>slot</code> tag pairs to its template, template.html.</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"header\" %}Calendar header{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"body\" %}Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>When using the component, you specify which slots you want to fill and where you want to use the defaults from the template. It looks like this:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"body\" %}\n        Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>Since the 'header' fill is unspecified, it's taken from the base template. If you put this in a template, and pass in <code>date=2020-06-06</code>, this is what gets rendered:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        Calendar header\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        Can you believe it's already &lt;span&gt;2020-06-06&lt;/span&gt;??\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/slots/#named-slots","title":"Named slots","text":"<p>As seen in the previouse section, you can use <code>{% fill slot_name %}</code> to insert content into a specific slot.</p> <p>You can define fills for multiple slot simply by defining them all within the <code>{% component %} {% endcomponent %}</code> tags:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"header\" %}\n        Hi this is header!\n    {% endfill %}\n    {% fill \"body\" %}\n        Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>You can also use <code>{% for %}</code>, <code>{% with %}</code>, or other non-component tags (even <code>{% include %}</code>) to construct the <code>{% fill %}</code> tags, as long as these other tags do not leave any text behind!</p> <pre><code>{% component \"table\" %}\n  {% for slot_name in slots %}\n    {% fill name=slot_name %}\n      {{ slot_name }}\n    {% endfill %}\n  {% endfor %}\n\n  {% with slot_name=\"abc\" %}\n    {% fill name=slot_name %}\n      {{ slot_name }}\n    {% endfill %}\n  {% endwith %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#default-slot","title":"Default slot","text":"<p>Added in version 0.28</p> <p>As you can see, component slots lets you write reusable containers that you fill in when you use a component. This makes for highly reusable components that can be used in different circumstances.</p> <p>It can become tedious to use <code>fill</code> tags everywhere, especially when you're using a component that declares only one slot. To make things easier, <code>slot</code> tags can be marked with an optional keyword: <code>default</code>.</p> <p>When added to the tag (as shown below), this option lets you pass filling content directly in the body of a <code>component</code> tag pair \u2013 without using a <code>fill</code> tag. Choose carefully, though: a component template may contain at most one slot that is marked as <code>default</code>. The <code>default</code> option can be combined with other slot options, e.g. <code>required</code>.</p> <p>Here's the same example as before, except with default slots and implicit filling.</p> <p>The template:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"header\" %}Calendar header{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"body\" default %}Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>Including the component (notice how the <code>fill</code> tag is omitted):</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n{% endcomponent %}\n</code></pre> <p>The rendered result (exactly the same as before):</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n  &lt;div class=\"header\"&gt;Calendar header&lt;/div&gt;\n  &lt;div class=\"body\"&gt;Can you believe it's already &lt;span&gt;2020-06-06&lt;/span&gt;??&lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>You may be tempted to combine implicit fills with explicit <code>fill</code> tags. This will not work. The following component template will raise an error when rendered.</p> <pre><code>{# DON'T DO THIS #}\n{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"header\" %}Totally new header!{% endfill %}\n    Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n{% endcomponent %}\n</code></pre> <p>Instead, you can use a named fill with name <code>default</code> to target the default fill:</p> <pre><code>{# THIS WORKS #}\n{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"header\" %}Totally new header!{% endfill %}\n    {% fill \"default\" %}\n        Can you believe it's already &lt;span&gt;{{ date }}&lt;/span&gt;??\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>NOTE: If you doubly-fill a slot, that is, that both <code>{% fill \"default\" %}</code> and <code>{% fill \"header\" %}</code> would point to the same slot, this will raise an error when rendered.</p>"},{"location":"concepts/fundamentals/slots/#accessing-default-slot-in-python","title":"Accessing default slot in Python","text":"<p>Since the default slot is stored under the slot name <code>default</code>, you can access the default slot like so:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        default_slot = self.input.slots[\"default\"]\n        return {\n            \"default_slot\": default_slot,\n        }\n</code></pre>"},{"location":"concepts/fundamentals/slots/#render-fill-in-multiple-places","title":"Render fill in multiple places","text":"<p>Added in version 0.70</p> <p>You can render the same content in multiple places by defining multiple slots with identical names:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"image\" %}Image here{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"image\" %}Image here{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>So if used like:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"image\" %}\n        &lt;img src=\"...\" /&gt;\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>This renders:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        &lt;img src=\"...\" /&gt;\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        &lt;img src=\"...\" /&gt;\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/slots/#default-and-required-slots","title":"Default and required slots","text":"<p>If you use a slot multiple times, you can still mark the slot as <code>default</code> or <code>required</code>. For that, you must mark each slot individually, e.g.:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        {% slot \"image\" default required %}Image here{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        {% slot \"image\" default required %}Image here{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>Which you can then use as regular default slot:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    &lt;img src=\"...\" /&gt;\n{% endcomponent %}\n</code></pre> <p>Since each slot is tagged individually, you can have multiple slots with the same name but different conditions.</p> <p>E.g. in this example, we have a component that renders a user avatar - a small circular image with a profile picture or name initials.</p> <p>If the component is given <code>image_src</code> or <code>name_initials</code> variables, the <code>image</code> slot is optional. But if neither of those are provided, you MUST fill the <code>image</code> slot.</p> <pre><code>&lt;div class=\"avatar\"&gt;\n    {% if image_src %}\n        {% slot \"image\" default %}\n            &lt;img src=\"{{ image_src }}\" /&gt;\n        {% endslot %}\n    {% elif name_initials %}\n        {% slot \"image\" default %}\n            &lt;div style=\"\n                border-radius: 25px;\n                width: 50px;\n                height: 50px;\n                background: blue;\n            \"&gt;\n                {{ name_initials }}\n            &lt;/div&gt;\n        {% endslot %}\n    {% else %}\n        {% slot \"image\" default required / %}\n    {% endif %}\n&lt;/div&gt;\n</code></pre>"},{"location":"concepts/fundamentals/slots/#accessing-original-content-of-slots","title":"Accessing original content of slots","text":"<p>Added in version 0.26</p> <p>NOTE: In version 0.77, the syntax was changed from</p> <pre><code>{% fill \"my_slot\" as \"alias\" %} {{ alias.default }}\n</code></pre> <p>to</p> <pre><code>{% fill \"my_slot\" default=\"slot_default\" %} {{ slot_default }}\n</code></pre> <p>Sometimes you may want to keep the original slot, but only wrap or prepend/append content to it. To do so, you can access the default slot via the <code>default</code> kwarg.</p> <p>Similarly to the <code>data</code> attribute, you specify the variable name through which the default slot will be made available.</p> <p>For instance, let's say you're filling a slot called 'body'. To render the original slot, assign it to a variable using the <code>'default'</code> keyword. You then render this variable to insert the default content:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"body\" default=\"body_default\" %}\n        {{ body_default }}. Have a great day!\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>This produces:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n    &lt;div class=\"header\"&gt;\n        Calendar header\n    &lt;/div&gt;\n    &lt;div class=\"body\"&gt;\n        Today's date is &lt;span&gt;2020-06-06&lt;/span&gt;. Have a great day!\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>To access the original content of a default slot, set the name to <code>default</code>:</p> <pre><code>{% component \"calendar\" date=\"2020-06-06\" %}\n    {% fill \"default\" default=\"slot_default\" %}\n        {{ slot_default }}. Have a great day!\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#conditional-slots","title":"Conditional slots","text":"<p>Added in version 0.26.</p> <p>NOTE: In version 0.70, <code>{% if_filled %}</code> tags were replaced with <code>{{ component_vars.is_filled }}</code> variables. If your slot name contained special characters, see the section Accessing <code>is_filled</code> of slot names with special characters.</p> <p>In certain circumstances, you may want the behavior of slot filling to depend on whether or not a particular slot is filled.</p> <p>For example, suppose we have the following component template:</p> <pre><code>&lt;div class=\"frontmatter-component\"&gt;\n    &lt;div class=\"title\"&gt;\n        {% slot \"title\" %}Title{% endslot %}\n    &lt;/div&gt;\n    &lt;div class=\"subtitle\"&gt;\n        {% slot \"subtitle\" %}{# Optional subtitle #}{% endslot %}\n    &lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>By default the slot named 'subtitle' is empty. Yet when the component is used without explicit fills, the div containing the slot is still rendered, as shown below:</p> <pre><code>&lt;div class=\"frontmatter-component\"&gt;\n  &lt;div class=\"title\"&gt;Title&lt;/div&gt;\n  &lt;div class=\"subtitle\"&gt;&lt;/div&gt;\n&lt;/div&gt;\n</code></pre> <p>This may not be what you want. What if instead the outer 'subtitle' div should only be included when the inner slot is in fact filled?</p> <p>The answer is to use the <code>{{ component_vars.is_filled.&lt;name&gt; }}</code> variable. You can use this together with Django's <code>{% if/elif/else/endif %}</code> tags to define a block whose contents will be rendered only if the component slot with the corresponding 'name' is filled.</p> <p>This is what our example looks like with <code>component_vars.is_filled</code>.</p> <pre><code>&lt;div class=\"frontmatter-component\"&gt;\n    &lt;div class=\"title\"&gt;\n        {% slot \"title\" %}Title{% endslot %}\n    &lt;/div&gt;\n    {% if component_vars.is_filled.subtitle %}\n    &lt;div class=\"subtitle\"&gt;\n        {% slot \"subtitle\" %}{# Optional subtitle #}{% endslot %}\n    &lt;/div&gt;\n    {% endif %}\n&lt;/div&gt;\n</code></pre> <p>Here's our example with more complex branching.</p> <pre><code>&lt;div class=\"frontmatter-component\"&gt;\n    &lt;div class=\"title\"&gt;\n        {% slot \"title\" %}Title{% endslot %}\n    &lt;/div&gt;\n    {% if component_vars.is_filled.subtitle %}\n    &lt;div class=\"subtitle\"&gt;\n        {% slot \"subtitle\" %}{# Optional subtitle #}{% endslot %}\n    &lt;/div&gt;\n    {% elif component_vars.is_filled.title %}\n        ...\n    {% elif component_vars.is_filled.&lt;name&gt; %}\n        ...\n    {% endif %}\n&lt;/div&gt;\n</code></pre> <p>Sometimes you're not interested in whether a slot is filled, but rather that it isn't. To negate the meaning of <code>component_vars.is_filled</code>, simply treat it as boolean and negate it with <code>not</code>:</p> <pre><code>{% if not component_vars.is_filled.subtitle %}\n&lt;div class=\"subtitle\"&gt;\n    {% slot \"subtitle\" / %}\n&lt;/div&gt;\n{% endif %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#accessing-is_filled-of-slot-names-with-special-characters","title":"Accessing <code>is_filled</code> of slot names with special characters","text":"<p>To be able to access a slot name via <code>component_vars.is_filled</code>, the slot name needs to be composed of only alphanumeric characters and underscores (e.g. <code>this__isvalid_123</code>).</p> <p>However, you can still define slots with other special characters. In such case, the slot name in <code>component_vars.is_filled</code> is modified to replace all invalid characters into <code>_</code>.</p> <p>So a slot named <code>\"my super-slot :)\"</code> will be available as <code>component_vars.is_filled.my_super_slot___</code>.</p> <p>Same applies when you are accessing <code>is_filled</code> from within the Python, e.g.:</p> <pre><code>class MyTable(Component):\n    def on_render_before(self, context, template) -&gt; None:\n        # \u2705 Works\n        if self.is_filled[\"my_super_slot___\"]:\n            # Do something\n\n        # \u274c Does not work\n        if self.is_filled[\"my super-slot :)\"]:\n            # Do something\n</code></pre>"},{"location":"concepts/fundamentals/slots/#conditional-fills","title":"Conditional fills","text":"<p>Similarly, you can use <code>{% if %}</code> and <code>{% for %}</code> when defining the <code>{% fill %}</code> tags, to conditionally fill the slots when using the componnet:</p> <p>In the example below, the <code>{% fill \"footer\" %}</code> fill is used only if the condition is true. If falsy, the fill is ignored, and so the <code>my_table</code> component will use its default content for the <code>footer</code> slot.</p> <pre><code>{% component \"my_table\" %}\n    {% if editable %}\n        {% fill \"footer\" %}\n            &lt;input name=\"name\" /&gt;\n        {% endfill %}\n    {% endif %}\n{% endcomponent %}\n</code></pre> <p>You can even combine <code>{% if %}</code> and <code>{% for %}</code>:</p> <pre><code>{% component \"my_table\" %}\n    {% for header in headers %}\n        {% if header != \"hyperlink\" %}\n            {# Generate fill name like `header.my_column` #}\n            {% fill name=\"header.\"|add:header\" %}\n                &lt;b&gt;{{ header }}&lt;/b&gt;\n            {% endfill %}\n        {% endif %}\n    {% endfor %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#scoped-slots","title":"Scoped slots","text":"<p>Added in version 0.76:</p> <p>Consider a component with slot(s). This component may do some processing on the inputs, and then use the processed variable in the slot's default template:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        &lt;div&gt;\n            {% slot \"content\" default %}\n                input: {{ input }}\n            {% endslot %}\n        &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self, input):\n        processed_input = do_something(input)\n        return {\"input\": processed_input}\n</code></pre> <p>You may want to design a component so that users of your component can still access the <code>input</code> variable, so they don't have to recompute it.</p> <p>This behavior is called \"scoped slots\". This is inspired by Vue scoped slots and scoped slots of django-web-components.</p> <p>Using scoped slots consists of two steps:</p> <ol> <li>Passing data to <code>slot</code> tag</li> <li>Accessing data in <code>fill</code> tag</li> </ol>"},{"location":"concepts/fundamentals/slots/#passing-data-to-slots","title":"Passing data to slots","text":"<p>To pass the data to the <code>slot</code> tag, simply pass them as keyword attributes (<code>key=value</code>):</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        &lt;div&gt;\n            {% slot \"content\" default input=input %}\n                input: {{ input }}\n            {% endslot %}\n        &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self, input):\n        processed_input = do_something(input)\n        return {\n            \"input\": processed_input,\n        }\n</code></pre>"},{"location":"concepts/fundamentals/slots/#accessing-slot-data-in-fill","title":"Accessing slot data in fill","text":"<p>Next, we head over to where we define a fill for this slot. Here, to access the slot data we set the <code>data</code> attribute to the name of the variable through which we want to access the slot data. In the example below, we set it to <code>data</code>:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"content\" data=\"slot_data\" %}\n        {{ slot_data.input }}\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>To access slot data on a default slot, you have to explictly define the <code>{% fill %}</code> tags.</p> <p>So this works:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"content\" data=\"slot_data\" %}\n        {{ slot_data.input }}\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>While this does not:</p> <pre><code>{% component \"my_comp\" data=\"data\" %}\n    {{ data.input }}\n{% endcomponent %}\n</code></pre> <p>Note: You cannot set the <code>data</code> attribute and <code>default</code> attribute) to the same name. This raises an error:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"content\" data=\"slot_var\" default=\"slot_var\" %}\n        {{ slot_var.input }}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#slot-data-of-default-slots","title":"Slot data of default slots","text":"<p>To access data of a default slot, you can specify <code>{% fill name=\"default\" %}</code>:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"default\" data=\"slot_data\" %}\n        {{ slot_data.input }}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#dynamic-slots-and-fills","title":"Dynamic slots and fills","text":"<p>Until now, we were declaring slot and fill names statically, as a string literal, e.g.</p> <pre><code>{% slot \"content\" / %}\n</code></pre> <p>However, sometimes you may want to generate slots based on the given input. One example of this is a table component like that of Vuetify, which creates a header and an item slots for each user-defined column.</p> <p>In django_components you can achieve the same, simply by using a variable (or a template expression) instead of a string literal:</p> <pre><code>&lt;table&gt;\n  &lt;tr&gt;\n    {% for header in headers %}\n      &lt;th&gt;\n        {% slot \"header-{{ header.key }}\" value=header.title %}\n          {{ header.title }}\n        {% endslot %}\n      &lt;/th&gt;\n    {% endfor %}\n  &lt;/tr&gt;\n&lt;/table&gt;\n</code></pre> <p>When using the component, you can either set the fill explicitly:</p> <pre><code>{% component \"table\" headers=headers items=items %}\n  {% fill \"header-name\" data=\"data\" %}\n    &lt;b&gt;{{ data.value }}&lt;/b&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <p>Or also use a variable:</p> <pre><code>{% component \"table\" headers=headers items=items %}\n  {# Make only the active column bold #}\n  {% fill \"header-{{ active_header_name }}\" data=\"data\" %}\n    &lt;b&gt;{{ data.value }}&lt;/b&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <p>NOTE: It's better to use static slot names whenever possible for clarity. The dynamic slot names should be reserved for advanced use only.</p> <p>Lastly, in rare cases, you can also pass the slot name via the spread operator. This is possible, because the slot name argument is actually a shortcut for a <code>name</code> keyword argument.</p> <p>So this:</p> <pre><code>{% slot \"content\" / %}\n</code></pre> <p>is the same as:</p> <pre><code>{% slot name=\"content\" / %}\n</code></pre> <p>So it's possible to define a <code>name</code> key on a dictionary, and then spread that onto the slot tag:</p> <pre><code>{# slot_props = {\"name\": \"content\"} #}\n{% slot ...slot_props / %}\n</code></pre>"},{"location":"concepts/fundamentals/slots/#pass-through-all-the-slots","title":"Pass through all the slots","text":"<p>You can dynamically pass all slots to a child component. This is similar to passing all slots in Vue:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"slots\": self.input.slots,\n        }\n\n    template = \"\"\"\n    &lt;div&gt;\n      {% component \"child\" %}\n        {% for slot_name in slots %}\n          {% fill name=slot_name data=\"data\" %}\n            {% slot name=slot_name ...data / %}\n          {% endfill %}\n        {% endfor %}\n      {% endcomponent %}\n    &lt;/div&gt;\n    \"\"\"\n</code></pre>"},{"location":"concepts/fundamentals/subclassing_components/","title":"Subclassing components","text":"<p>In larger projects, you might need to write multiple components with similar behavior. In such cases, you can extract shared behavior into a standalone component class to keep things DRY.</p> <p>When subclassing a component, there's a couple of things to keep in mind:</p>"},{"location":"concepts/fundamentals/subclassing_components/#template-js-and-css-inheritance","title":"Template, JS, and CSS Inheritance","text":"<p>When it comes to the pairs:</p> <ul> <li><code>Component.template</code>/<code>Component.template_file</code></li> <li><code>Component.js</code>/<code>Component.js_file</code></li> <li><code>Component.css</code>/<code>Component.css_file</code></li> </ul> <p>inheritance follows these rules:</p> <ul> <li>If a child component class defines either member of a pair (e.g., either <code>template</code> or <code>template_file</code>), it takes precedence and the parent's definition is ignored completely.</li> <li>For example, if a child component defines <code>template_file</code>, the parent's <code>template</code> or <code>template_file</code> will be ignored.</li> <li>This applies independently to each pair - you can inherit the JS while overriding the template, for instance.</li> </ul> <p>For example:</p> <pre><code>class BaseCard(Component):\n    template = \"\"\"\n        &lt;div class=\"card\"&gt;\n            &lt;div class=\"card-content\"&gt;{{ content }}&lt;/div&gt;\n        &lt;/div&gt;\n    \"\"\"\n    css = \"\"\"\n        .card {\n            border: 1px solid gray;\n        }\n    \"\"\"\n    js = \"\"\"console.log('Base card loaded');\"\"\"\n\n# This class overrides parent's template, but inherits CSS and JS\nclass SpecialCard(BaseCard):\n    template = \"\"\"\n        &lt;div class=\"card special\"&gt;\n            &lt;div class=\"card-content\"&gt;\u2728 {{ content }} \u2728&lt;/div&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n# This class overrides parent's template and CSS, but inherits JS\nclass CustomCard(BaseCard):\n    template_file = \"custom_card.html\"\n    css = \"\"\"\n        .card {\n            border: 2px solid gold;\n        }\n    \"\"\"\n</code></pre>"},{"location":"concepts/fundamentals/subclassing_components/#media-class-inheritance","title":"Media Class Inheritance","text":"<p>The <code>Component.Media</code> nested class follows Django's media inheritance rules:</p> <ul> <li>If both parent and child define a <code>Media</code> class, the child's media will automatically include both its own and the parent's JS and CSS files.</li> <li>This behavior can be configured using the <code>extend</code> attribute in the Media class, similar to Django's forms.   Read more on this in Controlling Media Inheritance.</li> </ul> <p>For example:</p> <pre><code>class BaseModal(Component):\n    template = \"&lt;div&gt;Modal content&lt;/div&gt;\"\n\n    class Media:\n        css = [\"base_modal.css\"]\n        js = [\"base_modal.js\"]  # Contains core modal functionality\n\nclass FancyModal(BaseModal):\n    class Media:\n        # Will include both base_modal.css/js AND fancy_modal.css/js\n        css = [\"fancy_modal.css\"]  # Additional styling\n        js = [\"fancy_modal.js\"]    # Additional animations\n\nclass SimpleModal(BaseModal):\n    class Media:\n        extend = False  # Don't inherit parent's media\n        css = [\"simple_modal.css\"]  # Only this CSS will be included\n        js = [\"simple_modal.js\"]    # Only this JS will be included\n</code></pre>"},{"location":"concepts/fundamentals/subclassing_components/#regular-python-inheritance","title":"Regular Python Inheritance","text":"<p>All other attributes and methods (including the <code>Component.View</code> class and its methods) follow standard Python inheritance rules.</p> <p>For example:</p> <pre><code>class BaseForm(Component):\n    template = \"\"\"\n        &lt;form&gt;\n            {{ form_content }}\n            &lt;button type=\"submit\"&gt;\n                {{ submit_text }}\n            &lt;/button&gt;\n        &lt;/form&gt;\n    \"\"\"\n\n    def get_context_data(self, **kwargs):\n        return {\n            \"form_content\": self.get_form_content(),\n            \"submit_text\": \"Submit\"\n        }\n\n    def get_form_content(self):\n        return \"&lt;input type='text' name='data'&gt;\"\n\nclass ContactForm(BaseForm):\n    # Extend parent's \"context\"\n    # but override \"submit_text\"\n    def get_context_data(self, **kwargs):\n        context = super().get_context_data(**kwargs)\n        context[\"submit_text\"] = \"Send Message\"  \n        return context\n\n    # Completely override parent's get_form_content\n    def get_form_content(self):\n        return \"\"\"\n            &lt;input type='text' name='name' placeholder='Your Name'&gt;\n            &lt;input type='email' name='email' placeholder='Your Email'&gt;\n            &lt;textarea name='message' placeholder='Your Message'&gt;&lt;/textarea&gt;\n        \"\"\"\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/","title":"Template tag syntax","text":"<p>All template tags in django_component, like <code>{% component %}</code> or <code>{% slot %}</code>, and so on, support extra syntax that makes it possible to write components like in Vue or React (JSX).</p>"},{"location":"concepts/fundamentals/template_tag_syntax/#self-closing-tags","title":"Self-closing tags","text":"<p>When you have a tag like <code>{% component %}</code> or <code>{% slot %}</code>, but it has no content, you can simply append a forward slash <code>/</code> at the end, instead of writing out the closing tags like <code>{% endcomponent %}</code> or <code>{% endslot %}</code>:</p> <p>So this:</p> <pre><code>{% component \"button\" %}{% endcomponent %}\n</code></pre> <p>becomes</p> <pre><code>{% component \"button\" / %}\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/#special-characters","title":"Special characters","text":"<p>New in version 0.71:</p> <p>Keyword arguments can contain special characters <code># @ . - _</code>, so keywords like so are still valid:</p> <pre><code>&lt;body&gt;\n    {% component \"calendar\" my-date=\"2015-06-19\" @click.native=do_something #some_id=True / %}\n&lt;/body&gt;\n</code></pre> <p>These can then be accessed inside <code>get_context_data</code> so:</p> <pre><code>@register(\"calendar\")\nclass Calendar(Component):\n    # Since # . @ - are not valid identifiers, we have to\n    # use `**kwargs` so the method can accept these args.\n    def get_context_data(self, **kwargs):\n        return {\n            \"date\": kwargs[\"my-date\"],\n            \"id\": kwargs[\"#some_id\"],\n            \"on_click\": kwargs[\"@click.native\"]\n        }\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/#spread-operator","title":"Spread operator","text":"<p>New in version 0.93:</p> <p>Instead of passing keyword arguments one-by-one:</p> <pre><code>{% component \"calendar\" title=\"How to abc\" date=\"2015-06-19\" author=\"John Wick\" / %}\n</code></pre> <p>You can use a spread operator <code>...dict</code> to apply key-value pairs from a dictionary:</p> <pre><code>post_data = {\n    \"title\": \"How to...\",\n    \"date\": \"2015-06-19\",\n    \"author\": \"John Wick\",\n}\n</code></pre> <pre><code>{% component \"calendar\" ...post_data / %}\n</code></pre> <p>This behaves similar to JSX's spread operator or Vue's <code>v-bind</code>.</p> <p>Spread operators are treated as keyword arguments, which means that:</p> <ol> <li>Spread operators must come after positional arguments.</li> <li>You cannot use spread operators for positional-only arguments.</li> </ol> <p>Other than that, you can use spread operators multiple times, and even put keyword arguments in-between or after them:</p> <pre><code>{% component \"calendar\" ...post_data id=post.id ...extra / %}\n</code></pre> <p>In a case of conflicts, the values added later (right-most) overwrite previous values.</p>"},{"location":"concepts/fundamentals/template_tag_syntax/#use-template-tags-inside-component-inputs","title":"Use template tags inside component inputs","text":"<p>New in version 0.93</p> <p>When passing data around, sometimes you may need to do light transformations, like negating booleans or filtering lists.</p> <p>Normally, what you would have to do is to define ALL the variables inside <code>get_context_data()</code>. But this can get messy if your components contain a lot of logic.</p> <pre><code>@register(\"calendar\")\nclass Calendar(Component):\n    def get_context_data(self, id: str, editable: bool):\n        return {\n            \"editable\": editable,\n            \"readonly\": not editable,\n            \"input_id\": f\"input-{id}\",\n            \"icon_id\": f\"icon-{id}\",\n            ...\n        }\n</code></pre> <p>Instead, template tags in django_components (<code>{% component %}</code>, <code>{% slot %}</code>, <code>{% provide %}</code>, etc) allow you to treat literal string values as templates:</p> <pre><code>{% component 'blog_post'\n  \"As positional arg {# yay #}\"\n  title=\"{{ person.first_name }} {{ person.last_name }}\"\n  id=\"{% random_int 10 20 %}\"\n  readonly=\"{{ editable|not }}\"\n  author=\"John Wick {# TODO: parametrize #}\"\n/ %}\n</code></pre> <p>In the example above:</p> <ul> <li>Component <code>test</code> receives a positional argument with value <code>\"As positional arg \"</code>. The comment is omitted.</li> <li>Kwarg <code>title</code> is passed as a string, e.g. <code>John Doe</code></li> <li>Kwarg <code>id</code> is passed as <code>int</code>, e.g. <code>15</code></li> <li>Kwarg <code>readonly</code> is passed as <code>bool</code>, e.g. <code>False</code></li> <li>Kwarg <code>author</code> is passed as a string, e.g. <code>John Wick</code> (Comment omitted)</li> </ul> <p>This is inspired by django-cotton.</p>"},{"location":"concepts/fundamentals/template_tag_syntax/#passing-data-as-string-vs-original-values","title":"Passing data as string vs original values","text":"<p>Sometimes you may want to use the template tags to transform or generate the data that is then passed to the component.</p> <p>The data doesn't necessarily have to be strings. In the example above, the kwarg <code>id</code> was passed as an integer, NOT a string.</p> <p>Although the string literals for components inputs are treated as regular Django templates, there is one special case:</p> <p>When the string literal contains only a single template tag, with no extra text, then the value is passed as the original type instead of a string.</p> <p>Here, <code>page</code> is an integer:</p> <pre><code>{% component 'blog_post' page=\"{% random_int 10 20 %}\" / %}\n</code></pre> <p>Here, <code>page</code> is a string:</p> <pre><code>{% component 'blog_post' page=\" {% random_int 10 20 %} \" / %}\n</code></pre> <p>And same applies to the <code>{{ }}</code> variable tags:</p> <p>Here, <code>items</code> is a list:</p> <pre><code>{% component 'cat_list' items=\"{{ cats|slice:':2' }}\" / %}\n</code></pre> <p>Here, <code>items</code> is a string:</p> <pre><code>{% component 'cat_list' items=\"{{ cats|slice:':2' }} See more\" / %}\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/#evaluating-python-expressions-in-template","title":"Evaluating Python expressions in template","text":"<p>You can even go a step further and have a similar experience to Vue or React, where you can evaluate arbitrary code expressions:</p> <pre><code>&lt;MyForm value={isEnabled ? inputValue : null} /&gt;\n</code></pre> <p>Similar is possible with <code>django-expr</code>, which adds an <code>expr</code> tag and filter that you can use to evaluate Python expressions from within the template:</p> <pre><code>{% component \"my_form\"\n  value=\"{% expr 'input_value if is_enabled else None' %}\"\n/ %}\n</code></pre> <p>Note: Never use this feature to mix business logic and template logic. Business logic should still be in the view!</p>"},{"location":"concepts/fundamentals/template_tag_syntax/#pass-dictonary-by-its-key-value-pairs","title":"Pass dictonary by its key-value pairs","text":"<p>New in version 0.74:</p> <p>Sometimes, a component may expect a dictionary as one of its inputs.</p> <p>Most commonly, this happens when a component accepts a dictionary of HTML attributes (usually called <code>attrs</code>) to pass to the underlying template.</p> <p>In such cases, we may want to define some HTML attributes statically, and other dynamically. But for that, we need to define this dictionary on Python side:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        {% component \"other\" attrs=attrs / %}\n    \"\"\"\n\n    def get_context_data(self, some_id: str):\n        attrs = {\n            \"class\": \"pa-4 flex\",\n            \"data-some-id\": some_id,\n            \"@click.stop\": \"onClickHandler\",\n        }\n        return {\"attrs\": attrs}\n</code></pre> <p>But as you can see in the case above, the event handler <code>@click.stop</code> and styling <code>pa-4 flex</code> are disconnected from the template. If the component grew in size and we moved the HTML to a separate file, we would have hard time reasoning about the component's template.</p> <p>Luckily, there's a better way.</p> <p>When we want to pass a dictionary to a component, we can define individual key-value pairs as component kwargs, so we can keep all the relevant information in the template. For that, we prefix the key with the name of the dict and <code>:</code>. So key <code>class</code> of input <code>attrs</code> becomes <code>attrs:class</code>. And our example becomes:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        {% component \"other\"\n            attrs:class=\"pa-4 flex\"\n            attrs:data-some-id=some_id\n            attrs:@click.stop=\"onClickHandler\"\n        / %}\n    \"\"\"\n\n    def get_context_data(self, some_id: str):\n        return {\"some_id\": some_id}\n</code></pre> <p>Sweet! Now all the relevant HTML is inside the template, and we can move it to a separate file with confidence:</p> <pre><code>{% component \"other\"\n    attrs:class=\"pa-4 flex\"\n    attrs:data-some-id=some_id\n    attrs:@click.stop=\"onClickHandler\"\n/ %}\n</code></pre> <p>Note: It is NOT possible to define nested dictionaries, so <code>attrs:my_key:two=2</code> would be interpreted as:</p> <pre><code>{\"attrs\": {\"my_key:two\": 2}}\n</code></pre>"},{"location":"concepts/fundamentals/template_tag_syntax/#multiline-tags","title":"Multiline tags","text":"<p>By default, Django expects a template tag to be defined on a single line.</p> <p>However, this can become unwieldy if you have a component with a lot of inputs:</p> <pre><code>{% component \"card\" title=\"Joanne Arc\" subtitle=\"Head of Kitty Relations\" date_last_active=\"2024-09-03\" ... %}\n</code></pre> <p>Instead, when you install django_components, it automatically configures Django to suport multi-line tags.</p> <p>So we can rewrite the above as:</p> <pre><code>{% component \"card\"\n    title=\"Joanne Arc\"\n    subtitle=\"Head of Kitty Relations\"\n    date_last_active=\"2024-09-03\"\n    ...\n%}\n</code></pre> <p>Much better!</p> <p>To disable this behavior, set <code>COMPONENTS.multiline_tag</code> to <code>False</code></p>"},{"location":"getting_started/adding_js_and_css/","title":"Adding JS and CSS","text":"<p>Next we will add CSS and JavaScript to our template.</p> <p>Info</p> <p>In django-components, using JS and CSS is as simple as defining them on the Component class. You don't have to insert the <code>&lt;script&gt;</code> and <code>&lt;link&gt;</code> tags into the HTML manually.</p> <p>Behind the scenes, django-components keeps track of which components use which JS and CSS files. Thus, when a component is rendered on the page, the page will contain only the JS and CSS used by the components, and nothing more!</p>"},{"location":"getting_started/adding_js_and_css/#1-update-project-structure","title":"1. Update project structure","text":"<p>Start by creating empty <code>calendar.js</code> and <code>calendar.css</code> files:</p> <pre><code>sampleproject/\n\u251c\u2500\u2500 calendarapp/\n\u251c\u2500\u2500 components/\n\u2502   \u2514\u2500\u2500 calendar/\n\u2502       \u251c\u2500\u2500 calendar.py\n\u2502       \u251c\u2500\u2500 calendar.js       \ud83c\udd95\n\u2502       \u251c\u2500\u2500 calendar.css      \ud83c\udd95\n\u2502       \u2514\u2500\u2500 calendar.html\n\u251c\u2500\u2500 sampleproject/\n\u251c\u2500\u2500 manage.py\n\u2514\u2500\u2500 requirements.txt\n</code></pre>"},{"location":"getting_started/adding_js_and_css/#2-write-css","title":"2. Write CSS","text":"<p>Inside <code>calendar.css</code>, write:</p> [project root]/components/calendar/calendar.css<pre><code>.calendar {\n  width: 200px;\n  background: pink;\n}\n.calendar span {\n  font-weight: bold;\n}\n</code></pre> <p>Be sure to prefix your rules with unique CSS class like <code>calendar</code>, so the CSS doesn't clash with other rules.</p> <p>Note</p> <p>Soon, django-components will automatically scope your CSS by default, so you won't have to worry about CSS class clashes.</p> <p>This CSS will be inserted into the page as an inlined <code>&lt;style&gt;</code> tag, at the position defined by <code>{% component_css_dependencies %}</code>, or at the end of the inside the <code>&lt;head&gt;</code> tag (See JS and CSS output locations).</p> <p>So in your HTML, you may see something like this:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n    &lt;style&gt;\n      .calendar {\n        width: 200px;\n        background: pink;\n      }\n      .calendar span {\n        font-weight: bold;\n      }\n    &lt;/style&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    ...\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre>"},{"location":"getting_started/adding_js_and_css/#3-write-js","title":"3. Write JS","text":"<p>Next we write a JavaScript file that specifies how to interact with this component.</p> <p>You are free to use any javascript framework you want.</p> [project root]/components/calendar/calendar.js<pre><code>(function () {\n  document.querySelector(\".calendar\").onclick = () =&gt; {\n    alert(\"Clicked calendar!\");\n  };\n})();\n</code></pre> <p>A good way to make sure the JS of this component doesn't clash with other components is to define all JS code inside an anonymous self-invoking function (<code>(() =&gt; { ... })()</code>). This makes all variables defined only be defined inside this component and not affect other components.</p> <p>Note</p> <p>Soon, django-components will automatically wrap your JS in a self-invoking function by default (except for JS defined with <code>&lt;script type=\"module\"&gt;</code>).</p> <p>Similarly to CSS, JS will be inserted into the page as an inlined <code>&lt;script&gt;</code> tag, at the position defined by <code>{% component_js_dependencies %}</code>, or at the end of the inside the <code>&lt;body&gt;</code> tag (See JS and CSS output locations).</p> <p>So in your HTML, you may see something like this:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n  &lt;/head&gt;\n  &lt;body&gt;\n    ...\n    &lt;script&gt;\n      (function () {\n        document.querySelector(\".calendar\").onclick = () =&gt; {\n          alert(\"Clicked calendar!\");\n        };\n      })();\n    &lt;/script&gt;\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre>"},{"location":"getting_started/adding_js_and_css/#rules-of-js-execution","title":"Rules of JS execution","text":"<ol> <li> <p>JS is executed in the order in which the components are found in the HTML</p> <p>By default, the JS is inserted as a synchronous script (<code>&lt;script&gt; ... &lt;/script&gt;</code>)</p> <p>So if you define multiple components on the same page, their JS will be executed in the order in which the components are found in the HTML.</p> <p>So if we have a template like so:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component \"calendar\" / %}\n    {% component \"table\" / %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre> <p>Then the JS file of the component <code>calendar</code> will be executed first, and the JS file of component <code>table</code> will be executed second.</p> </li> <li> <p>JS will be executed only once, even if there is multiple instances of the same component</p> <p>In this case, the JS of <code>calendar</code> will STILL execute first (because it was found first), and will STILL execute only once, even though it's present twice:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component \"calendar\" / %}\n    {% component \"table\" / %}\n    {% component \"calendar\" / %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre> </li> </ol>"},{"location":"getting_started/adding_js_and_css/#4-link-js-and-css-to-a-component","title":"4. Link JS and CSS to a component","text":"<p>Finally, we return to our Python component in <code>calendar.py</code> to tie this together.</p> <p>To link JS and CSS defined in other files, use <code>js_file</code> and <code>css_file</code> attributes:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"   # &lt;--- new\n    css_file = \"calendar.css\"   # &lt;--- new\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>And that's it! If you were to embed this component in an HTML, django-components will automatically embed the associated JS and CSS.</p> <p>Note</p> <p>Similarly to the template file, the JS and CSS file paths can be either:</p> <ol> <li>Relative to the Python component file (as seen above),</li> <li>Relative to any of the component directories as defined by <code>COMPONENTS.dirs</code> and/or <code>COMPONENTS.app_dirs</code> (e.g. <code>[your apps]/components</code> dir and <code>[project root]/components</code>)</li> <li>Relative to any of the directories defined by <code>STATICFILES_DIRS</code>.</li> </ol>"},{"location":"getting_started/adding_js_and_css/#5-link-additional-js-and-css-to-a-component","title":"5. Link additional JS and CSS to a component","text":"<p>Your components may depend on third-party packages or styling, or other shared logic. To load these additional dependencies, you can use a nested <code>Media</code> class.</p> <p>This <code>Media</code> class behaves similarly to Django's Media class, with a few differences:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list, or (CSS-only) a dictonary (see below).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>, <code>SafeString</code>, or a function.</li> <li>Individual JS / CSS files can be glob patterns, e.g. <code>*.js</code> or <code>styles/**/*.css</code>.</li> <li>If you set <code>Media.extend</code> to a list,    it should be a list of <code>Component</code> classes.</li> </ol> <p>Learn more about using Media.</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    class Media:   # &lt;--- new\n        js = [\n            \"path/to/shared.js\",\n            \"path/to/*.js\",  # Or as a glob\n            \"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\",  # AlpineJS\n        ]\n        css = [\n            \"path/to/shared.css\",\n            \"path/to/*.css\",  # Or as a glob\n            \"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\",  # Tailwind\n        ]\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>Note</p> <p>Same as with the \"primary\" JS and CSS, the file paths files can be either:</p> <ol> <li>Relative to the Python component file (as seen above),</li> <li>Relative to any of the component directories as defined by <code>COMPONENTS.dirs</code> and/or <code>COMPONENTS.app_dirs</code> (e.g. <code>[your apps]/components</code> dir and <code>[project root]/components</code>)</li> </ol> <p>Info</p> <p>The <code>Media</code> nested class is shaped based on Django's Media class.</p> <p>As such, django-components allows multiple formats to define the nested Media class:</p> <pre><code># Single files\nclass Media:\n    js = \"calendar.js\"\n    css = \"calendar.css\"\n\n# Lists of files\nclass Media:\n    js = [\"calendar.js\", \"calendar2.js\"]\n    css = [\"calendar.css\", \"calendar2.css\"]\n\n# Dictionary of media types for CSS\nclass Media:\n    js = [\"calendar.js\", \"calendar2.js\"]\n    css = {\n      \"all\": [\"calendar.css\", \"calendar2.css\"],\n    }\n</code></pre> <p>If you define a list of JS files, they will be executed one-by-one, left-to-right.</p>"},{"location":"getting_started/adding_js_and_css/#rules-of-execution-of-scripts-in-mediajs","title":"Rules of execution of scripts in <code>Media.js</code>","text":"<p>The scripts defined in <code>Media.js</code> still follow the rules outlined above:</p> <ol> <li>JS is executed in the order in which the components are found in the HTML.</li> <li>JS will be executed only once, even if there is multiple instances of the same component.</li> </ol> <p>Additionally to <code>Media.js</code> applies that:</p> <ol> <li>JS in <code>Media.js</code> is executed before the component's primary JS.</li> <li>JS in <code>Media.js</code> is executed in the same order as it was defined.</li> <li>If there is multiple components that specify the same JS path or URL in <code>Media.js</code>,    this JS will be still loaded and executed only once.</li> </ol> <p>Putting all of this together, our <code>Calendar</code> component above would render HTML like so:</p> <pre><code>&lt;html&gt;\n  &lt;head&gt;\n    ...\n    &lt;!-- CSS from Media.css --&gt;\n    &lt;link href=\"/static/path/to/shared.css\" media=\"all\" rel=\"stylesheet\" /&gt;\n    &lt;link\n      href=\"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\"\n      media=\"all\"\n      rel=\"stylesheet\"\n    /&gt;\n    &lt;!-- CSS from Component.css_file --&gt;\n    &lt;style&gt;\n      .calendar {\n        width: 200px;\n        background: pink;\n      }\n      .calendar span {\n        font-weight: bold;\n      }\n    &lt;/style&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    ...\n    &lt;!-- JS from Media.js --&gt;\n    &lt;script src=\"/static/path/to/shared.js\"&gt;&lt;/script&gt;\n    &lt;script src=\"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\"&gt;&lt;/script&gt;\n    &lt;!-- JS from Component.js_file --&gt;\n    &lt;script&gt;\n      (function () {\n        document.querySelector(\".calendar\").onclick = () =&gt; {\n          alert(\"Clicked calendar!\");\n        };\n      })();\n    &lt;/script&gt;\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre> <p>Now that we have a fully-defined component, next let's use it in a Django template \u27a1\ufe0f.</p>"},{"location":"getting_started/adding_slots/","title":"Adding slots","text":"<p>Our calendar component's looking great! But we just got a new assignment from our colleague - The calendar date needs to be shown on 3 different pages:</p> <ol> <li>On one page, it needs to be shown as is</li> <li>On the second, the date needs to be bold</li> <li>On the third, the date needs to be in italics</li> </ol> <p>As a reminder, this is what the component's template looks like:</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>There's many ways we could approach this:</p> <ul> <li>Expose the date in a slot</li> <li>Style <code>.calendar &gt; span</code> differently on different pages</li> <li>Pass a variable to the component that decides how the date is rendered</li> <li>Create a new component</li> </ul> <p>First two options are more flexible, because the custom styling is not baked into a component's implementation. And for the sake of demonstration, we'll solve this challenge with slots.</p>"},{"location":"getting_started/adding_slots/#1-what-are-slots","title":"1. What are slots","text":"<p>Components support something called Slots.</p> <p>When a component is used inside another template, slots allow the parent template to override specific parts of the child component by passing in different content.</p> <p>This mechanism makes components more reusable and composable.</p> <p>This behavior is similar to slots in Vue.</p> <p>In the example below we introduce two tags that work hand in hand to make this work. These are...</p> <ul> <li><code>{% slot &lt;name&gt; %}</code>/<code>{% endslot %}</code>: Declares a new slot in the component template.</li> <li><code>{% fill &lt;name&gt; %}</code>/<code>{% endfill %}</code>: (Used inside a <code>{% component %}</code>   tag pair.) Fills a declared slot with the specified content.</li> </ul>"},{"location":"getting_started/adding_slots/#2-add-a-slot-tag","title":"2. Add a slot tag","text":"<p>Let's update our calendar component to support more customization. We'll add <code>{% slot %}</code> tag to the template:</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is\n  {% slot \"date\" default %}  {# &lt;--- new #}\n    &lt;span&gt;{{ date }}&lt;/span&gt;\n  {% endslot %}\n&lt;/div&gt;\n</code></pre> <p>Notice that:</p> <ol> <li> <p>We named the slot <code>date</code> - so we can fill this slot by using <code>{% fill \"date\" %}</code></p> </li> <li> <p>We also made it the default slot.</p> </li> <li> <p>We placed our original implementation inside the <code>{% slot %}</code>    tag - this is what will be rendered when the slot is NOT overriden.</p> </li> </ol>"},{"location":"getting_started/adding_slots/#3-add-fill-tag","title":"3. Add fill tag","text":"<p>Now we can use <code>{% fill %}</code> tags inside the <code>{% component %}</code> tags to override the <code>date</code> slot to generate the bold and italics variants:</p> <pre><code>{# Default #}\n{% component \"calendar\" date=\"2024-12-13\" / %}\n\n{# Bold #}\n{% component \"calendar\" date=\"2024-12-13\" %}\n  &lt;b&gt; 2024-12-13 &lt;/b&gt;\n{% endcomponent %}\n\n{# Italics #}\n{% component \"calendar\" date=\"2024-12-13\" %}\n  &lt;i&gt; 2024-12-13 &lt;/i&gt;\n{% endcomponent %}\n</code></pre> <p>Which will render as:</p> <pre><code>&lt;!-- Default --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;2024-12-13&lt;/span&gt;\n&lt;/div&gt;\n\n&lt;!-- Bold --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;b&gt;2024-12-13&lt;/b&gt;\n&lt;/div&gt;\n\n&lt;!-- Italics --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;i&gt;2024-12-13&lt;/i&gt;\n&lt;/div&gt;\n</code></pre> <p>Info</p> <p>Since we used the <code>default</code> flag on <code>{% slot \"date\" %}</code> inside our calendar component, we can target the <code>date</code> component in multiple ways:</p> <ol> <li> <p>Explicitly by it's name     <pre><code>{% component \"calendar\" date=\"2024-12-13\" %}\n  {% fill \"date\" %}\n    &lt;i&gt; 2024-12-13 &lt;/i&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre></p> </li> <li> <p>Implicitly as the default slot (Omitting the     <code>{% fill %}</code> tag)     <pre><code>{% component \"calendar\" date=\"2024-12-13\" %}\n  &lt;i&gt; 2024-12-13 &lt;/i&gt;\n{% endcomponent %}\n</code></pre></p> </li> <li> <p>Explicitly as the default slot (Setting fill name to <code>default</code>)     <pre><code>{% component \"calendar\" date=\"2024-12-13\" %}\n  {% fill \"default\" %}\n    &lt;i&gt; 2024-12-13 &lt;/i&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre></p> </li> </ol>"},{"location":"getting_started/adding_slots/#5-wait-theres-a-bug","title":"5. Wait, there's a bug","text":"<p>There is a mistake in our code! <code>2024-12-13</code> is Friday, so that's fine. But if we updated the to <code>2024-12-14</code>, which is Saturday, our template from previous step would render this:</p> <pre><code>&lt;!-- Default --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;2024-12-16&lt;/span&gt;\n&lt;/div&gt;\n\n&lt;!-- Bold --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;b&gt;2024-12-14&lt;/b&gt;\n&lt;/div&gt;\n\n&lt;!-- Italics --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;i&gt;2024-12-14&lt;/i&gt;\n&lt;/div&gt;\n</code></pre> <p>The first instance rendered <code>2024-12-16</code>, while the rest rendered <code>2024-12-14</code>!</p> <p>Why? Remember that in the <code>get_context_data()</code> method of our Calendar component, we pre-process the date. If the date falls on Saturday or Sunday, we shift it to next Monday:</p> [project root]/components/calendar/calendar.py<pre><code>from datetime import date\n\nfrom django_components import Component, register\n\n# If date is Sat or Sun, shift it to next Mon, so the date is always workweek.\ndef to_workweek_date(d: date):\n    ...\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    ...\n    def get_context_data(self, date: date, extra_class: str | None = None):\n        workweek_date = to_workweek_date(date)\n        return {\n            \"date\": workweek_date,\n            \"extra_class\": extra_class,\n        }\n</code></pre> <p>And the issue is that in our template, we used the <code>date</code> value that we used as input, which is NOT the same as the <code>date</code> variable used inside Calendar's template.</p>"},{"location":"getting_started/adding_slots/#5-adding-data-to-slots","title":"5. Adding data to slots","text":"<p>We want to use the same <code>date</code> variable that's used inside Calendar's template.</p> <p>Luckily, django-components allows passing data to the slot, also known as Scoped slots.</p> <p>This consists of two steps:</p> <ol> <li>Pass the <code>date</code> variable to the <code>{% slot %}</code> tag</li> <li>Access the <code>date</code> variable in the <code>{% fill %}</code>    tag by using the special <code>data</code> kwarg</li> </ol> <p>Let's update the Calendar's template:</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is\n  {% slot \"date\" default date=date %}  {# &lt;--- changed #}\n    &lt;span&gt;{{ date }}&lt;/span&gt;\n  {% endslot %}\n&lt;/div&gt;\n</code></pre> <p>Info</p> <p>The <code>{% slot %}</code> tag has one special kwarg, <code>name</code>. When you write</p> <pre><code>{% slot \"date\" / %}\n</code></pre> <p>It's the same as:</p> <pre><code>{% slot name=\"date\" / %}\n</code></pre> <p>Other than the <code>name</code> kwarg, you can pass any extra kwargs to the <code>{% slot %}</code> tag, and these will be exposed as the slot's data.</p> <pre><code>{% slot name=\"date\" kwarg1=123 kwarg2=\"text\" kwarg3=my_var / %}\n</code></pre>"},{"location":"getting_started/adding_slots/#6-accessing-slot-data-in-fills","title":"6. Accessing slot data in fills","text":"<p>Now, on the <code>{% fill %}</code> tags, we can use the <code>data</code> kwarg to specify the variable under which the slot data will be available.</p> <p>The variable from the <code>data</code> kwarg contains all the extra kwargs passed to the <code>{% slot %}</code> tag.</p> <p>So if we set <code>data=\"slot_data\"</code>, then we can access the date variable under <code>slot_data.date</code>:</p> <pre><code>{# Default #}\n{% component \"calendar\" date=\"2024-12-13\" / %}\n\n{# Bold #}\n{% component \"calendar\" date=\"2024-12-13\" %}\n  {% fill \"date\" data=\"slot_data\" %}\n    &lt;b&gt; {{ slot_data.date }} &lt;/b&gt;\n  {% endfill %}\n{% endcomponent %}\n\n{# Italics #}\n{% component \"calendar\" date=\"2024-12-13\" %}\n  {% fill \"date\" data=\"slot_data\" %}\n    &lt;i&gt; {{ slot_data.date }} &lt;/i&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre> <p>By using the <code>date</code> variable from the slot, we'll render the correct date each time:</p> <pre><code>&lt;!-- Default --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;2024-12-16&lt;/span&gt;\n&lt;/div&gt;\n\n&lt;!-- Bold --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;b&gt;2024-12-16&lt;/b&gt;\n&lt;/div&gt;\n\n&lt;!-- Italics --&gt;\n&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;i&gt;2024-12-16&lt;/i&gt;\n&lt;/div&gt;\n</code></pre> <p>Info</p> <p>When to use slots vs variables?</p> <p>Generally, slots are more flexible - you can access the slot data, even the original slot content. Thus, slots behave more like functions that render content based on their context.</p> <p>On the other hand, variables are static - the variable you pass to a component is what will be used.</p> <p>Moreover, slots are treated as part of the template - for example the CSS scoping (work in progress) is applied to the slot content too.</p>"},{"location":"getting_started/components_in_templates/","title":"Components in templates","text":"<p>By the end of this section, we want to be able to use our components in Django templates like so:</p> <pre><code>{% load component_tags %}\n&lt;!DOCTYPE html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    &lt;title&gt;My example calendar&lt;/title&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component \"calendar\" / %}\n  &lt;/body&gt;\n&lt;html&gt;\n</code></pre>"},{"location":"getting_started/components_in_templates/#1-register-component","title":"1. Register component","text":"<p>First, however, we need to register our component class with <code>ComponentRegistry</code>.</p> <p>To register a component with a <code>ComponentRegistry</code>, we will use the <code>@register</code> decorator, and give it a name under which the component will be accessible from within the template:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register  # &lt;--- new\n\n@register(\"calendar\")  # &lt;--- new\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>This will register the component to the default registry. Default registry is loaded into the template by calling <code>{% load component_tags %}</code> inside the template.</p> <p>Info</p> <p>Why do we have to register components?</p> <p>We want to use our component as a template tag (<code>{% ... %}</code>) in Django template.</p> <p>In Django, template tags are managed by the <code>Library</code> instances. Whenever you include <code>{% load xxx %}</code> in your template, you are loading a <code>Library</code> instance into your template.</p> <p><code>ComponentRegistry</code> acts like a router and connects the registered components with the associated <code>Library</code>.</p> <p>That way, when you include <code>{% load component_tags %}</code> in your template, you are able to \"call\" components like <code>{% component \"calendar\" / %}</code>.</p> <p><code>ComponentRegistries</code> also make it possible to group and share components as standalone packages. Learn more here.</p> <p>Note</p> <p>You can create custom <code>ComponentRegistry</code> instances, which will use different <code>Library</code> instances. In that case you will have to load different libraries depending on which components you want to use:</p> <p>Example 1 - Using component defined in the default registry <pre><code>{% load component_tags %}\n&lt;div&gt;\n  {% component \"calendar\" / %}\n&lt;/div&gt;\n</code></pre></p> <p>Example 2 - Using component defined in a custom registry <pre><code>{% load my_custom_tags %}\n&lt;div&gt;\n  {% my_component \"table\" / %}\n&lt;/div&gt;\n</code></pre></p> <p>Note that, because the tag name <code>component</code> is use by the default ComponentRegistry, the custom registry was configured to use the tag <code>my_component</code> instead. Read more here</p>"},{"location":"getting_started/components_in_templates/#2-load-and-use-the-component-in-template","title":"2. Load and use the component in template","text":"<p>The component is now registered under the name <code>calendar</code>. All that remains to do is to load and render the component inside a template:</p> <pre><code>{% load component_tags %}  {# Load the default registry #}\n&lt;!DOCTYPE html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    &lt;title&gt;My example calendar&lt;/title&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    {% component \"calendar\" / %}  {# Render the component #}\n  &lt;/body&gt;\n&lt;html&gt;\n</code></pre> <p>Info</p> <p>Component tags should end with <code>/</code> if they do not contain any Slot fills. But you can also use <code>{% endcomponent %}</code> instead:</p> <pre><code>{% component \"calendar\" %}{% endcomponent %}\n</code></pre> <p>We defined the Calendar's template as</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>and the variable <code>date</code> as <code>\"1970-01-01\"</code>.</p> <p>Thus, the final output will look something like this:</p> <pre><code>&lt;!DOCTYPE html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    &lt;title&gt;My example calendar&lt;/title&gt;\n    &lt;style&gt;\n      .calendar {\n        width: 200px;\n        background: pink;\n      }\n      .calendar span {\n        font-weight: bold;\n      }\n    &lt;/style&gt;\n  &lt;/head&gt;\n  &lt;body&gt;\n    &lt;div class=\"calendar\"&gt;\n      Today's date is &lt;span&gt;1970-01-01&lt;/span&gt;\n    &lt;/div&gt;\n    &lt;script&gt;\n      (function () {\n        document.querySelector(\".calendar\").onclick = () =&gt; {\n          alert(\"Clicked calendar!\");\n        };\n      })();\n    &lt;/script&gt;\n  &lt;/body&gt;\n&lt;html&gt;\n</code></pre> <p>This makes it possible to organize your front-end around reusable components, instead of relying on template tags and keeping your CSS and Javascript in the static directory.</p> <p>Info</p> <p>Remember that you can use <code>{% component_js_dependencies %}</code> and <code>{% component_css_dependencies %}</code> to change where the <code>&lt;script&gt;</code> and <code>&lt;style&gt;</code> tags will be rendered (See JS and CSS output locations).</p> <p>Info</p> <p>How does django-components pick up registered components?</p> <p>Notice that it was enough to add <code>@register</code> to the component. We didn't need to import the component file anywhere to execute it.</p> <p>This is because django-components automatically imports all Python files found in the component directories during an event called Autodiscovery.</p> <p>So with Autodiscovery, it's the same as if you manually imported the component files on the <code>ready()</code> hook:</p> <pre><code>class MyApp(AppConfig):\n    default_auto_field = \"django.db.models.BigAutoField\"\n    name = \"myapp\"\n\n    def ready(self):\n        import myapp.components.calendar\n        import myapp.components.table\n        ...\n</code></pre> <p>You can now render the components in templates!</p> <p>Currently our component always renders the same content. Let's parametrise it, so that our Calendar component is configurable from within the template \u27a1\ufe0f</p>"},{"location":"getting_started/parametrising_components/","title":"Parametrising components","text":"<p>So far, our Calendar component will always render the date <code>1970-01-01</code>. Let's make it more useful and flexible by being able to pass in custom date.</p> <p>What we want is to be able to use the Calendar component within the template like so:</p> <pre><code>{% component \"calendar\" date=\"2024-12-13\" extra_class=\"text-red\" / %}\n</code></pre>"},{"location":"getting_started/parametrising_components/#1-understading-component-inputs","title":"1. Understading component inputs","text":"<p>In section Create your first component, we defined the <code>get_context_data()</code> method that defines what variables will be available within the template:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    ...\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>What we didn't say is that <code>get_context_data()</code> actually receives the args and kwargs that were passed to a component.</p> <p>So if we call a component with a <code>date</code> and <code>extra_class</code> keywords:</p> <pre><code>{% component \"calendar\" date=\"2024-12-13\" extra_class=\"text-red\" / %}\n</code></pre> <p>This is the same as calling:</p> <pre><code>Calendar.get_context_data(date=\"2024-12-13\", extra_class=\"text-red\")\n</code></pre> <p>And same applies to positional arguments, or mixing args and kwargs, where:</p> <pre><code>{% component \"calendar\" \"2024-12-13\" extra_class=\"text-red\" / %}\n</code></pre> <p>is same as</p> <pre><code>Calendar.get_context_data(\"2024-12-13\", extra_class=\"text-red\")\n</code></pre>"},{"location":"getting_started/parametrising_components/#2-define-inputs-for-get_context_data","title":"2. Define inputs for <code>get_context_data</code>","text":"<p>Let's put this to test. We want to pass <code>date</code> and <code>extra_class</code> kwargs to the component. And so, we can write the <code>get_context_data()</code> method such that it expects those parameters:</p> [project root]/components/calendar/calendar.py<pre><code>from datetime import date\n\nfrom django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    ...\n    def get_context_data(self, date: date, extra_class: str | None = None):\n        return {\n            \"date\": date,\n            \"extra_class\": extra_class,\n        }\n</code></pre> <p>Info</p> <p>Since <code>get_context_data()</code> is just a regular Python function, type hints annotations work the same way as anywhere else.</p> <p>Warning</p> <p>Since <code>get_context_data()</code> is just a regular Python function, it will raise TypeError if it receives incorrect parameters.</p> <p>Since <code>extra_class</code> is optional in the function signature, it's optional also in the template. So both following calls are valid:</p> <pre><code>{% component \"calendar\" \"2024-12-13\" / %}\n{% component \"calendar\" \"2024-12-13\" extra_class=\"text-red\" / %}\n</code></pre> <p>However, <code>date</code> is required. Thus we MUST provide it. Same with regular Python functions, <code>date</code> can be set either as positional or keyword argument. But either way it MUST be set:</p> <pre><code>\u2705\n{% component \"calendar\" \"2024-12-13\" / %}\n{% component \"calendar\" extra_class=\"text-red\" date=\"2024-12-13\" / %}\n\n\u274c\n{% component \"calendar\" extra_class=\"text-red\" / %}\n</code></pre>"},{"location":"getting_started/parametrising_components/#3-process-inputs-in-get_context_data","title":"3. Process inputs in <code>get_context_data</code>","text":"<p>The <code>get_context_data()</code> method is powerful, because it allows us to decouple component inputs from the template variables. In other words, we can pre-process the component inputs, and massage them into a shape that's most appropriate for what the template needs. And it also allows us to pass in static data into the template.</p> <p>Imagine our component receives data from the database that looks like below (taken from Django).</p> <pre><code>cities = [\n    {\"name\": \"Mumbai\", \"population\": \"19,000,000\", \"country\": \"India\"},\n    {\"name\": \"Calcutta\", \"population\": \"15,000,000\", \"country\": \"India\"},\n    {\"name\": \"New York\", \"population\": \"20,000,000\", \"country\": \"USA\"},\n    {\"name\": \"Chicago\", \"population\": \"7,000,000\", \"country\": \"USA\"},\n    {\"name\": \"Tokyo\", \"population\": \"33,000,000\", \"country\": \"Japan\"},\n]\n</code></pre> <p>We need to group the list items by size into following buckets by population:</p> <ul> <li>0-10,000,000</li> <li>10,000,001-20,000,000</li> <li>20,000,001-30,000,000</li> <li>+30,000,001</li> </ul> <p>So we want to end up with following data:</p> <pre><code>cities_by_pop = [\n    {\n      \"name\": \"0-10,000,000\",\n      \"items\": [\n          {\"name\": \"Chicago\", \"population\": \"7,000,000\", \"country\": \"USA\"},\n      ]\n    },\n    {\n      \"name\": \"10,000,001-20,000,000\",\n      \"items\": [\n          {\"name\": \"Calcutta\", \"population\": \"15,000,000\", \"country\": \"India\"},\n          {\"name\": \"Mumbai\", \"population\": \"19,000,000\", \"country\": \"India\"},\n          {\"name\": \"New York\", \"population\": \"20,000,000\", \"country\": \"USA\"},\n      ]\n    },\n    {\n      \"name\": \"30,000,001-40,000,000\",\n      \"items\": [\n          {\"name\": \"Tokyo\", \"population\": \"33,000,000\", \"country\": \"Japan\"},\n      ]\n    },\n]\n</code></pre> <p>Without the <code>get_context_data()</code> method, we'd have to either:</p> <ol> <li>Pre-process the data in Python before passing it to the components.</li> <li>Define a Django filter or template tag to take the data and process it on the spot.</li> </ol> <p>Instead, with <code>get_context_data()</code>, we can keep this transformation private to this component, and keep the rest of the codebase clean.</p> <pre><code>def group_by_pop(data):\n    ...\n\n@register(\"population_table\")\nclass PopulationTable(Component):\n    template_file = \"population_table.html\"\n\n    def get_context_data(self, data):\n        return {\n            \"data\": group_by_pop(data),\n        }\n</code></pre> <p>Similarly we can make use of <code>get_context_data()</code> to pre-process the date that was given to the component:</p> [project root]/components/calendar/calendar.py<pre><code>from datetime import date\n\nfrom django_components import Component, register\n\n# If date is Sat or Sun, shift it to next Mon, so the date is always workweek.\ndef to_workweek_date(d: date):\n    ...\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    ...\n    def get_context_data(self, date: date, extra_class: str | None = None):\n        workweek_date = to_workweek_date(date)  # &lt;--- new\n        return {\n            \"date\": workweek_date,  # &lt;--- changed\n            \"extra_class\": extra_class,\n        }\n</code></pre>"},{"location":"getting_started/parametrising_components/#4-pass-inputs-to-components","title":"4. Pass inputs to components","text":"<p>Once we're happy with <code>Calendar.get_contex_data()</code>, we can update our templates to use the parametrized version of the component:</p> <pre><code>&lt;div&gt;\n  {% component \"calendar\" date=\"2024-12-13\" / %}\n  {% component \"calendar\" date=\"1970-01-01\" / %}\n&lt;/div&gt;\n</code></pre> <p>Next, you will learn how to use slots give your components even more flexibility \u27a1\ufe0f</p>"},{"location":"getting_started/rendering_components/","title":"Rendering components","text":"<p>Our calendar component can accept and pre-process data, defines its own CSS and JS, and can be used in templates.</p> <p>...But how do we actually render the components into HTML?</p> <p>There's 3 ways to render a component:</p> <ul> <li>Render the template that contains the <code>{% component %}</code> tag</li> <li>Render the component directly with <code>Component.render()</code></li> <li>Render the component directly with <code>Component.render_to_response()</code></li> </ul> <p>As a reminder, this is what the calendar component looks like:</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre>"},{"location":"getting_started/rendering_components/#1-render-the-template-that-contains-the-component-tag","title":"1. Render the template that contains the <code>{% component %}</code> tag","text":"<p>If you have embedded the component in a Django template using the <code>{% component %}</code> tag:</p> [project root]/templates/my_template.html<pre><code>{% load component_tags %}\n&lt;div&gt;\n  {% component \"calendar\" date=\"2024-12-13\" / %}\n&lt;/div&gt;\n</code></pre> <p>You can simply render the template with the Django tooling:</p>"},{"location":"getting_started/rendering_components/#with-djangoshortcutsrender","title":"With <code>django.shortcuts.render()</code>","text":"<pre><code>from django.shortcuts import render\n\ncontext = {\"date\": \"2024-12-13\"}\nrendered_template = render(request, \"my_template.html\", context)\n</code></pre>"},{"location":"getting_started/rendering_components/#with-templaterender","title":"With <code>Template.render()</code>","text":"<p>Either loading the template with <code>get_template()</code>:</p> <pre><code>from django.template.loader import get_template\n\ntemplate = get_template(\"my_template.html\")\ncontext = {\"date\": \"2024-12-13\"}\nrendered_template = template.render(context)\n</code></pre> <p>Or creating a new <code>Template</code> instance:</p> <pre><code>from django.template import Template\n\ntemplate = Template(\"\"\"\n{% load component_tags %}\n&lt;div&gt;\n  {% component \"calendar\" date=\"2024-12-13\" / %}\n&lt;/div&gt;\n\"\"\")\nrendered_template = template.render()\n</code></pre>"},{"location":"getting_started/rendering_components/#2-render-the-component-directly-with-componentrender","title":"2. Render the component directly with <code>Component.render()</code>","text":"<p>You can also render the component directly with <code>Component.render()</code>, without wrapping the component in a template.</p> <pre><code>from components.calendar import Calendar\n\ncalendar = Calendar\nrendered_component = calendar.render()\n</code></pre> <p>You can pass args, kwargs, slots, and more, to the component:</p> <pre><code>from components.calendar import Calendar\n\ncalendar = Calendar\nrendered_component = calendar.render(\n    args=[\"2024-12-13\"],\n    kwargs={\n        \"extra_class\": \"my-class\"\n    },\n    slots={\n        \"date\": \"&lt;b&gt;2024-12-13&lt;/b&gt;\"\n    },\n)\n</code></pre> <p>Info</p> <p>Among other, you can pass also the <code>request</code> object to the <code>render</code> method:</p> <pre><code>from components.calendar import Calendar\n\ncalendar = Calendar\nrendered_component = calendar.render(request=request)\n</code></pre> <p>The <code>request</code> object is required for some of the component's features, like using Django's context processors.</p>"},{"location":"getting_started/rendering_components/#3-render-the-component-directly-with-componentrender_to_response","title":"3. Render the component directly with <code>Component.render_to_response()</code>","text":"<p>A common pattern in Django is to render the component and then return the resulting HTML as a response to an HTTP request.</p> <p>For this, you can use the <code>Component.render_to_response()</code> convenience method.</p> <p><code>render_to_response()</code> accepts the same args, kwargs, slots, and more, as <code>Component.render()</code>, but wraps the result in an <code>HttpResponse</code>.</p> <pre><code>from components.calendar import Calendar\n\ndef my_view(request):\n    response = Calendar.render_to_response(\n        args=[\"2024-12-13\"],\n        kwargs={\n            \"extra_class\": \"my-class\"\n        },\n        slots={\n            \"date\": \"&lt;b&gt;2024-12-13&lt;/b&gt;\"\n        },\n        request=request,\n    )\n    return response\n</code></pre> <p>Info</p> <p>Response class of <code>render_to_response</code></p> <p>While <code>render</code> method returns a plain string, <code>render_to_response</code> wraps the rendered content in a \"Response\" class. By default, this is <code>django.http.HttpResponse</code>.</p> <p>If you want to use a different Response class in <code>render_to_response</code>, set the <code>Component.response_class</code> attribute:</p> <pre><code>class MyCustomResponse(HttpResponse):\n    def __init__(self, *args, **kwargs) -&gt; None:\n        super().__init__(*args, **kwargs)\n        # Configure response\n        self.headers = ...\n        self.status = ...\n\nclass SimpleComponent(Component):\n    response_class = MyCustomResponse\n</code></pre>"},{"location":"getting_started/your_first_component/","title":"Create your first component","text":"<p>A component in django-components can be as simple as a Django template and Python code to declare the component:</p> calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n</code></pre> <p>Or a combination of Django template, Python, CSS, and Javascript:</p> calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> calendar.css<pre><code>.calendar {\n  width: 200px;\n  background: pink;\n}\n</code></pre> calendar.js<pre><code>document.querySelector(\".calendar\").onclick = function () {\n  alert(\"Clicked calendar!\");\n};\n</code></pre> calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n</code></pre> <p>Alternatively, you can \"inline\" HTML, JS, and CSS right into the component class:</p> <pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template = \"\"\"\n      &lt;div class=\"calendar\"&gt;\n        Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n      &lt;/div&gt;\n    \"\"\"\n\n    css = \"\"\"\n      .calendar {\n        width: 200px;\n        background: pink;\n      }\n    \"\"\"\n\n    js = \"\"\"\n      document.querySelector(\".calendar\").onclick = function () {\n        alert(\"Clicked calendar!\");\n      };\n    \"\"\"\n</code></pre> <p>Note</p> <p>If you \"inline\" the HTML, JS and CSS code into the Python class, you can set up syntax highlighting for better experience. However, autocompletion / intellisense does not work with syntax highlighting.</p> <p>We'll start by creating a component that defines only a Django template:</p>"},{"location":"getting_started/your_first_component/#1-create-project-structure","title":"1. Create project structure","text":"<p>Start by creating empty <code>calendar.py</code> and <code>calendar.html</code> files:</p> <pre><code>sampleproject/\n\u251c\u2500\u2500 calendarapp/\n\u251c\u2500\u2500 components/             \ud83c\udd95\n\u2502   \u2514\u2500\u2500 calendar/           \ud83c\udd95\n\u2502       \u251c\u2500\u2500 calendar.py     \ud83c\udd95\n\u2502       \u2514\u2500\u2500 calendar.html   \ud83c\udd95\n\u251c\u2500\u2500 sampleproject/\n\u251c\u2500\u2500 manage.py\n\u2514\u2500\u2500 requirements.txt\n</code></pre>"},{"location":"getting_started/your_first_component/#2-write-django-template","title":"2. Write Django template","text":"<p>Inside <code>calendar.html</code>, write:</p> [project root]/components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>In this example we've defined one template variable <code>date</code>. You can use any and as many variables as you like. These variables will be defined in the Python file in <code>get_context_data()</code> when creating an instance of this component.</p> <p>Note</p> <p>The template will be rendered with whatever template backend you've specified in your Django settings file.</p> <p>Currently django-components supports only the default <code>\"django.template.backends.django.DjangoTemplates\"</code> template backend!</p>"},{"location":"getting_started/your_first_component/#3-create-new-component-in-python","title":"3. Create new Component in Python","text":"<p>In <code>calendar.py</code>, create a subclass of Component to create a new component.</p> <p>To link the HTML template with our component, set <code>template_file</code> to the name of the HTML file.</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n</code></pre> <p>Note</p> <p>The path to the template file can be either:</p> <ol> <li>Relative to the component's python file (as seen above),</li> <li>Relative to any of the component directories as defined by <code>COMPONENTS.dirs</code> and/or <code>COMPONENTS.app_dirs</code> (e.g. <code>[your apps]/components</code> dir and <code>[project root]/components</code>)</li> </ol>"},{"location":"getting_started/your_first_component/#4-define-the-template-variables","title":"4. Define the template variables","text":"<p>In <code>calendar.html</code>, we've used the variable <code>date</code>. So we need to define it for the template to work.</p> <p>This is done using <code>Component.get_context_data()</code>. It's a function that returns a dictionary. The entries in this dictionary will become available within the template as variables, e.g. as <code>{{ date }}</code>.</p> [project root]/components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n\n    def get_context_data(self):\n        return {\n            \"date\": \"1970-01-01\",\n        }\n</code></pre> <p>Now, when we render the component with <code>Component.render()</code> method:</p> <pre><code>Calendar.render()\n</code></pre> <p>It will output</p> <pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;1970-01-01&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>And voil\u00e1!! We've created our first component.</p> <p>Next, let's add JS and CSS to this component \u27a1\ufe0f.</p>"},{"location":"guides/devguides/dependency_mgmt/","title":"JS and CSS rendering","text":"<p>Aim of this doc is to share the intuition on how we manage the JS and CSS (\"dependencies\") associated with components, and how we render them.</p>"},{"location":"guides/devguides/dependency_mgmt/#starting-conditions","title":"Starting conditions","text":"<ol> <li> <p>First of all, when we consider a component, it has two kind of dependencies - the \"inlined\" JS and CSS, and additional linked JS and CSS via <code>Media.js/css</code>:</p> <pre><code>from django_components import Component, types\n\nclass MyTable(Component):\n    # Inlined JS\n    js: types.js = \"\"\"\n      console.log(123);\n    \"\"\"\n\n    # Inlined CSS\n    css: types.css = \"\"\"\n      .my-table {\n        color: red;\n      }\n    \"\"\"\n\n    # Linked JS / CSS\n    class Media:\n        js = [\n            \"script-one.js\",  # STATIC file relative to component file\n            \"/script-two.js\", # URL path\n            \"https://example.com/script-three.js\", # URL\n        ]\n\n        css = [\n            \"style-one.css\",  # STATIC file relative to component file\n            \"/style-two.css\", # URL path\n            \"https://example.com/style-three.css\", # URL\n        ]\n</code></pre> </li> <li> <p>Second thing to keep in mind is that all component's are eventually rendered into a string. And so, if we want to associate extra info with a rendered component, it has to be serialized to a string.</p> <p>This is because a component may be embedded in a Django Template with the <code>{% component %}</code> tag, which, when rendered, is turned into a string:</p> <pre><code>template = Template(\"\"\"\n  {% load component_tags %}\n  &lt;div&gt;\n    {% component \"my_table\" / %}\n  &lt;/div&gt;\n\"\"\")\n\nhtml_str = template.render(Context({}))\n</code></pre> <p>And for this reason, we take the same approach also when we render a component with <code>Component.render()</code> - It returns a string.</p> </li> <li> <p>Thirdly, we also want to add support for JS / CSS variables. That is, that a variable defined on the component would be somehow accessible from within the JS script / CSS style.</p> <p>A simple approach to this would be to modify the inlined JS / CSS directly, and insert them for each component. But if you had extremely large JS / CSS, and e.g. only a single JS / CSS variable that you want to insert, it would be wasteful to create a copy of the JS / CSS scripts for each component instance.</p> <p>So instead, a preferred approach here is to defined and insert the inlined JS / CSS only once, and have some kind of mechanism on how we make correct the JS / CSS variables available only to the correct components.</p> </li> <li> <p>Last important thing is that we want the JS / CSS dependencies to work also with HTML fragments.</p> <p>So normally, e.g. when a user hits URL of a web page, the server renders full HTML document, with <code>&lt;!doctype&gt;</code>, <code>&lt;html&gt;</code>, <code>&lt;head&gt;</code>, and <code>&lt;body&gt;</code>. In such case, we know about ALL JS and CSS dependencies at render time, so we can e.g. insert them into <code>&lt;head&gt;</code> and <code>&lt;body&gt;</code> ourselves.</p> <p>However this renders only the initial state. HTML fragments is a common pattern where interactivity is added to the web page by fetching and replacing bits of HTML on the main HTML document after some user action.</p> <p>In the case of HTML fragments, the HTML is NOT a proper document, but only the HTML that will be inserted somewhere into the DOM.</p> <p>The challenge here is that Django template for the HTML fragment MAY contain components, and these components MAY have inlined or linked JS and CSS.</p> <pre><code>def fragment_view(request):\n    template = Template(\"\"\"\n      {% load component_tags %}\n      &lt;div&gt;\n        {% component \"my_table\" / %}\n      &lt;/div&gt;\n    \"\"\")\n\n    fragment_str = template.render(Context({}))\n    return HttpResponse(fragment_str, status=200)\n</code></pre> <p>User may use different libraries to fetch and insert the HTML fragments (e.g. HTMX, AlpineJS, ...). From our perspective, the only thing that we can reliably say is that we expect that the HTML fragment WILL be eventually inserted into the DOM.</p> <p>So to include the corresponding JS and CSS, a simple approach could be to append them to the HTML as <code>&lt;style&gt;</code> and <code>&lt;script&gt;</code>, e.g.:</p> <pre><code>&lt;!-- Original content --&gt;\n&lt;div&gt;...&lt;/div&gt;\n&lt;!-- Associated CSS files --&gt;\n&lt;link href=\"http://...\" /&gt;\n&lt;style&gt;\n  .my-class {\n    color: red;\n  }\n&lt;/style&gt;\n&lt;!-- Associated JS files --&gt;\n&lt;script src=\"http://...\"&gt;&lt;/script&gt;\n&lt;script&gt;\n  console.log(123);\n&lt;/script&gt;\n</code></pre> <p>But this has a number of issues:</p> <ul> <li>The JS scripts would run for each instance of the component.</li> <li>Bloating of the HTML file, as each inlined JS or CSS would be included fully for each component.</li> <li>While this sound OK, this could really bloat the HTML files if we used a UI component library for the basic building blocks like buttons, lists, cards, etc.</li> </ul> </li> </ol>"},{"location":"guides/devguides/dependency_mgmt/#flow","title":"Flow","text":"<p>So the solution should address all the points above. To achieve that, we manage the JS / CSS dependencies ourselves in the browser. So when a full HTML document is loaded, we keep track of which JS and CSS have been loaded. And when an HTML fragment is inserted, we check which JS / CSS dependencies it has, and load only those that have NOT been loaded yet.</p> <p>This is how we achieve that:</p> <ol> <li> <p>When a component is rendered, it inserts an HTML comment containing metadata about the rendered component.</p> <p>So a template like this</p> <pre><code>{% load component_tags %}\n&lt;div&gt;\n  {% component \"my_table\" / %}\n&lt;/div&gt;\n{% component \"button\" %}\n  Click me!\n{% endcomponent %}\n</code></pre> <p>May actually render:</p> <pre><code>&lt;div&gt;\n  &lt;!-- _RENDERED \"my_table_10bc2c,c020ad\" --&gt;\n  &lt;table&gt;\n    ...\n  &lt;/table&gt;\n&lt;/div&gt;\n&lt;!-- _RENDERED \"button_309dcf,31c0da\" --&gt;\n&lt;button&gt;Click me!&lt;/button&gt;\n</code></pre> <p>Each <code>&lt;!-- _RENDERED --&gt;</code> comment includes comma-separated data - a unique hash for the component class, e.g. <code>my_table_10bc2c</code>, and the component ID, e.g. <code>c020ad</code>.</p> <p>This way, we or the user can freely pass the rendered around or transform it, treating it as a string to add / remove / replace bits. As long as the <code>&lt;!-- _RENDERED --&gt;</code> comments remain in the rendered string, we will be able to deduce which JS and CSS dependencies the component needs.</p> </li> <li> <p>Post-process the rendered HTML, extracting the <code>&lt;!-- _RENDERED --&gt;</code> comments, and instead inserting the corresponding JS and CSS dependencies.</p> <p>If we dealt only with JS, then we could get away with processing the <code>&lt;!-- _RENDERED --&gt;</code> comments on the client (browser). However, the CSS needs to be processed still on the server, so the browser receives CSS styles already inserted as <code>&lt;style&gt;</code> or <code>&lt;link&gt;</code> HTML tags. Because if we do not do that, we get a flash of unstyled content, as there will be a delay between when the HTML page loaded and when the CSS was fetched and loaded.</p> <p>So, assuming that a user has already rendered their template, which still contains <code>&lt;!-- _RENDERED --&gt;</code> comments, we need to extract and process these comments.</p> <p>There's multiple ways to achieve this:</p> <ul> <li> <p>The approach recommended to the users is to use the <code>ComponentDependencyMiddleware</code> middleware, which scans all outgoing HTML, and post-processes the <code>&lt;!-- _RENDERED --&gt;</code> comments.</p> </li> <li> <p>If users are using <code>Component.render()</code> or <code>Component.render_to_response()</code>, these post-process the <code>&lt;!-- _RENDERED --&gt;</code> comments by default.</p> </li> <li> <p>NOTE: Users are able to opt out of the post-processing by setting <code>render_dependencies=False</code>.</p> </li> <li> <p>For advanced use cases, users may use <code>render_dependencies()</code> directly. This is the function that both <code>ComponentDependencyMiddleware</code> and <code>Component.render()</code> call internally.</p> </li> </ul> <p><code>render_dependencies()</code>, whether called directly, via middleware or other way, does the following:</p> <ol> <li> <p>Find all <code>&lt;!-- _RENDERED --&gt;</code> comments, and for each comment:</p> </li> <li> <p>Look up the corresponding component class.</p> </li> <li> <p>Get the component's inlined JS / CSS from <code>Component.js/css</code>, and linked JS / CSS from <code>Component.Media.js/css</code>.</p> </li> <li> <p>Generate JS script that loads the JS / CSS dependencies.</p> </li> <li> <p>Insert the JS scripts either at the end of <code>&lt;body&gt;</code>, or in place of <code>{% component_dependencies %}</code> / <code>{% component_js_dependencies %}</code> tags.</p> </li> <li> <p>To avoid the flash of unstyled content, we need place the styles into the HTML instead of dynamically loading them from within a JS script. The CSS is placed either at the end of <code>&lt;head&gt;</code>, or in place of <code>{% component_dependencies %}</code> / <code>{% component_css_dependencies %}</code></p> </li> <li> <p>We cache the component's inlined JS and CSS, so they can be fetched via an URL, so the inlined JS / CSS an be treated the same way as the JS / CSS dependencies set in <code>Component.Media.js/css</code>.</p> <ul> <li>NOTE: While this is currently not entirely necessary, it opens up the doors for allowing plugins to post-process the inlined JS and CSS. Because after it has been post-processed, we need to store it somewhere.</li> </ul> </li> </ol> </li> <li> <p>Server returns the post-processed HTML.</p> </li> <li> <p>In the browser, the generated JS script from step 2.4 is executed. It goes through all JS and CSS dependencies it was given. If some JS / CSS was already loaded, it is NOT fetched again. Otherwise it generates the corresponding <code>&lt;script&gt;</code> or <code>&lt;link&gt;</code> HTML tags to load the JS / CSS dependencies.</p> <p>In the browser, the \"dependency manager JS\" may look like this:</p> <pre><code>// Load JS or CSS script if not loaded already\nComponents.loadJs('&lt;script src=\"/abc/xyz/script.js\"&gt;');\nComponents.loadCss('&lt;link href=\"/abc/xyz/style.css\"&gt;');\n\n// Or mark one as already-loaded, so it is ignored when\n// we call `loadJs`\nComponents.markScriptLoaded(\"js\", \"/abc/def\");\n</code></pre> <p>Note that <code>loadJs() / loadCss()</code> receive whole <code>&lt;script&gt; / &lt;link&gt;</code> tags, not just the URL. This is because when Django's <code>Media</code> class renders JS and CSS, it formats it as <code>&lt;script&gt;</code> and <code>&lt;link&gt;</code> tags. And we allow users to modify how the JS and CSS should be rendered into the <code>&lt;script&gt;</code> and <code>&lt;link&gt;</code> tags.</p> <p>So, if users decided to add an extra attribute to their <code>&lt;script&gt;</code> tags, e.g. <code>&lt;script defer src=\"http://...\"&gt;&lt;/script&gt;</code>, then this way we make sure that the <code>defer</code> attribute will be present on the <code>&lt;script&gt;</code> tag when it is inserted into the DOM at the time of loading the JS script.</p> </li> <li> <p>To be able to fetch component's inlined JS and CSS, django-components adds a URL path under:</p> <p><code>/components/cache/&lt;str:comp_cls_hash&gt;.&lt;str:script_type&gt;/</code></p> <p>E.g. <code>/components/cache/my_table_10bc2c.js/</code></p> <p>This endpoint takes the component's unique hash, e.g. <code>my_table_10bc2c</code>, and looks up the component's inlined JS or CSS.</p> </li> </ol> <p>Thus, with this approach, we ensure that:</p> <ol> <li>All JS / CSS dependencies are loaded / executed only once.</li> <li>The approach is compatible with HTML fragments</li> <li>The approach is compatible with JS / CSS variables.</li> <li>Inlined JS / CSS may be post-processed by plugins</li> </ol>"},{"location":"guides/devguides/slot_rendering/","title":"Slot rendering","text":"<p>This doc serves as a primer on how component slots and fills are resolved.</p>"},{"location":"guides/devguides/slot_rendering/#flow","title":"Flow","text":"<ol> <li> <p>Imagine you have a template. Some kind of text, maybe HTML:    <pre><code>| ------\n| ---------\n| ----\n| -------\n</code></pre></p> </li> <li> <p>The template may contain some vars, tags, etc    <pre><code>| -- {{ my_var }} --\n| ---------\n| ----\n| -------\n</code></pre></p> </li> <li> <p>The template also contains some slots, etc    <pre><code>| -- {{ my_var }} --\n| ---------\n| -- {% slot \"myslot\" %} ---\n| -- {% endslot %} ---\n| ----\n| -- {% slot \"myslot2\" %} ---\n| -- {% endslot %} ---\n| -------\n</code></pre></p> </li> <li> <p>Slots may be nested    <pre><code>| -- {{ my_var }} --\n| -- ABC\n| -- {% slot \"myslot\" %} ---\n| ----- DEF {{ my_var }}\n| ----- {% slot \"myslot_inner\" %}\n| -------- GHI {{ my_var }}\n| ----- {% endslot %}\n| -- {% endslot %} ---\n| ----\n| -- {% slot \"myslot2\" %} ---\n| ---- JKL {{ my_var }}\n| -- {% endslot %} ---\n| -------\n</code></pre></p> </li> <li> <p>Some slots may be inside fills for other components    <pre><code>| -- {{ my_var }} --\n| -- ABC\n| -- {% slot \"myslot\" %}---\n| ----- DEF {{ my_var }}\n| ----- {% slot \"myslot_inner\" %}\n| -------- GHI {{ my_var }}\n| ----- {% endslot %}\n| -- {% endslot %} ---\n| ------\n| -- {% component \"mycomp\" %} ---\n| ---- {% slot \"myslot\" %} ---\n| ------- JKL {{ my_var }}\n| ------- {% slot \"myslot_inner\" %}\n| ---------- MNO {{ my_var }}\n| ------- {% endslot %}\n| ---- {% endslot %} ---\n| -- {% endcomponent %} ---\n| ----\n| -- {% slot \"myslot2\" %} ---\n| ---- PQR {{ my_var }}\n| -- {% endslot %} ---\n| -------\n</code></pre></p> </li> <li> <p>The names of the slots and fills may be defined using variables    <pre><code>| -- {% slot slot_name %} ---\n| ---- STU {{ my_var }}\n| -- {% endslot %} ---\n| -------\n</code></pre></p> </li> <li> <p>The slot and fill names may be defined using for loops or other variables defined within the template (e.g. <code>{% with %}</code> tag or <code>{% ... as var %}</code> syntax)    <pre><code>| -- {% for slot_name in slots %} ---\n| ---- {% slot slot_name %} ---\n| ------ STU {{ slot_name }}\n| ---- {% endslot %} ---\n| -- {% endfor %} ---\n| -------\n</code></pre></p> </li> <li> <p>Variables for names and for loops allow us implement \"passthrough slots\" - that is, taking all slots that our component received, and passing them to a child component, dynamically.    <pre><code>| -- {% component \"mycomp\" %} ---\n| ---- {% for slot_name in slots %} ---\n| ------ {% fill slot_name %} ---\n| -------- {% slot slot_name %} ---\n| ---------- XYZ {{ slot_name }}\n| --------- {% endslot %}\n| ------- {% endfill %}\n| ---- {% endfor %} ---\n| -- {% endcomponent %} ---\n| ----\n</code></pre></p> </li> <li> <p>Putting that all together, a document may look like this:    <pre><code>| -- {{ my_var }} --\n| -- ABC\n| -- {% slot \"myslot\" %}---\n| ----- DEF {{ my_var }}\n| ----- {% slot \"myslot_inner\" %}\n| -------- GHI {{ my_var }}\n| ----- {% endslot %}\n| -- {% endslot %} ---\n| ------\n| -- {% component \"mycomp\" %} ---\n| ---- {% slot \"myslot\" %} ---\n| ------- JKL {{ my_var }}\n| ------- {% slot \"myslot_inner\" %}\n| ---------- MNO {{ my_var }}\n| ------- {% endslot %}\n| ---- {% endslot %} ---\n| -- {% endcomponent %} ---\n| ----\n| -- {% slot \"myslot2\" %} ---\n| ---- PQR {{ my_var }}\n| -- {% endslot %} ---\n| -------\n| -- {% for slot_name in slots %} ---\n| ---- {% component \"mycomp\" %} ---\n| ------- {% slot slot_name %}\n| ---------- STU {{ slot_name }}\n| ------- {% endslot %}\n| ---- {% endcomponent %} ---\n| -- {% endfor %} ---\n| ----\n| -- {% component \"mycomp\" %} ---\n| ---- {% for slot_name in slots %} ---\n| ------ {% fill slot_name %} ---\n| -------- {% slot slot_name %} ---\n| ---------- XYZ {{ slot_name }}\n| --------- {% endslot %}\n| ------- {% endfill %}\n| ---- {% endfor %} ---\n| -- {% endcomponent %} ---\n| -------\n</code></pre></p> </li> <li> <p>Given the above, we want to render the slots with <code>{% fill %}</code> tag that were defined OUTSIDE of this template. How do I do that?</p> <p>NOTE: Before v0.110, slots were resolved statically, by walking down the Django Template and Nodes. However, this did not allow for using for loops or other variables defined in the template.</p> <p>Currently, this consists of 2 steps:</p> <ol> <li> <p>If a component is rendered within a template using <code>{% component %}</code> tag, determine the given <code>{% fill %}</code> tags in the component's body (the content in between <code>{% component %}</code> and <code>{% endcomponent %}</code>).</p> <p>After this step, we know about all the fills that were passed to the component.</p> </li> <li> <p>Then we simply render the template as usual. And then we reach the <code>{% slot %}</code> tag, we search the context for the available fills.</p> <ul> <li>If there IS a fill with the same name as the slot, we render the fill.</li> <li>If the slot is marked <code>default</code>, and there is a fill named <code>default</code>, then we render that.</li> <li>Otherwise, we render the slot's default content.</li> </ul> </li> </ol> </li> <li> <p>Obtaining the fills from <code>{% fill %}</code>.</p> <p>When a component is rendered with <code>{% component %}</code> tag, and it has some content in between <code>{% component %}</code> and <code>{% endcomponent %}</code>, we want to figure out if that content is a default slot (no <code>{% fill %}</code> used), or if there is a collection of named <code>{% fill %}</code> tags:</p> <p>Default slot:</p> <pre><code>| -- {% component \"mycomp\" %} ---\n| ---- STU {{ slot_name }}\n| -- {% endcomponent %} ---\n</code></pre> <p>Named slots:</p> <pre><code>| -- {% component \"mycomp\" %} ---\n| ---- {% fill \"slot_a\" %}\n| ------ STU\n| ---- {% endslot %}\n| ---- {% fill \"slot_b\" %}\n| ------ XYZ\n| ---- {% endslot %}\n| -- {% endcomponent %} ---\n</code></pre> <p>To respect any forloops or other variables defined within the template to which the fills may have access, we:</p> <ol> <li>Render the content between <code>{% component %}</code> and <code>{% endcomponent %}</code> using the context    outside of the component.</li> <li>When we reach a <code>{% fill %}</code> tag, we capture any variables that were created between    the <code>{% component %}</code> and <code>{% fill %}</code> tags.</li> <li>When we reach <code>{% fill %}</code> tag, we do not continue rendering deeper. Instead we    make a record that we found the fill tag with given name, kwargs, etc.</li> <li>After the rendering is done, we check if we've encountered any fills.    If yes, we expect only named fills. If no, we assume that the the component's body    is a default slot.</li> <li>Lastly we process the found fills, and make them available to the context, so any    slots inside the component may access these fills.</li> </ol> </li> <li> <p>Rendering slots</p> <p>Slot rendering works similarly to collecting fills, in a sense that we do not search for the slots ahead of the time, but instead let Django handle the rendering of the template, and we step in only when Django come across as <code>{% slot %}</code> tag.</p> <p>When we reach a slot tag, we search the context for the available fills.</p> <ul> <li>If there IS a fill with the same name as the slot, we render the fill.</li> <li>If the slot is marked <code>default</code>, and there is a fill named <code>default</code>, then we render that.</li> <li>Otherwise, we render the slot's default content.</li> </ul> </li> </ol>"},{"location":"guides/devguides/slot_rendering/#using-the-correct-context-in-slotfill-tags","title":"Using the correct context in {% slot/fill %} tags","text":"<p>In previous section, we said that the <code>{% fill %}</code> tags should be already rendered by the time they are inserted into the <code>{% slot %}</code> tags.</p> <p>This is not quite true. To help you understand, consider this complex case:</p> <pre><code>| -- {% for var in [1, 2, 3] %} ---\n| ---- {% component \"mycomp2\" %} ---\n| ------ {% fill \"first\" %}\n| ------- STU {{ my_var }}\n| -------     {{ var }}\n| ------ {% endfill %}\n| ------ {% fill \"second\" %}\n| -------- {% component var=var my_var=my_var %}\n| ---------- VWX {{ my_var }}\n| -------- {% endcomponent %}\n| ------ {% endfill %}\n| ---- {% endcomponent %} ---\n| -- {% endfor %} ---\n| -------\n</code></pre> <p>We want the forloop variables to be available inside the <code>{% fill %}</code> tags. Because of that, however, we CANNOT render the fills/slots in advance.</p> <p>Instead, our solution is closer to how Vue handles slots. In Vue, slots are effectively functions that accept a context variables and render some content.</p> <p>While we do not wrap the logic in a function, we do PREPARE IN ADVANCE: 1. The content that should be rendered for each slot 2. The context variables from <code>get_context_data()</code></p> <p>Thus, once we reach the <code>{% slot %}</code> node, in it's <code>render()</code> method, we access the data above, and, depending on the <code>context_behavior</code> setting, include the current context or not. For more info, see <code>SlotNode.render()</code>.</p>"},{"location":"guides/devguides/slots_and_blocks/","title":"Using slot and block tags","text":"<ol> <li> <p>First let's clarify how <code>include</code> and <code>extends</code> tags work inside components.</p> <p>When component template includes <code>include</code> or <code>extends</code> tags, it's as if the \"included\" template was inlined. So if the \"included\" template contains <code>slot</code> tags, then the component uses those slots.</p> <p>If you have a template <code>abc.html</code>: <pre><code>&lt;div&gt;\n  hello\n  {% slot \"body\" %}{% endslot %}\n&lt;/div&gt;\n</code></pre></p> <p>And components that make use of <code>abc.html</code> via <code>include</code> or <code>extends</code>: <pre><code>from django_components import Component, register\n\n@register(\"my_comp_extends\")\nclass MyCompWithExtends(Component):\n    template = \"\"\"{% extends \"abc.html\" %}\"\"\"\n\n@register(\"my_comp_include\")\nclass MyCompWithInclude(Component):\n    template = \"\"\"{% include \"abc.html\" %}\"\"\"\n</code></pre></p> <p>Then you can set slot fill for the slot imported via <code>include/extends</code>:</p> <pre><code>{% component \"my_comp_extends\" %}\n    {% fill \"body\" %}\n        123\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>And it will render: <pre><code>&lt;div&gt;\n  hello\n  123\n&lt;/div&gt;\n</code></pre></p> </li> <li> <p>Slot and block</p> <p>If you have a template <code>abc.html</code> like so:</p> <pre><code>&lt;div&gt;\n  hello\n  {% block inner %}\n    1\n    {% slot \"body\" %}\n      2\n    {% endslot %}\n  {% endblock %}\n&lt;/div&gt;\n</code></pre> <p>and component <code>my_comp</code>:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template_file = \"abc.html\"\n</code></pre> <p>Then:</p> <ol> <li> <p>Since the <code>block</code> wasn't overriden, you can use the <code>body</code> slot:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"body\" %}\n        XYZ\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>And we get:</p> <pre><code>&lt;div&gt;hello 1 XYZ&lt;/div&gt;\n</code></pre> </li> <li> <p><code>blocks</code> CANNOT be overriden through the <code>component</code> tag, so something like this:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"body\" %}\n        XYZ\n    {% endfill %}\n{% endcomponent %}\n{% block \"inner\" %}\n    456\n{% endblock %}\n</code></pre> <p>Will still render the component content just the same:</p> <pre><code>&lt;div&gt;hello 1 XYZ&lt;/div&gt;\n</code></pre> </li> <li> <p>You CAN override the <code>block</code> tags of <code>abc.html</code> if the component template     uses <code>extends</code>. In that case, just as you would expect, the <code>block inner</code> inside     <code>abc.html</code> will render <code>OVERRIDEN</code>:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n        {% extends \"abc.html\" %}\n        {% block inner %}\n          OVERRIDEN\n        {% endblock %}\n    \"\"\"\n</code></pre> </li> <li> <p>This is where it gets interesting (but still intuitive). You can insert even     new <code>slots</code> inside these \"overriding\" blocks:</p> <pre><code>@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"\"\"\n      {% extends \"abc.html\" %}\n\n      {% load component_tags %}\n      {% block \"inner\" %}\n        OVERRIDEN\n        {% slot \"new_slot\" %}\n          hello\n        {% endslot %}\n      {% endblock %}\n    \"\"\"\n</code></pre> <p>And you can then pass fill for this <code>new_slot</code> when rendering the component:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"new_slot\" %}\n        XYZ\n    {% endfill %}\n{% endcomponent %}\n</code></pre> <p>NOTE: Currently you can supply fills for both <code>new_slot</code> and <code>body</code> slots, and you will not get an error for an invalid/unknown slot name. But since <code>body</code> slot is not rendered, it just won't do anything. So this renders the same as above:</p> <pre><code>{% component \"my_comp\" %}\n    {% fill \"new_slot\" %}\n        XYZ\n    {% endfill %}\n    {% fill \"body\" %}\n        www\n    {% endfill %}\n{% endcomponent %}\n</code></pre> </li> </ol> </li> </ol>"},{"location":"guides/other/troubleshooting/","title":"Troubleshooting","text":"<p>As larger projects get more complex, it can be hard to debug issues. Django Components provides a number of tools and approaches that can help you with that.</p>"},{"location":"guides/other/troubleshooting/#component-and-slot-highlighting","title":"Component and slot highlighting","text":"<p>Django Components provides a visual debugging feature that helps you understand the structure and boundaries of your components and slots. When enabled, it adds a colored border and a label around each component and slot on your rendered page.</p> <p>To enable component and slot highlighting, set <code>debug_highlight_components</code> and/or <code>debug_highlight_slots</code> to <code>True</code> in your <code>settings.py</code> file:</p> <pre><code>from django_components import ComponentsSettings\n\nCOMPONENTS = ComponentsSettings(\n    debug_highlight_components=True,\n    debug_highlight_slots=True,\n)\n</code></pre> <p>Components will be highlighted with a blue border and label:</p> <p></p> <p>While the slots will be highlighted with a red border and label:</p> <p></p> <p>Warning</p> <p>Use this feature ONLY in during development. Do NOT use it in production.</p>"},{"location":"guides/other/troubleshooting/#component-path-in-errors","title":"Component path in errors","text":"<p>When an error occurs, the error message will show the path to the component that caused the error. E.g.</p> <pre><code>KeyError: \"An error occured while rendering components MyPage &gt; MyLayout &gt; MyComponent &gt; Childomponent(slot:content)\n</code></pre> <p>The error message contains also the slot paths, so if you have a template like this:</p> <pre><code>{% component \"my_page\" %}\n    {% slot \"content\" %}\n        {% component \"table\" %}\n            {% slot \"header\" %}\n                {% component \"table_header\" %}\n                    ...  {# ERROR HERE #}\n                {% endcomponent %}\n            {% endslot %}\n        {% endcomponent %}\n    {% endslot %}\n{% endcomponent %}\n</code></pre> <p>Then the error message will show the path to the component that caused the error:</p> <pre><code>KeyError: \"An error occured while rendering components my_page &gt; layout &gt; layout(slot:content) &gt; my_page(slot:content) &gt; table &gt; table(slot:header) &gt; table_header &gt; table_header(slot:content)\n</code></pre>"},{"location":"guides/other/troubleshooting/#debug-and-trace-logging","title":"Debug and trace logging","text":"<p>Django components supports logging with Django.</p> <p>To configure logging for Django components, set the <code>django_components</code> logger in <code>LOGGING</code> in <code>settings.py</code> (below).</p> <p>Also see the <code>settings.py</code> file in sampleproject for a real-life example.</p> <pre><code>import logging\nimport sys\n\nLOGGING = {\n    'version': 1,\n    'disable_existing_loggers': False,\n    \"handlers\": {\n        \"console\": {\n            'class': 'logging.StreamHandler',\n            'stream': sys.stdout,\n        },\n    },\n    \"loggers\": {\n        \"django_components\": {\n            \"level\": logging.DEBUG,\n            \"handlers\": [\"console\"],\n        },\n    },\n}\n</code></pre> <p>Info</p> <p>To set TRACE level, set <code>\"level\"</code> to <code>5</code>:</p> <pre><code>LOGGING = {\n    \"loggers\": {\n        \"django_components\": {\n            \"level\": 5,\n            \"handlers\": [\"console\"],\n        },\n    },\n}\n</code></pre>"},{"location":"guides/other/troubleshooting/#logger-levels","title":"Logger levels","text":"<p>As of v0.126, django-components primarily uses these logger levels:</p> <ul> <li><code>DEBUG</code>: Report on loading associated HTML / JS / CSS files, autodiscovery, etc.</li> <li><code>TRACE</code>: Detailed interaction of components and slots. Logs when template tags,   components, and slots are started / ended rendering, and when a slot is filled.</li> </ul>"},{"location":"guides/other/troubleshooting/#slot-origin","title":"Slot origin","text":"<p>When you pass a slot fill to a Component, the component and slot names is remebered on the slot object.</p> <p>Thus, you can check where a slot was filled from by printing it out:</p> <pre><code>class MyComponent(Component):\n    def on_render_before(self):\n        print(self.input.slots)\n</code></pre> <p>might print:</p> <pre><code>{\n    'content': &lt;Slot component_name='layout' slot_name='content'&gt;,\n    'header': &lt;Slot component_name='my_page' slot_name='header'&gt;,\n    'left_panel': &lt;Slot component_name='layout' slot_name='left_panel'&gt;,\n}\n</code></pre>"},{"location":"guides/other/troubleshooting/#agentic-debugging","title":"Agentic debugging","text":"<p>All the features above make django-components to work really well with coding AI agents like Github Copilot or CursorAI.</p> <p>To debug component rendering with LLMs, you want to provide the LLM with:</p> <ol> <li>The components source code</li> <li>The rendered output</li> <li>As much additional context as possible</li> </ol> <p>Your codebase already contains the components source code, but not the latter two.</p>"},{"location":"guides/other/troubleshooting/#providing-rendered-output","title":"Providing rendered output","text":"<p>To provide the LLM with the rendered output, you can simply export the rendered output to a file.</p> <pre><code>rendered = ProjectPage.render(...)\nwith open(\"result.html\", \"w\") as f:\n    f.write(rendered)\n</code></pre> <p>If you're using <code>render_to_response</code>, access the output from the <code>HttpResponse</code> object:</p> <pre><code>response = ProjectPage.render_to_response(...)\nwith open(\"result.html\", \"wb\") as f:\n    f.write(response.content)\n</code></pre>"},{"location":"guides/other/troubleshooting/#providing-contextual-logs","title":"Providing contextual logs","text":"<p>Next, we provide the agent with info on HOW we got the result that we have. We do so by providing the agent with the trace-level logs.</p> <p>In your <code>settings.py</code>, configure the trace-level logs to be written to the <code>django_components.log</code> file:</p> <pre><code>LOGGING = {\n    \"version\": 1,\n    \"disable_existing_loggers\": False,\n    \"handlers\": {\n        \"file\": {\n            \"class\": \"logging.FileHandler\",\n            \"filename\": \"django_components.log\",\n            \"mode\": \"w\",  # Overwrite the file each time\n        },\n    },\n    \"loggers\": {\n        \"django_components\": {\n            \"level\": 5,\n            \"handlers\": [\"file\"],\n        },\n    },\n}\n</code></pre>"},{"location":"guides/other/troubleshooting/#prompting-the-agent","title":"Prompting the agent","text":"<p>Now, you can prompt the agent and include the trace log and the rendered output to guide the agent with debugging.</p> <p>I have a django-components (DJC) project. DJC is like if Vue or React component-based web development but made for Django ecosystem.</p> <p>In the view <code>project_view</code>, I am rendering the <code>ProjectPage</code> component. However, the output is not as expected. The output is missing the tabs.</p> <p>You have access to the full log trace in <code>django_components.log</code>.</p> <p>You can also see the rendered output in <code>result.html</code>.</p> <p>With this information, help me debug the issue.</p> <p>First, tell me what kind of info you would be looking for in the logs, and why (how it relates to understanding the cause of the bug).</p> <p>Then tell me if that info was there, and what the implications are.</p> <p>Finally, tell me what you would do to fix the issue.</p>"},{"location":"guides/setup/caching/","title":"Caching","text":"<p>This page describes the kinds of assets that django-components caches and how to configure the cache backends.</p>"},{"location":"guides/setup/caching/#components-js-and-css-files","title":"Component's JS and CSS files","text":"<p>django-components caches the JS and CSS files associated with your components. This enables components to be rendered as HTML fragments and still having the associated JS and CSS files loaded with them.</p> <p>This includes:</p> <ul> <li>Inlined JS/CSS defined via <code>Component.js</code> and <code>Component.css</code></li> <li>JS/CSS variables generated from <code>get_js_data()</code> and <code>get_css_data()</code></li> </ul> <p>By default, django-components uses Django's local memory cache backend to store these assets. You can configure it to use any of your Django cache backends by setting the <code>COMPONENTS.cache</code> option in your settings:</p> <pre><code>COMPONENTS = {\n    # Name of the cache backend to use\n    \"cache\": \"my-cache-backend\",\n}\n</code></pre> <p>The value should be the name of one of your configured cache backends from Django's <code>CACHES</code> setting.</p> <p>For example, to use Redis for caching component assets:</p> <pre><code>CACHES = {\n    \"default\": {\n        \"BACKEND\": \"django.core.cache.backends.locmem.LocMemCache\",\n    },\n    \"component-media\": {\n        \"BACKEND\": \"django.core.cache.backends.redis.RedisCache\",\n        \"LOCATION\": \"redis://127.0.0.1:6379/1\",\n    }\n}\n\nCOMPONENTS = {\n    # Use the Redis cache backend\n    \"cache\": \"component-media\",\n}\n</code></pre> <p>See <code>COMPONENTS.cache</code> for more details about this setting.</p>"},{"location":"guides/setup/development_server/","title":"Development server","text":""},{"location":"guides/setup/development_server/#reload-dev-server-on-component-file-changes","title":"Reload dev server on component file changes","text":"<p>This is relevant if you are using the project structure as shown in our examples, where HTML, JS, CSS and Python are in separate files and nested in a directory.</p> <pre><code>sampleproject/\n\u251c\u2500\u2500 components/\n\u2502   \u2514\u2500\u2500 calendar/\n\u2502       \u251c\u2500\u2500 calendar.py\n\u2502       \u2514\u2500\u2500 calendar.html\n\u2502       \u2514\u2500\u2500 calendar.css\n\u2502       \u2514\u2500\u2500 calendar.js\n\u251c\u2500\u2500 sampleproject/\n\u251c\u2500\u2500 manage.py\n\u2514\u2500\u2500 requirements.txt\n</code></pre> <p>In this case you may notice that when you are running a development server, the server sometimes does not reload when you change component files.</p> <p>From relevant StackOverflow thread:</p> <p>TL;DR is that the server won't reload if it thinks the changed file is in a templates directory, or in a nested sub directory of a templates directory. This is by design.</p> <p>To make the dev server reload on all component files, set <code>reload_on_file_change</code> to <code>True</code>. This configures Django to watch for component files too.</p> <p>Warning</p> <p>This setting should be enabled only for the dev environment!</p>"},{"location":"guides/setup/syntax_highlight/","title":"Syntax highlighting","text":""},{"location":"guides/setup/syntax_highlight/#vscode","title":"VSCode","text":"<ol> <li> <p>First install Python Inline Source Syntax Highlighting extension, it will give you syntax highlighting for the template, CSS, and JS.</p> </li> <li> <p>Next, in your component, set typings of <code>Component.template/css/js</code> to <code>types.django_html</code>, <code>types.css</code>, and <code>types.js</code> respectively. The extension will recognize these and will activate syntax highlighting.</p> </li> </ol> [project root]/components/calendar.py<pre><code># In a file called [project root]/components/calendar.py\nfrom django_components import Component, register, types\n\n@register(\"calendar\")\nclass Calendar(Component):\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n\n    template: types.django_html = \"\"\"\n        &lt;div class=\"calendar-component\"&gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css: types.css = \"\"\"\n        .calendar-component {\n            width: 200px;\n            background: pink;\n        }\n        .calendar-component span {\n            font-weight: bold;\n        }\n    \"\"\"\n\n    js: types.js = \"\"\"\n        (function(){\n            if (document.querySelector(\".calendar-component\")) {\n                document.querySelector(\".calendar-component\").onclick = function(){ alert(\"Clicked calendar!\"); };\n            }\n        })()\n    \"\"\"\n</code></pre>"},{"location":"guides/setup/syntax_highlight/#pycharm-or-other-jetbrains-ides","title":"Pycharm (or other Jetbrains IDEs)","text":"<p>With PyCharm (or any other editor from Jetbrains), you don't need to use <code>types.django_html</code>, <code>types.css</code>, <code>types.js</code> since Pycharm uses language injections. You only need to write the comments <code># language=&lt;lang&gt;</code> above the variables.</p> <pre><code>from django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    def get_context_data(self, date):\n        return {\n            \"date\": date,\n        }\n\n    # language=HTML\n    template= \"\"\"\n        &lt;div class=\"calendar-component\"&gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    # language=CSS\n    css = \"\"\"\n        .calendar-component {\n            width: 200px;\n            background: pink;\n        }\n        .calendar-component span {\n            font-weight: bold;\n        }\n    \"\"\"\n\n    # language=JS\n    js = \"\"\"\n        (function(){\n            if (document.querySelector(\".calendar-component\")) {\n                document.querySelector(\".calendar-component\").onclick = function(){ alert(\"Clicked calendar!\"); };\n            }\n        })()\n    \"\"\"\n</code></pre>"},{"location":"guides/setup/syntax_highlight/#pygments","title":"Pygments","text":"<p>Pygments is a syntax highlighting library written in Python. It's also what's used by this documentation site (mkdocs-material) to highlight code blocks.</p> <p>To write code blocks with syntax highlighting, you need to install the <code>pygments-djc</code> package.</p> <pre><code>pip install pygments-djc\n</code></pre> <p>And then initialize it by importing <code>pygments_djc</code>:</p> <pre><code>import pygments_djc\n</code></pre> <p>Now you can write code blocks with syntax highlighting.</p> <pre><code>\\```djc_py\nfrom django_components import Component, register\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template= \"\"\"\n        &lt;div class=\"calendar-component\"&gt;\n            Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css = \"\"\"\n        .calendar-component {\n            width: 200px;\n            background: pink;\n        }\n        .calendar-component span {\n            font-weight: bold;\n        }\n    \"\"\"\n\\```\n</code></pre>"},{"location":"overview/code_of_conduct/","title":"Contributor Covenant Code of Conduct","text":""},{"location":"overview/code_of_conduct/#our-pledge","title":"Our Pledge","text":"<p>In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.</p>"},{"location":"overview/code_of_conduct/#our-standards","title":"Our Standards","text":"<p>Examples of behavior that contributes to creating a positive environment include:</p> <ul> <li>Using welcoming and inclusive language</li> <li>Being respectful of differing viewpoints and experiences</li> <li>Gracefully accepting constructive criticism</li> <li>Focusing on what is best for the community</li> <li>Showing empathy towards other community members</li> </ul> <p>Examples of unacceptable behavior by participants include:</p> <ul> <li>The use of sexualized language or imagery and unwelcome sexual attention or  advances</li> <li>Trolling, insulting/derogatory comments, and personal or political attacks</li> <li>Public or private harassment</li> <li>Publishing others' private information, such as a physical or electronic  address, without explicit permission</li> <li>Other conduct which could reasonably be considered inappropriate in a  professional setting</li> </ul>"},{"location":"overview/code_of_conduct/#our-responsibilities","title":"Our Responsibilities","text":"<p>Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.</p> <p>Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.</p>"},{"location":"overview/code_of_conduct/#scope","title":"Scope","text":"<p>This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.</p>"},{"location":"overview/code_of_conduct/#enforcement","title":"Enforcement","text":"<p>Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at emil@emilstenstrom.se. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.</p> <p>Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.</p>"},{"location":"overview/code_of_conduct/#attribution","title":"Attribution","text":"<p>This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html</p> <p>For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq</p>"},{"location":"overview/community/","title":"Community","text":""},{"location":"overview/community/#community-questions","title":"Community questions","text":"<p>The best place to ask questions is in our Github Discussion board.</p> <p>Please, before opening a new discussion, check if similar discussion wasn't opened already.</p>"},{"location":"overview/community/#community-examples","title":"Community examples","text":"<p>One of our goals with <code>django-components</code> is to make it easy to share components between projects (see how to package components). If you have a set of components that you think would be useful to others, please open a pull request to add them to the list below.</p> <ul> <li> <p>django-htmx-components: A set of components for use with htmx. Try out the live demo.</p> </li> <li> <p>djc-heroicons: A component that renders icons from Heroicons.com.</p> </li> </ul>"},{"location":"overview/compatibility/","title":"Compatibility","text":"<p>Django-components supports all supported combinations versions of Django and Python.</p> Python version Django version 3.8 4.2 3.9 4.2 3.10 4.2, 5.0, 5.1 3.11 4.2, 5.0, 5.1 3.12 4.2, 5.0, 5.1 3.13 5.1"},{"location":"overview/contributing/","title":"Contributing","text":""},{"location":"overview/contributing/#bug-reports","title":"Bug reports","text":"<p>If you find a bug, please open an issue with detailed description of what happened.</p>"},{"location":"overview/contributing/#bug-fixes","title":"Bug fixes","text":"<p>If you found a fix for a bug or typo, go ahead and open a PR with a fix. We'll help you out with the rest!</p>"},{"location":"overview/contributing/#feature-requests","title":"Feature requests","text":"<p>For feature requests or suggestions, please open either a discussion or an issue.</p>"},{"location":"overview/contributing/#getting-involved","title":"Getting involved","text":"<p>django_components is still under active development, and there's much to build, so come aboard!</p>"},{"location":"overview/contributing/#sponsoring","title":"Sponsoring","text":"<p>Another way you can get involved is by donating to the development of django_components.</p>"},{"location":"overview/development/","title":"Development","text":""},{"location":"overview/development/#install-locally-and-run-the-tests","title":"Install locally and run the tests","text":"<p>Start by forking the project by clicking the Fork button up in the right corner in the GitHub. This makes a copy of the repository in your own name. Now you can clone this repository locally and start adding features:</p> <pre><code>git clone https://github.com/&lt;your GitHub username&gt;/django-components.git\ncd django-components\n</code></pre> <p>To quickly run the tests install the local dependencies by running:</p> <pre><code>pip install -r requirements-dev.txt\n</code></pre> <p>You also have to install this local django-components version. Use <code>-e</code> for editable mode so you don't have to re-install after every change:</p> <pre><code>pip install -e .\n</code></pre> <p>Now you can run the tests to make sure everything works as expected:</p> <pre><code>pytest\n</code></pre> <p>The library is also tested across many versions of Python and Django. To run tests that way:</p> <pre><code>pyenv install -s 3.8\npyenv install -s 3.9\npyenv install -s 3.10\npyenv install -s 3.11\npyenv install -s 3.12\npyenv install -s 3.13\npyenv local 3.8 3.9 3.10 3.11 3.12 3.13\ntox -p\n</code></pre> <p>To run tests for a specific Python version, use:</p> <pre><code>tox -e py38\n</code></pre> <p>NOTE: See the available environments in <code>tox.ini</code>.</p> <p>And to run only linters, use:</p> <pre><code>tox -e mypy,flake8,isort,black\n</code></pre>"},{"location":"overview/development/#running-playwright-tests","title":"Running Playwright tests","text":"<p>We use Playwright for end-to-end tests. You will therefore need to install Playwright to be able to run these tests.</p> <p>Luckily, Playwright makes it very easy:</p> <pre><code>pip install -r requirements-dev.txt\nplaywright install chromium --with-deps\n</code></pre> <p>After Playwright is ready, simply run the tests with <code>tox</code>:</p> <pre><code>tox\n</code></pre>"},{"location":"overview/development/#developing-against-live-django-app","title":"Developing against live Django app","text":"<p>How do you check that your changes to django-components project will work in an actual Django project?</p> <p>Use the sampleproject demo project to validate the changes:</p> <ol> <li> <p>Navigate to sampleproject directory:</p> <pre><code>cd sampleproject\n</code></pre> </li> <li> <p>Install dependencies from the requirements.txt file:</p> <pre><code>pip install -r requirements.txt\n</code></pre> </li> <li> <p>Link to your local version of django-components:</p> <pre><code>pip install -e ..\n</code></pre> <p>Note</p> <p>The path to the local version (in this case <code>..</code>) must point to the directory that has the <code>setup.py</code> file.</p> </li> <li> <p>Start Django server     <pre><code>python manage.py runserver\n</code></pre></p> </li> </ol> <p>Once the server is up, it should be available at http://127.0.0.1:8000.</p> <p>To display individual components, add them to the <code>urls.py</code>, like in the case of http://127.0.0.1:8000/greeting</p>"},{"location":"overview/development/#building-js-code","title":"Building JS code","text":"<p>django_components uses a bit of JS code to:</p> <ul> <li>Manage the loading of JS and CSS files used by the components</li> <li>Allow to pass data from Python to JS</li> </ul> <p>When you make changes to this JS code, you also need to compile it:</p> <ol> <li> <p>Make sure you are inside <code>src/django_components_js</code>:</p> <pre><code>cd src/django_components_js\n</code></pre> </li> <li> <p>Install the JS dependencies</p> <pre><code>npm install\n</code></pre> </li> <li> <p>Compile the JS/TS code:</p> <pre><code>python build.py\n</code></pre> <p>The script will combine all JS/TS code into a single <code>.js</code> file, minify it, and copy it to <code>django_components/static/django_components/django_components.min.js</code>.</p> </li> </ol>"},{"location":"overview/development/#packaging-and-publishing","title":"Packaging and publishing","text":"<p>To package the library into a distribution that can be published to PyPI, run:</p> <pre><code># Install pypa/build\npython -m pip install build --user\n# Build a binary wheel and a source tarball\npython -m build --sdist --wheel --outdir dist/ .\n</code></pre> <p>To publish the package to PyPI, use <code>twine</code> (See Python user guide):</p> <pre><code>twine upload --repository pypi dist/* -u __token__ -p &lt;PyPI_TOKEN&gt;\n</code></pre> <p>See the full workflow here.</p>"},{"location":"overview/development/#development-guides","title":"Development guides","text":"<p>Head over to Dev guides for a deep dive into how django_components' features are implemented.</p>"},{"location":"overview/installation/","title":"Installation","text":"<ol> <li> <p>Install <code>django_components</code> into your environment:</p> <pre><code>pip install django_components\n</code></pre> </li> <li> <p>Load <code>django_components</code> into Django by adding it into <code>INSTALLED_APPS</code> in in your settings file:</p> <pre><code>INSTALLED_APPS = [\n    ...,\n    'django_components',\n]\n</code></pre> </li> <li> <p><code>BASE_DIR</code> setting is required. Ensure that it is defined:</p> <pre><code>from pathlib import Path\n\nBASE_DIR = Path(__file__).resolve().parent.parent\n</code></pre> </li> <li> <p>Optional. Set <code>COMPONENTS.dirs</code>    and/or <code>COMPONENTS.app_dirs</code>    so django_components knows where to find component HTML, JS and CSS files:</p> <p>If <code>COMPONENTS.dirs</code> is omitted, django-components will by default look for a top-level <code>/components</code> directory, <code>{BASE_DIR}/components</code>.</p> <pre><code>from django_components import ComponentsSettings\n\nCOMPONENTS = ComponentsSettings(\n    dirs=[\n        ...,\n        Path(BASE_DIR) / \"components\",\n    ],\n)\n</code></pre> <p>In addition to <code>COMPONENTS.dirs</code>, django_components will also load components from app-level directories, such as <code>my-app/components/</code>. The directories within apps are configured with <code>COMPONENTS.app_dirs</code>, and the default is <code>[app]/components</code>.</p> <p>Note</p> <p>The input to <code>COMPONENTS.dirs</code> is the same as for <code>STATICFILES_DIRS</code>, and the paths must be full paths. See Django docs.</p> </li> <li> <p>Next, modify <code>TEMPLATES</code> section of settings.py as follows:</p> <ul> <li>Remove <code>'APP_DIRS': True,</code><ul> <li>NOTE: Instead of <code>APP_DIRS: True</code>, we will use   <code>django.template.loaders.app_directories.Loader</code>,   which has the same effect.</li> </ul> </li> <li>Add <code>loaders</code> to <code>OPTIONS</code> list and set it to following value:</li> </ul> <p>This allows Django to load component HTML files as Django templates.</p> <pre><code>TEMPLATES = [\n    {\n        ...,\n        'OPTIONS': {\n            'loaders':[(\n                'django.template.loaders.cached.Loader', [\n                    # Default Django loader\n                    'django.template.loaders.filesystem.Loader',\n                    # Including this is the same as APP_DIRS=True\n                    'django.template.loaders.app_directories.Loader',\n                    # Components loader\n                    'django_components.template_loader.Loader',\n                ]\n            )],\n        },\n    },\n]\n</code></pre> </li> </ol>"},{"location":"overview/installation/#adding-support-for-js-and-css","title":"Adding support for JS and CSS","text":"<p>If you want to use JS or CSS with components, you will need to:</p> <ol> <li> <p>Add <code>\"django_components.finders.ComponentsFileSystemFinder\"</code> to <code>STATICFILES_FINDERS</code> in your settings file.</p> <p>This allows Django to serve component JS and CSS as static files.</p> <pre><code>STATICFILES_FINDERS = [\n    # Default finders\n    \"django.contrib.staticfiles.finders.FileSystemFinder\",\n    \"django.contrib.staticfiles.finders.AppDirectoriesFinder\",\n    # Django components\n    \"django_components.finders.ComponentsFileSystemFinder\",\n]\n</code></pre> </li> <li> <p>Add <code>ComponentDependencyMiddleware</code>    to <code>MIDDLEWARE</code> setting.</p> <p>The middleware searches the outgoing HTML for all components that were rendered to generate the HTML, and adds the JS and CSS associated with those components.</p> <pre><code>MIDDLEWARE = [\n    ...\n    \"django_components.middleware.ComponentDependencyMiddleware\",\n]\n</code></pre> <p>Read more in Rendering JS/CSS dependencies.</p> </li> <li> <p>Add django-component's URL paths to your <code>urlpatterns</code>:</p> <pre><code>from django.urls import include, path\n\nurlpatterns = [\n    ...\n    path(\"\", include(\"django_components.urls\")),\n]\n</code></pre> </li> <li> <p>Optional. If you want to change where the JS and CSS is rendered, use     <code>{% component_js_dependencies %}</code>     and <code>{% component_css_dependencies %}</code>.</p> <p>By default, the JS <code>&lt;script&gt;</code> and CSS <code>&lt;link&gt;</code> tags are automatically inserted into the HTML (See JS and CSS output locations).</p> <pre><code>&lt;!doctype html&gt;\n&lt;html&gt;\n  &lt;head&gt;\n    ...\n    {% component_css_dependencies %}\n  &lt;/head&gt;\n  &lt;body&gt;\n    ...\n    {% component_js_dependencies %}\n  &lt;/body&gt;\n&lt;/html&gt;\n</code></pre> </li> <li> <p>Optional. By default, components' JS and CSS files are cached in memory.</p> <p>If you want to change the cache backend, set the <code>COMPONENTS.cache</code> setting.</p> <p>Read more in Caching.</p> </li> </ol>"},{"location":"overview/installation/#optional","title":"Optional","text":""},{"location":"overview/installation/#builtin-template-tags","title":"Builtin template tags","text":"<p>To avoid loading the app in each template using <code>{% load component_tags %}</code>, you can add the tag as a 'builtin' in settings.py</p> <pre><code>TEMPLATES = [\n    {\n        ...,\n        'OPTIONS': {\n            'builtins': [\n                'django_components.templatetags.component_tags',\n            ]\n        },\n    },\n]\n</code></pre> <p>Now you're all set! Read on to find out how to build your first component.</p>"},{"location":"overview/license/","title":"License","text":"<p>MIT License</p> <p>Copyright (c) 2019 Emil Stenstr\u00f6m</p> <p>Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p> <p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p> <p>THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>"},{"location":"overview/performance/","title":"Performance","text":"<p>We track the performance of <code>django-components</code> using ASV.</p> <p>See the benchmarks dashboard.</p>"},{"location":"overview/security_notes/","title":"Security notes \ud83d\udea8","text":"<p>It is strongly recommended to read this section before using django-components in production.</p>"},{"location":"overview/security_notes/#static-files","title":"Static files","text":"<p>TL;DR: No action needed from v0.100 onwards. Before v0.100, use <code>safer_staticfiles</code> to avoid exposing backend logic.</p> <p>Components can be organized however you prefer. That said, our prefered way is to keep the files of a component close together by bundling them in the same directory.</p> <p>This means that files containing backend logic, such as Python modules and HTML templates, live in the same directory as static files, e.g. JS and CSS.</p> <p>From v0.100 onwards, we keep component files (as defined by <code>COMPONENTS.dirs</code> and <code>COMPONENTS.app_dirs</code>) separate from the rest of the static files (defined by <code>STATICFILES_DIRS</code>). That way, the Python and HTML files are NOT exposed by the server. Only the static JS, CSS, and other common formats.</p> <p>Note</p> <p>If you need to expose different file formats, you can configure these with <code>COMPONENTS.static_files_allowed</code> and <code>COMPONENTS.static_files_forbidden</code>.</p>"},{"location":"overview/security_notes/#static-files-prior-to-v0100","title":"Static files prior to v0.100","text":"<p>Prior to v0.100, if your were using django.contrib.staticfiles to collect static files, no distinction was made between the different kinds of files.</p> <p>As a result, your Python code and templates may inadvertently become available on your static file server. You probably don't want this, as parts of your backend logic will be exposed, posing a potential security vulnerability.</p> <p>From v0.27 until v0.100, django-components shipped with an additional installable app django_components.safer_staticfiles. It was a drop-in replacement for django.contrib.staticfiles. Its behavior is 100% identical except it ignores <code>.py</code> and <code>.html</code> files, meaning these will not end up on your static files server.</p> <p>To use it, add it to <code>INSTALLED_APPS</code> and remove django.contrib.staticfiles.</p> <pre><code>INSTALLED_APPS = [\n    # 'django.contrib.staticfiles',   # &lt;-- REMOVE\n    'django_components',\n    'django_components.safer_staticfiles'  # &lt;-- ADD\n]\n</code></pre> <p>If you are on an pre-v0.27 version of django-components, your alternatives are:</p> <ul> <li>a) passing <code>--ignore &lt;pattern&gt;</code> options to the collecstatic CLI command,</li> <li>b) defining a subclass of StaticFilesConfig.</li> </ul> <p>Both routes are described in the official docs of the staticfiles app.</p> <p>Note that <code>safer_staticfiles</code> excludes the <code>.py</code> and <code>.html</code> files for collectstatic command:</p> <pre><code>python manage.py collectstatic\n</code></pre> <p>but it is ignored on the development server:</p> <pre><code>python manage.py runserver\n</code></pre> <p>For a step-by-step guide on deploying production server with static files, see the demo project.</p> <p>See the older versions of the sampleproject for a setup with pre-v0.100 version.</p>"},{"location":"overview/welcome/","title":"Welcome to Django Components","text":"<p><code>django-components</code> combines Django's templating system with the modularity seen in modern frontend frameworks like Vue or React.</p> <p>With <code>django-components</code> you can support Django projects small and large without leaving the Django ecosystem.</p>"},{"location":"overview/welcome/#quickstart","title":"Quickstart","text":"<p>A component in django-components can be as simple as a Django template and Python code to declare the component:</p> components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n</code></pre> <p>Or a combination of Django template, Python, CSS, and Javascript:</p> components/calendar/calendar.html<pre><code>&lt;div class=\"calendar\"&gt;\n  Today's date is &lt;span&gt;{{ date }}&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> components/calendar/calendar.css<pre><code>.calendar {\n  width: 200px;\n  background: pink;\n}\n</code></pre> components/calendar/calendar.js<pre><code>document.querySelector(\".calendar\").onclick = () =&gt; {\n  alert(\"Clicked calendar!\");\n};\n</code></pre> components/calendar/calendar.py<pre><code>from django_components import Component\n\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n    js_file = \"calendar.js\"\n    css_file = \"calendar.css\"\n\n    def get_context_data(self, date):\n        return {\"date\": date}\n</code></pre> <p>Use the component like this:</p> <pre><code>{% component \"calendar\" date=\"2024-11-06\" %}{% endcomponent %}\n</code></pre> <p>And this is what gets rendered:</p> <pre><code>&lt;div class=\"calendar-component\"&gt;\n  Today's date is &lt;span&gt;2024-11-06&lt;/span&gt;\n&lt;/div&gt;\n</code></pre> <p>Read on to learn about all the exciting details and configuration possibilities!</p> <p>(If you instead prefer to jump right into the code, check out the example project)</p>"},{"location":"overview/welcome/#features","title":"Features","text":""},{"location":"overview/welcome/#modern-and-modular-ui","title":"Modern and modular UI","text":"<ul> <li>Create self-contained, reusable UI elements.</li> <li>Each component can include its own HTML, CSS, and JS, or additional third-party JS and CSS.</li> <li>HTML, CSS, and JS can be defined on the component class, or loaded from files.</li> </ul> <pre><code>from django_components import Component\n\n@register(\"calendar\")\nclass Calendar(Component):\n    template = \"\"\"\n        &lt;div class=\"calendar\"&gt;\n            Today's date is\n            &lt;span&gt;{{ date }}&lt;/span&gt;\n        &lt;/div&gt;\n    \"\"\"\n\n    css = \"\"\"\n        .calendar {\n            width: 200px;\n            background: pink;\n        }\n    \"\"\"\n\n    js = \"\"\"\n        document.querySelector(\".calendar\")\n            .addEventListener(\"click\", () =&gt; {\n                alert(\"Clicked calendar!\");\n            });\n    \"\"\"\n\n    # Additional JS and CSS\n    class Media:\n        js = [\"https://cdn.jsdelivr.net/npm/htmx.org@2.1.1/dist/htmx.min.js\"]\n        css = [\"bootstrap/dist/css/bootstrap.min.css\"]\n\n    # Variables available in the template\n    def get_context_data(self, date):\n        return {\n            \"date\": date\n        }\n</code></pre>"},{"location":"overview/welcome/#composition-with-slots","title":"Composition with slots","text":"<ul> <li>Render components inside templates with <code>{% component %}</code> tag.</li> <li>Compose them with <code>{% slot %}</code> and <code>{% fill %}</code> tags.</li> <li>Vue-like slot system, including scoped slots.</li> </ul> <pre><code>{% component \"Layout\"\n    bookmarks=bookmarks\n    breadcrumbs=breadcrumbs\n%}\n    {% fill \"header\" %}\n        &lt;div class=\"flex justify-between gap-x-12\"&gt;\n            &lt;div class=\"prose\"&gt;\n                &lt;h3&gt;{{ project.name }}&lt;/h3&gt;\n            &lt;/div&gt;\n            &lt;div class=\"font-semibold text-gray-500\"&gt;\n                {{ project.start_date }} - {{ project.end_date }}\n            &lt;/div&gt;\n        &lt;/div&gt;\n    {% endfill %}\n\n    {# Access data passed to `{% slot %}` with `data` #}\n    {% fill \"tabs\" data=\"tabs_data\" %}\n        {% component \"TabItem\" header=\"Project Info\" %}\n            {% component \"ProjectInfo\"\n                project=project\n                project_tags=project_tags\n                attrs:class=\"py-5\"\n                attrs:width=tabs_data.width\n            / %}\n        {% endcomponent %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"overview/welcome/#extended-template-tags","title":"Extended template tags","text":"<p><code>django-components</code> extends Django's template tags syntax with:</p> <ul> <li>Literal lists and dictionaries in template tags</li> <li>Self-closing tags <code>{% mytag / %}</code></li> <li>Multi-line template tags</li> <li>Spread operator <code>...</code> to dynamically pass args or kwargs into the template tag</li> <li>Nested template tags like <code>\"{{ first_name }} {{ last_name }}\"</code></li> <li>Flat definition of dictionary keys <code>attr:key=val</code></li> </ul> <pre><code>{% component \"table\"\n    ...default_attrs\n    title=\"Friend list for {{ user.name }}\"\n    headers=[\"Name\", \"Age\", \"Email\"]\n    data=[\n        {\n            \"name\": \"John\"|upper,\n            \"age\": 30|add:1,\n            \"email\": \"john@example.com\",\n            \"hobbies\": [\"reading\"],\n        },\n        {\n            \"name\": \"Jane\"|upper,\n            \"age\": 25|add:1,\n            \"email\": \"jane@example.com\",\n            \"hobbies\": [\"reading\", \"coding\"],\n        },\n    ],\n    attrs:class=\"py-4 ma-2 border-2 border-gray-300 rounded-md\"\n/ %}\n</code></pre>"},{"location":"overview/welcome/#html-fragment-support","title":"HTML fragment support","text":"<p><code>django-components</code> makes intergration with HTMX, AlpineJS or jQuery easy by allowing components to be rendered as HTML fragments:</p> <ul> <li> <p>Components's JS and CSS is loaded automatically when the fragment is inserted into the DOM.</p> </li> <li> <p>Expose components as views with <code>get</code>, <code>post</code>, <code>put</code>, <code>patch</code>, <code>delete</code> methods</p> </li> </ul> <pre><code># components/calendar/calendar.py\n@register(\"calendar\")\nclass Calendar(Component):\n    template_file = \"calendar.html\"\n\n    def get(self, request, *args, **kwargs):\n        page = request.GET.get(\"page\", 1)\n        return self.render_to_response(\n            kwargs={\n                \"page\": page,\n            }\n        )\n\n    def get_context_data(self, page):\n        return {\n            \"page\": page,\n        }\n\n# urls.py\npath(\"calendar/\", Calendar.as_view()),\n</code></pre>"},{"location":"overview/welcome/#type-hints","title":"Type hints","text":"<p>Opt-in to type hints by defining types for component's args, kwargs, slots, and more:</p> <pre><code>from typing import NotRequired, Tuple, TypedDict, SlotContent, SlotFunc\n\nButtonArgs = Tuple[int, str]\n\nclass ButtonKwargs(TypedDict):\n    variable: str\n    another: int\n    maybe_var: NotRequired[int] # May be omitted\n\nclass ButtonData(TypedDict):\n    variable: str\n\nclass ButtonSlots(TypedDict):\n    my_slot: NotRequired[SlotFunc]\n    another_slot: SlotContent\n\nButtonType = Component[ButtonArgs, ButtonKwargs, ButtonSlots, ButtonData, JsData, CssData]\n\nclass Button(ButtonType):\n    def get_context_data(self, *args, **kwargs):\n        self.input.args[0]  # int\n        self.input.kwargs[\"variable\"]  # str\n        self.input.slots[\"my_slot\"]  # SlotFunc[MySlotData]\n\n        return {}  # Error: Key \"variable\" is missing\n</code></pre> <p>When you then call <code>Button.render()</code> or <code>Button.render_to_response()</code>, you will get type hints:</p> <pre><code>Button.render(\n    # Error: First arg must be `int`, got `float`\n    args=(1.25, \"abc\"),\n    # Error: Key \"another\" is missing\n    kwargs={\n        \"variable\": \"text\",\n    },\n)\n</code></pre>"},{"location":"overview/welcome/#extensions","title":"Extensions","text":"<p>Django-components functionality can be extended with \"extensions\". Extensions allow for powerful customization and integrations. They can:</p> <ul> <li>Tap into lifecycle events, such as when a component is created, deleted, or registered.</li> <li>Add new attributes and methods to the components under an extension-specific nested class.</li> </ul> <p>Some of the planned extensions include:</p> <ul> <li>Caching</li> <li>AlpineJS integration</li> <li>Storybook integration</li> <li>Pydantic validation</li> <li>Component-level benchmarking with asv</li> </ul>"},{"location":"overview/welcome/#simple-testing","title":"Simple testing","text":"<ul> <li>Write tests for components with <code>@djc_test</code> decorator.</li> <li>The decorator manages global state, ensuring that tests don't leak.</li> <li>If using <code>pytest</code>, the decorator allows you to parametrize Django or Components settings.</li> <li>The decorator also serves as a stand-in for Django's <code>@override_settings</code>.</li> </ul> <pre><code>from djc_test import djc_test\n\nfrom components.my_component import MyTable\n\n@djc_test\ndef test_my_table():\n    rendered = MyTable.render(\n        kwargs={\n            \"title\": \"My table\",\n        },\n    )\n    assert rendered == \"&lt;table&gt;My table&lt;/table&gt;\"\n</code></pre>"},{"location":"overview/welcome/#handle-large-projects-with-ease","title":"Handle large projects with ease","text":"<ul> <li>Components can be infinitely nested.</li> <li>(Soon) Optimize performance with component-level caching</li> </ul>"},{"location":"overview/welcome/#debugging-features","title":"Debugging features","text":"<ul> <li>Visual component inspection: Highlight components and slots directly in your browser.</li> <li>Detailed tracing logs to supply AI-agents with context: The logs include component and slot names and IDs, and their position in the tree.</li> </ul>"},{"location":"overview/welcome/#sharing-components","title":"Sharing components","text":"<ul> <li>Install and use third-party components from PyPI</li> <li>Or publish your own \"component registry\"</li> <li> <p>Highly customizable - Choose how the components are called in the template (and more):</p> <pre><code>{% component \"calendar\" date=\"2024-11-06\" %}\n{% endcomponent %}\n\n{% calendar date=\"2024-11-06\" %}\n{% endcalendar %}\n</code></pre> </li> </ul>"},{"location":"overview/welcome/#other-features","title":"Other features","text":"<ul> <li>Vue-like provide / inject system</li> <li>Format HTML attributes with <code>{% html_attrs %}</code></li> </ul>"},{"location":"overview/welcome/#performance","title":"Performance","text":"<p>Our aim is to be at least as fast as Django templates.</p> <p>As of <code>0.130</code>, <code>django-components</code> is ~4x slower than Django templates.</p> Render time django 68.9\u00b10.6ms django-components 259\u00b14ms <p>See the full performance breakdown for more information.</p>"},{"location":"overview/welcome/#release-notes","title":"Release notes","text":"<p>Read the Release Notes to see the latest features and fixes.</p>"},{"location":"overview/welcome/#community-examples","title":"Community examples","text":"<p>One of our goals with <code>django-components</code> is to make it easy to share components between projects. Head over to the Community examples to see some examples.</p>"},{"location":"overview/welcome/#contributing-and-development","title":"Contributing and development","text":"<p>Get involved or sponsor this project - See here</p> <p>Running django-components locally for development - See here</p>"},{"location":"reference/api/","title":"API","text":""},{"location":"reference/api/#api","title":"API","text":""},{"location":"reference/api/#django_components.BaseNode","title":"BaseNode","text":"<pre><code>BaseNode(\n    params: List[TagAttr], flags: Optional[Dict[str, bool]] = None, nodelist: Optional[NodeList] = None, node_id: Optional[str] = None\n)\n</code></pre> <p>Bases: <code>django.template.base.Node</code></p> <p>See source code</p> <p>Node class for all django-components custom template tags.</p> <p>This class has a dual role:</p> <ol> <li> <p>It declares how a particular template tag should be parsed - By setting the    <code>tag</code>,    <code>end_tag</code>,    and <code>allowed_flags</code>    attributes:</p> <pre><code>class SlotNode(BaseNode):\n    tag = \"slot\"\n    end_tag = \"endslot\"\n    allowed_flags = [\"required\"]\n</code></pre> <p>This will allow the template tag <code>{% slot %}</code> to be used like this:</p> <pre><code>{% slot required %} ... {% endslot %}\n</code></pre> </li> <li> <p>The <code>render</code> method is     the actual implementation of the template tag.</p> <p>This is where the tag's logic is implemented:</p> <pre><code>class MyNode(BaseNode):\n    tag = \"mynode\"\n\n    def render(self, context: Context, name: str, **kwargs: Any) -&gt; str:\n        return f\"Hello, {name}!\"\n</code></pre> <p>This will allow the template tag <code>{% mynode %}</code> to be used like this:</p> <pre><code>{% mynode name=\"John\" %}\n</code></pre> </li> </ol> <p>The template tag accepts parameters as defined on the <code>render</code> method's signature.</p> <p>For more info, see <code>BaseNode.render()</code>.</p> <p>Methods:</p> <ul> <li> <code>parse</code>             \u2013              </li> <li> <code>register</code>             \u2013              </li> <li> <code>render</code>             \u2013              </li> <li> <code>unregister</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>active_flags</code>               (<code>List[str]</code>)           \u2013            </li> <li> <code>allowed_flags</code>               (<code>Optional[List[str]]</code>)           \u2013            </li> <li> <code>end_tag</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>flags</code>           \u2013            </li> <li> <code>node_id</code>           \u2013            </li> <li> <code>nodelist</code>           \u2013            </li> <li> <code>params</code>           \u2013            </li> <li> <code>tag</code>               (<code>str</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.BaseNode.active_flags","title":"active_flags  <code>property</code>","text":"<pre><code>active_flags: List[str]\n</code></pre> <p>See source code</p> <p>Flags that were set for this specific instance.</p>"},{"location":"reference/api/#django_components.BaseNode.allowed_flags","title":"allowed_flags  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>allowed_flags: Optional[List[str]] = None\n</code></pre> <p>See source code</p> <p>The allowed flags for this tag.</p> <p>E.g. <code>[\"required\"]</code> will allow this tag to be used like <code>{% slot required %}</code>.</p>"},{"location":"reference/api/#django_components.BaseNode.end_tag","title":"end_tag  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>end_tag: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The end tag name.</p> <p>E.g. <code>\"endcomponent\"</code> or <code>\"endslot\"</code> will make this class match template tags <code>{% endcomponent %}</code> or <code>{% endslot %}</code>.</p> <p>If not set, then this template tag has no end tag.</p> <p>So instead of <code>{% component %} ... {% endcomponent %}</code>, you'd use only <code>{% component %}</code>.</p>"},{"location":"reference/api/#django_components.BaseNode.flags","title":"flags  <code>instance-attribute</code>","text":"<pre><code>flags = flags or {flag: Falsefor flag in allowed_flags or []}\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.node_id","title":"node_id  <code>instance-attribute</code>","text":"<pre><code>node_id = node_id or gen_id()\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.nodelist","title":"nodelist  <code>instance-attribute</code>","text":"<pre><code>nodelist = nodelist or NodeList()\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.params","title":"params  <code>instance-attribute</code>","text":"<pre><code>params = params\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.tag","title":"tag  <code>instance-attribute</code>","text":"<pre><code>tag: str\n</code></pre> <p>See source code</p> <p>The tag name.</p> <p>E.g. <code>\"component\"</code> or <code>\"slot\"</code> will make this class match template tags <code>{% component %}</code> or <code>{% slot %}</code>.</p>"},{"location":"reference/api/#django_components.BaseNode.parse","title":"parse  <code>classmethod</code>","text":"<pre><code>parse(parser: Parser, token: Token, **kwargs: Any) -&gt; BaseNode\n</code></pre> <p>See source code</p> <p>This function is what is passed to Django's <code>Library.tag()</code> when registering the tag.</p> <p>In other words, this method is called by Django's template parser when we encounter a tag that matches this node's tag, e.g. <code>{% component %}</code> or <code>{% slot %}</code>.</p> <p>To register the tag, you can use <code>BaseNode.register()</code>.</p>"},{"location":"reference/api/#django_components.BaseNode.register","title":"register  <code>classmethod</code>","text":"<pre><code>register(library: Library) -&gt; None\n</code></pre> <p>See source code</p> <p>A convenience method for registering the tag with the given library.</p> <pre><code>class MyNode(BaseNode):\n    tag = \"mynode\"\n\nMyNode.register(library)\n</code></pre> <p>Allows you to then use the node in templates like so:</p> <pre><code>{% load mylibrary %}\n{% mynode %}\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.render","title":"render","text":"<pre><code>render(context: Context, *args: Any, **kwargs: Any) -&gt; str\n</code></pre> <p>See source code</p> <p>Render the node. This method is meant to be overridden by subclasses.</p> <p>The signature of this function decides what input the template tag accepts.</p> <p>The <code>render()</code> method MUST accept a <code>context</code> argument. Any arguments after that will be part of the tag's input parameters.</p> <p>So if you define a <code>render</code> method like this:</p> <pre><code>def render(self, context: Context, name: str, **kwargs: Any) -&gt; str:\n</code></pre> <p>Then the tag will require the <code>name</code> parameter, and accept any extra keyword arguments:</p> <pre><code>{% component name=\"John\" age=20 %}\n</code></pre>"},{"location":"reference/api/#django_components.BaseNode.unregister","title":"unregister  <code>classmethod</code>","text":"<pre><code>unregister(library: Library) -&gt; None\n</code></pre> <p>See source code</p> <p>Unregisters the node from the given library.</p>"},{"location":"reference/api/#django_components.CommandArg","title":"CommandArg  <code>dataclass</code>","text":"<pre><code>CommandArg(\n    name_or_flags: Union[str, Sequence[str]],\n    action: Optional[Union[CommandLiteralAction, Action]] = None,\n    nargs: Optional[Union[int, Literal[\"*\", \"+\", \"?\"]]] = None,\n    const: Any = None,\n    default: Any = None,\n    type: Optional[Union[Type, Callable[[str], Any]]] = None,\n    choices: Optional[Sequence[Any]] = None,\n    required: Optional[bool] = None,\n    help: Optional[str] = None,\n    metavar: Optional[str] = None,\n    dest: Optional[str] = None,\n    version: Optional[str] = None,\n    deprecated: Optional[bool] = None,\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Define a single positional argument or an option for a command.</p> <p>Fields on this class correspond to the arguments for <code>ArgumentParser.add_argument()</code></p> <p>Methods:</p> <ul> <li> <code>asdict</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>action</code>               (<code>Optional[Union[CommandLiteralAction, Action]]</code>)           \u2013            </li> <li> <code>choices</code>               (<code>Optional[Sequence[Any]]</code>)           \u2013            </li> <li> <code>const</code>               (<code>Any</code>)           \u2013            </li> <li> <code>default</code>               (<code>Any</code>)           \u2013            </li> <li> <code>deprecated</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>dest</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>help</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>metavar</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>name_or_flags</code>               (<code>Union[str, Sequence[str]]</code>)           \u2013            </li> <li> <code>nargs</code>               (<code>Optional[Union[int, Literal['*', '+', '?']]]</code>)           \u2013            </li> <li> <code>required</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>type</code>               (<code>Optional[Union[Type, Callable[[str], Any]]]</code>)           \u2013            </li> <li> <code>version</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.CommandArg.action","title":"action  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>action: Optional[Union[CommandLiteralAction, Action]] = None\n</code></pre> <p>See source code</p> <p>The basic type of action to be taken when this argument is encountered at the command line.</p>"},{"location":"reference/api/#django_components.CommandArg.choices","title":"choices  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>choices: Optional[Sequence[Any]] = None\n</code></pre> <p>See source code</p> <p>A sequence of the allowable values for the argument.</p>"},{"location":"reference/api/#django_components.CommandArg.const","title":"const  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>const: Any = None\n</code></pre> <p>See source code</p> <p>A constant value required by some action and nargs selections.</p>"},{"location":"reference/api/#django_components.CommandArg.default","title":"default  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>default: Any = None\n</code></pre> <p>See source code</p> <p>The value produced if the argument is absent from the command line and if it is absent from the namespace object.</p>"},{"location":"reference/api/#django_components.CommandArg.deprecated","title":"deprecated  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>deprecated: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Whether or not use of the argument is deprecated.</p> <p>NOTE: This is supported only in Python 3.13+</p>"},{"location":"reference/api/#django_components.CommandArg.dest","title":"dest  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>dest: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The name of the attribute to be added to the object returned by parse_args().</p>"},{"location":"reference/api/#django_components.CommandArg.help","title":"help  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>help: Optional[str] = None\n</code></pre> <p>See source code</p> <p>A brief description of what the argument does.</p>"},{"location":"reference/api/#django_components.CommandArg.metavar","title":"metavar  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>metavar: Optional[str] = None\n</code></pre> <p>See source code</p> <p>A name for the argument in usage messages.</p>"},{"location":"reference/api/#django_components.CommandArg.name_or_flags","title":"name_or_flags  <code>instance-attribute</code>","text":"<pre><code>name_or_flags: Union[str, Sequence[str]]\n</code></pre> <p>See source code</p> <p>Either a name or a list of option strings, e.g. 'foo' or '-f', '--foo'.</p>"},{"location":"reference/api/#django_components.CommandArg.nargs","title":"nargs  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>nargs: Optional[Union[int, Literal['*', '+', '?']]] = None\n</code></pre> <p>See source code</p> <p>The number of command-line arguments that should be consumed.</p>"},{"location":"reference/api/#django_components.CommandArg.required","title":"required  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>required: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Whether or not the command-line option may be omitted (optionals only).</p>"},{"location":"reference/api/#django_components.CommandArg.type","title":"type  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>type: Optional[Union[Type, Callable[[str], Any]]] = None\n</code></pre> <p>See source code</p> <p>The type to which the command-line argument should be converted.</p>"},{"location":"reference/api/#django_components.CommandArg.version","title":"version  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>version: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The version string to be added to the object returned by parse_args().</p> <p>MUST be used with <code>action='version'</code>.</p> <p>See https://docs.python.org/3/library/argparse.html#action</p>"},{"location":"reference/api/#django_components.CommandArg.asdict","title":"asdict","text":"<pre><code>asdict() -&gt; dict\n</code></pre> <p>See source code</p> <p>Convert the dataclass to a dictionary, stripping out fields with <code>None</code> values</p>"},{"location":"reference/api/#django_components.CommandArgGroup","title":"CommandArgGroup  <code>dataclass</code>","text":"<pre><code>CommandArgGroup(title: Optional[str] = None, description: Optional[str] = None, arguments: Sequence[CommandArg] = ())\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Define a group of arguments for a command.</p> <p>Fields on this class correspond to the arguments for <code>ArgumentParser.add_argument_group()</code></p> <p>Methods:</p> <ul> <li> <code>asdict</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>arguments</code>               (<code>Sequence[CommandArg]</code>)           \u2013            </li> <li> <code>description</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>title</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.CommandArgGroup.arguments","title":"arguments  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>arguments: Sequence[CommandArg] = ()\n</code></pre>"},{"location":"reference/api/#django_components.CommandArgGroup.description","title":"description  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>description: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Description for the argument group in help output, by default None</p>"},{"location":"reference/api/#django_components.CommandArgGroup.title","title":"title  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>title: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Title for the argument group in help output; by default \u201cpositional arguments\u201d if description is provided, otherwise uses title for positional arguments.</p>"},{"location":"reference/api/#django_components.CommandArgGroup.asdict","title":"asdict","text":"<pre><code>asdict() -&gt; dict\n</code></pre> <p>See source code</p> <p>Convert the dataclass to a dictionary, stripping out fields with <code>None</code> values</p>"},{"location":"reference/api/#django_components.CommandHandler","title":"CommandHandler","text":""},{"location":"reference/api/#django_components.CommandLiteralAction","title":"CommandLiteralAction  <code>module-attribute</code>","text":"<pre><code>CommandLiteralAction = Literal['append', 'append_const', 'count', 'extend', 'store', 'store_const', 'store_true', 'store_false', 'version']\n</code></pre> <p>See source code</p> <p>The basic type of action to be taken when this argument is encountered at the command line.</p> <p>This is a subset of the values for <code>action</code> in <code>ArgumentParser.add_argument()</code>.</p>"},{"location":"reference/api/#django_components.CommandParserInput","title":"CommandParserInput  <code>dataclass</code>","text":"<pre><code>CommandParserInput(\n    prog: Optional[str] = None,\n    usage: Optional[str] = None,\n    description: Optional[str] = None,\n    epilog: Optional[str] = None,\n    parents: Optional[Sequence[ArgumentParser]] = None,\n    formatter_class: Optional[Type[_FormatterClass]] = None,\n    prefix_chars: Optional[str] = None,\n    fromfile_prefix_chars: Optional[str] = None,\n    argument_default: Optional[Any] = None,\n    conflict_handler: Optional[str] = None,\n    add_help: Optional[bool] = None,\n    allow_abbrev: Optional[bool] = None,\n    exit_on_error: Optional[bool] = None,\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Typing for the input to the <code>ArgumentParser</code> constructor.</p> <p>Methods:</p> <ul> <li> <code>asdict</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>add_help</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>allow_abbrev</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>argument_default</code>               (<code>Optional[Any]</code>)           \u2013            </li> <li> <code>conflict_handler</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>description</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>epilog</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>exit_on_error</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>formatter_class</code>               (<code>Optional[Type[_FormatterClass]]</code>)           \u2013            </li> <li> <code>fromfile_prefix_chars</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>parents</code>               (<code>Optional[Sequence[ArgumentParser]]</code>)           \u2013            </li> <li> <code>prefix_chars</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>prog</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>usage</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.CommandParserInput.add_help","title":"add_help  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>add_help: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Add a -h/--help option to the parser (default: <code>True</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.allow_abbrev","title":"allow_abbrev  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>allow_abbrev: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Allows long options to be abbreviated if the abbreviation is unambiguous. (default: <code>True</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.argument_default","title":"argument_default  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>argument_default: Optional[Any] = None\n</code></pre> <p>See source code</p> <p>The global default value for arguments (default: <code>None</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.conflict_handler","title":"conflict_handler  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>conflict_handler: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The strategy for resolving conflicting optionals (usually unnecessary)</p>"},{"location":"reference/api/#django_components.CommandParserInput.description","title":"description  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>description: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Text to display before the argument help (by default, no text)</p>"},{"location":"reference/api/#django_components.CommandParserInput.epilog","title":"epilog  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>epilog: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Text to display after the argument help (by default, no text)</p>"},{"location":"reference/api/#django_components.CommandParserInput.exit_on_error","title":"exit_on_error  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>exit_on_error: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Determines whether or not ArgumentParser exits with error info when an error occurs. (default: <code>True</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.formatter_class","title":"formatter_class  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>formatter_class: Optional[Type[_FormatterClass]] = None\n</code></pre> <p>See source code</p> <p>A class for customizing the help output</p>"},{"location":"reference/api/#django_components.CommandParserInput.fromfile_prefix_chars","title":"fromfile_prefix_chars  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>fromfile_prefix_chars: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The set of characters that prefix files from which additional arguments should be read (default: <code>None</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.parents","title":"parents  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>parents: Optional[Sequence[ArgumentParser]] = None\n</code></pre> <p>See source code</p> <p>A list of ArgumentParser objects whose arguments should also be included</p>"},{"location":"reference/api/#django_components.CommandParserInput.prefix_chars","title":"prefix_chars  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>prefix_chars: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The set of characters that prefix optional arguments (default: \u2018-\u2018)</p>"},{"location":"reference/api/#django_components.CommandParserInput.prog","title":"prog  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>prog: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The name of the program (default: <code>os.path.basename(sys.argv[0])</code>)</p>"},{"location":"reference/api/#django_components.CommandParserInput.usage","title":"usage  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>usage: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The string describing the program usage (default: generated from arguments added to parser)</p>"},{"location":"reference/api/#django_components.CommandParserInput.asdict","title":"asdict","text":"<pre><code>asdict() -&gt; dict\n</code></pre> <p>See source code</p> <p>Convert the dataclass to a dictionary, stripping out fields with <code>None</code> values</p>"},{"location":"reference/api/#django_components.CommandSubcommand","title":"CommandSubcommand  <code>dataclass</code>","text":"<pre><code>CommandSubcommand(\n    title: Optional[str] = None,\n    description: Optional[str] = None,\n    prog: Optional[str] = None,\n    parser_class: Optional[Type[ArgumentParser]] = None,\n    action: Optional[Union[CommandLiteralAction, Action]] = None,\n    dest: Optional[str] = None,\n    required: Optional[bool] = None,\n    help: Optional[str] = None,\n    metavar: Optional[str] = None,\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Define a subcommand for a command.</p> <p>Fields on this class correspond to the arguments for <code>ArgumentParser.add_subparsers.add_parser()</code></p> <p>Methods:</p> <ul> <li> <code>asdict</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>action</code>               (<code>Optional[Union[CommandLiteralAction, Action]]</code>)           \u2013            </li> <li> <code>description</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>dest</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>help</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>metavar</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>parser_class</code>               (<code>Optional[Type[ArgumentParser]]</code>)           \u2013            </li> <li> <code>prog</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>required</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>title</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.CommandSubcommand.action","title":"action  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>action: Optional[Union[CommandLiteralAction, Action]] = None\n</code></pre> <p>See source code</p> <p>The basic type of action to be taken when this argument is encountered at the command line.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.description","title":"description  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>description: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Description for the sub-parser group in help output, by default <code>None</code>.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.dest","title":"dest  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>dest: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the attribute under which sub-command name will be stored; by default <code>None</code> and no value is stored.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.help","title":"help  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>help: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Help for sub-parser group in help output, by default <code>None</code>.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.metavar","title":"metavar  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>metavar: Optional[str] = None\n</code></pre> <p>See source code</p> <p>String presenting available subcommands in help; by default it is None and presents subcommands in form <code>{cmd1, cmd2, ..}</code>.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.parser_class","title":"parser_class  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>parser_class: Optional[Type[ArgumentParser]] = None\n</code></pre> <p>See source code</p> <p>Class which will be used to create sub-parser instances, by default the class of the current parser (e.g. <code>ArgumentParser</code>).</p>"},{"location":"reference/api/#django_components.CommandSubcommand.prog","title":"prog  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>prog: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Usage information that will be displayed with sub-command help, by default the name of the program and any positional arguments before the subparser argument.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.required","title":"required  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>required: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Whether or not a subcommand must be provided, by default <code>False</code> (added in 3.7)</p>"},{"location":"reference/api/#django_components.CommandSubcommand.title","title":"title  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>title: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Title for the sub-parser group in help output; by default \u201csubcommands\u201d if description is provided, otherwise uses title for positional arguments.</p>"},{"location":"reference/api/#django_components.CommandSubcommand.asdict","title":"asdict","text":"<pre><code>asdict() -&gt; dict\n</code></pre> <p>See source code</p> <p>Convert the dataclass to a dictionary, stripping out fields with <code>None</code> values</p>"},{"location":"reference/api/#django_components.Component","title":"Component","text":"<pre><code>Component(registered_name: Optional[str] = None, outer_context: Optional[Context] = None, registry: Optional[ComponentRegistry] = None)\n</code></pre> <p>Methods:</p> <ul> <li> <code>as_view</code>             \u2013              </li> <li> <code>get_context_data</code>             \u2013              </li> <li> <code>get_template</code>             \u2013              </li> <li> <code>get_template_name</code>             \u2013              </li> <li> <code>inject</code>             \u2013              </li> <li> <code>on_render_after</code>             \u2013              </li> <li> <code>on_render_before</code>             \u2013              </li> <li> <code>render</code>             \u2013              </li> <li> <code>render_to_response</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>Media</code>               (<code>Optional[Type[ComponentMediaInput]]</code>)           \u2013            </li> <li> <code>context_processors_data</code>               (<code>Dict</code>)           \u2013            </li> <li> <code>css</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>css_file</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>id</code>               (<code>str</code>)           \u2013            </li> <li> <code>input</code>               (<code>RenderInput[ArgsType, KwargsType, SlotsType]</code>)           \u2013            </li> <li> <code>is_filled</code>               (<code>SlotIsFilled</code>)           \u2013            </li> <li> <code>js</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>js_file</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>media</code>               (<code>Optional[Media]</code>)           \u2013            </li> <li> <code>media_class</code>               (<code>Type[Media]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>outer_context</code>               (<code>Optional[Context]</code>)           \u2013            </li> <li> <code>registered_name</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>registry</code>           \u2013            </li> <li> <code>request</code>               (<code>Optional[HttpRequest]</code>)           \u2013            </li> <li> <code>response_class</code>           \u2013            </li> <li> <code>template</code>               (<code>Optional[Union[str, Template]]</code>)           \u2013            </li> <li> <code>template_file</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>template_name</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.Component.Media","title":"Media  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>Media: Optional[Type[ComponentMediaInput]] = None\n</code></pre> <p>See source code</p> <p>Defines JS and CSS media files associated with this component.</p> <p>This <code>Media</code> class behaves similarly to Django's Media class:</p> <ul> <li>Paths are generally handled as static file paths, and resolved URLs are rendered to HTML with   <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A path that starts with <code>http</code>, <code>https</code>, or <code>/</code> is considered a URL, skipping the static file resolution.   This path is still rendered to HTML with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>A <code>SafeString</code> (with <code>__html__</code> method) is considered an already-formatted HTML tag, skipping both static file     resolution and rendering with <code>media_class.render_js()</code> or <code>media_class.render_css()</code>.</li> <li>You can set <code>extend</code> to configure   whether to inherit JS / CSS from parent components. See   Controlling Media Inheritance.</li> </ul> <p>However, there's a few differences from Django's Media class:</p> <ol> <li>Our Media class accepts various formats for the JS and CSS files: either a single file, a list,    or (CSS-only) a dictionary (See <code>ComponentMediaInput</code>).</li> <li>Individual JS / CSS files can be any of <code>str</code>, <code>bytes</code>, <code>Path</code>,    <code>SafeString</code>, or a function    (See <code>ComponentMediaInputPath</code>).</li> </ol> <p>Example:</p> <pre><code>class MyTable(Component):\n    class Media:\n        js = [\n            \"path/to/script.js\",\n            \"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\",  # AlpineJS\n        ]\n        css = {\n            \"all\": [\n                \"path/to/style.css\",\n                \"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\",  # TailwindCSS\n            ],\n            \"print\": [\"path/to/style2.css\"],\n        }\n</code></pre>"},{"location":"reference/api/#django_components.Component.context_processors_data","title":"context_processors_data  <code>property</code>","text":"<pre><code>context_processors_data: Dict\n</code></pre> <p>See source code</p> <p>Retrieve data injected by <code>context_processors</code>.</p> <p>This data is also available from within the component's template, without having to return this data from <code>get_context_data()</code>.</p> <p>Unlike regular Django templates, the context processors are applied to components either when:</p> <ul> <li>The component is rendered with <code>RequestContext</code> (Regular Django behavior)</li> <li>The component is rendered with a regular <code>Context</code> (or none), but the <code>request</code> kwarg   of <code>Component.render()</code> is set.</li> <li>The component is nested in another component that matches one of the two conditions above.</li> </ul> <p>See <code>Component.request</code> on how the <code>request</code> (HTTPRequest) object is passed to and within the components.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        user = self.context_processors_data['user']\n        return {\n            'is_logged_in': user.is_authenticated,\n        }\n</code></pre>"},{"location":"reference/api/#django_components.Component.css","title":"css  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>css: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Main CSS associated with this component inlined as string.</p> <p>Only one of <code>css</code> or <code>css_file</code> must be defined.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    css = \"\"\"\n    .my-class {\n        color: red;\n    }\n    \"\"\"\n</code></pre>"},{"location":"reference/api/#django_components.Component.css_file","title":"css_file  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>css_file: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Main CSS associated with this component as file path.</p> <p>The filepath must be either:</p> <ul> <li>Relative to the directory where the Component's Python file is defined.</li> <li>Relative to one of the component directories, as set by   <code>COMPONENTS.dirs</code>   or   <code>COMPONENTS.app_dirs</code>   (e.g. <code>&lt;root&gt;/components/</code>).</li> <li>Relative to the staticfiles directories, as set by Django's <code>STATICFILES_DIRS</code> setting (e.g. <code>&lt;root&gt;/static/</code>).</li> </ul> <p>When you create a Component class with <code>css_file</code>, these will happen:</p> <ol> <li>If the file path is relative to the directory where the component's Python file is,    the path is resolved.</li> <li>The file is read and its contents is set to <code>Component.css</code>.</li> </ol> <p>Only one of <code>css</code> or <code>css_file</code> must be defined.</p> <p>Example:</p> path/to/style.css<pre><code>.my-class {\n    color: red;\n}\n</code></pre> path/to/component.py<pre><code>class MyComponent(Component):\n    css_file = \"path/to/style.css\"\n\nprint(MyComponent.css)\n# Output:\n# .my-class {\n#     color: red;\n# };\n</code></pre>"},{"location":"reference/api/#django_components.Component.id","title":"id  <code>property</code>","text":"<pre><code>id: str\n</code></pre> <p>See source code</p> <p>This ID is unique for every time a <code>Component.render()</code> (or equivalent) is called (AKA \"render ID\").</p> <p>This is useful for logging or debugging.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p> <p>A single render ID has a chance of collision 1 in 3.3M. However, due to birthday paradox, the chance of collision increases when approaching ~1,000 render IDs.</p> <p>Thus, there is a soft-cap of 1,000 components rendered on a single page.</p> <p>If you need to more than that, please open an issue on GitHub.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        print(f\"Rendering '{self.id}'\")\n        return {}\n\nMyComponent.render()\n# Rendering 'ab3c4d'\n</code></pre>"},{"location":"reference/api/#django_components.Component.input","title":"input  <code>property</code>","text":"<pre><code>input: RenderInput[ArgsType, KwargsType, SlotsType]\n</code></pre> <p>See source code</p> <p>Input holds the data (like arg, kwargs, slots) that were passed to the current execution of the <code>render</code> method.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p>"},{"location":"reference/api/#django_components.Component.is_filled","title":"is_filled  <code>property</code>","text":"<pre><code>is_filled: SlotIsFilled\n</code></pre> <p>See source code</p> <p>Dictionary describing which slots have or have not been filled.</p> <p>This attribute is available for use only within the template as <code>{{ component_vars.is_filled.slot_name }}</code>, and within <code>on_render_before</code> and <code>on_render_after</code> hooks.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p>"},{"location":"reference/api/#django_components.Component.js","title":"js  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>js: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Main JS associated with this component inlined as string.</p> <p>Only one of <code>js</code> or <code>js_file</code> must be defined.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    js = \"console.log('Hello, World!');\"\n</code></pre>"},{"location":"reference/api/#django_components.Component.js_file","title":"js_file  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>js_file: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Main JS associated with this component as file path.</p> <p>The filepath must be either:</p> <ul> <li>Relative to the directory where the Component's Python file is defined.</li> <li>Relative to one of the component directories, as set by   <code>COMPONENTS.dirs</code>   or   <code>COMPONENTS.app_dirs</code>   (e.g. <code>&lt;root&gt;/components/</code>).</li> <li>Relative to the staticfiles directories, as set by Django's <code>STATICFILES_DIRS</code> setting (e.g. <code>&lt;root&gt;/static/</code>).</li> </ul> <p>When you create a Component class with <code>js_file</code>, these will happen:</p> <ol> <li>If the file path is relative to the directory where the component's Python file is,    the path is resolved.</li> <li>The file is read and its contents is set to <code>Component.js</code>.</li> </ol> <p>Only one of <code>js</code> or <code>js_file</code> must be defined.</p> <p>Example:</p> path/to/script.js<pre><code>console.log('Hello, World!');\n</code></pre> path/to/component.py<pre><code>class MyComponent(Component):\n    js_file = \"path/to/script.js\"\n\nprint(MyComponent.js)\n# Output: console.log('Hello, World!');\n</code></pre>"},{"location":"reference/api/#django_components.Component.media","title":"media  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>media: Optional[Media] = None\n</code></pre> <p>See source code</p> <p>Normalized definition of JS and CSS media files associated with this component. <code>None</code> if <code>Component.Media</code> is not defined.</p> <p>This field is generated from <code>Component.media_class</code>.</p> <p>Read more on Accessing component's HTML / JS / CSS.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    class Media:\n        js = \"path/to/script.js\"\n        css = \"path/to/style.css\"\n\nprint(MyComponent.media)\n# Output:\n# &lt;script src=\"/static/path/to/script.js\"&gt;&lt;/script&gt;\n# &lt;link href=\"/static/path/to/style.css\" media=\"all\" rel=\"stylesheet\"&gt;\n</code></pre>"},{"location":"reference/api/#django_components.Component.media_class","title":"media_class  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>media_class: Type[Media] = Media\n</code></pre> <p>See source code</p> <p>Set the Media class that will be instantiated with the JS and CSS media files from <code>Component.Media</code>.</p> <p>This is useful when you want to customize the behavior of the media files, like customizing how the JS or CSS files are rendered into <code>&lt;script&gt;</code> or <code>&lt;link&gt;</code> HTML tags. Read more in Defining HTML / JS / CSS files.</p> <p>Example:</p> <pre><code>class MyTable(Component):\n    class Media:\n        js = \"path/to/script.js\"\n        css = \"path/to/style.css\"\n\n    media_class = MyMediaClass\n</code></pre>"},{"location":"reference/api/#django_components.Component.name","title":"name  <code>property</code>","text":"<pre><code>name: str\n</code></pre>"},{"location":"reference/api/#django_components.Component.outer_context","title":"outer_context  <code>instance-attribute</code>","text":"<pre><code>outer_context: Optional[Context] = outer_context\n</code></pre>"},{"location":"reference/api/#django_components.Component.registered_name","title":"registered_name  <code>instance-attribute</code>","text":"<pre><code>registered_name: Optional[str] = registered_name\n</code></pre>"},{"location":"reference/api/#django_components.Component.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry = registry or registry\n</code></pre>"},{"location":"reference/api/#django_components.Component.request","title":"request  <code>property</code>","text":"<pre><code>request: Optional[HttpRequest]\n</code></pre> <p>See source code</p> <p>HTTPRequest object passed to this component.</p> <p>In regular Django templates, you have to use <code>RequestContext</code> to pass the <code>HttpRequest</code> object to the template.</p> <p>But in Components, you can either use <code>RequestContext</code>, or pass the <code>request</code> object explicitly via <code>Component.render()</code> and <code>Component.render_to_response()</code>.</p> <p>When a component is nested in another, the child component uses parent's <code>request</code> object.</p> <p>Raises <code>RuntimeError</code> if accessed outside of rendering execution.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    def get_context_data(self):\n        user_id = self.request.GET['user_id']\n        return {\n            'user_id': user_id,\n        }\n</code></pre>"},{"location":"reference/api/#django_components.Component.response_class","title":"response_class  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>response_class = HttpResponse\n</code></pre> <p>See source code</p> <p>This allows to configure what class is used to generate response from <code>render_to_response</code></p>"},{"location":"reference/api/#django_components.Component.template","title":"template  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>template: Optional[Union[str, Template]] = None\n</code></pre> <p>See source code</p> <p>Inlined Django template associated with this component. Can be a plain string or a Template instance.</p> <p>Only one of <code>template_file</code>, <code>get_template_name</code>, <code>template</code> or <code>get_template</code> must be defined.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    template = \"Hello, {{ name }}!\"\n\n    def get_context_data(self):\n        return {\"name\": \"World\"}\n</code></pre>"},{"location":"reference/api/#django_components.Component.template_file","title":"template_file  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>template_file: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Filepath to the Django template associated with this component.</p> <p>The filepath must be either:</p> <ul> <li>Relative to the directory where the Component's Python file is defined.</li> <li>Relative to one of the component directories, as set by   <code>COMPONENTS.dirs</code>   or   <code>COMPONENTS.app_dirs</code>   (e.g. <code>&lt;root&gt;/components/</code>).</li> <li>Relative to the template directories, as set by Django's <code>TEMPLATES</code> setting (e.g. <code>&lt;root&gt;/templates/</code>).</li> </ul> <p>Only one of <code>template_file</code>, <code>get_template_name</code>, <code>template</code> or <code>get_template</code> must be defined.</p> <p>Example:</p> <pre><code>class MyComponent(Component):\n    template_file = \"path/to/template.html\"\n\n    def get_context_data(self):\n        return {\"name\": \"World\"}\n</code></pre>"},{"location":"reference/api/#django_components.Component.template_name","title":"template_name  <code>instance-attribute</code>","text":"<pre><code>template_name: Optional[str]\n</code></pre> <p>See source code</p> <p>Alias for <code>template_file</code>.</p> <p>For historical reasons, django-components used <code>template_name</code> to align with Django's TemplateView.</p> <p><code>template_file</code> was introduced to align with <code>js/js_file</code> and <code>css/css_file</code>.</p> <p>Setting and accessing this attribute is proxied to <code>template_file</code>.</p>"},{"location":"reference/api/#django_components.Component.as_view","title":"as_view  <code>classmethod</code>","text":"<pre><code>as_view(**initkwargs: Any) -&gt; ViewFn\n</code></pre> <p>See source code</p> <p>Shortcut for calling <code>Component.View.as_view</code> and passing component instance to it.</p>"},{"location":"reference/api/#django_components.Component.get_context_data","title":"get_context_data","text":"<pre><code>get_context_data(*args: Any, **kwargs: Any) -&gt; DataType\n</code></pre>"},{"location":"reference/api/#django_components.Component.get_template","title":"get_template","text":"<pre><code>get_template(context: Context) -&gt; Optional[Union[str, Template]]\n</code></pre> <p>See source code</p> <p>Inlined Django template associated with this component. Can be a plain string or a Template instance.</p> <p>Only one of <code>template_file</code>, <code>get_template_name</code>, <code>template</code> or <code>get_template</code> must be defined.</p>"},{"location":"reference/api/#django_components.Component.get_template_name","title":"get_template_name","text":"<pre><code>get_template_name(context: Context) -&gt; Optional[str]\n</code></pre> <p>See source code</p> <p>Filepath to the Django template associated with this component.</p> <p>The filepath must be relative to either the file where the component class was defined, or one of the roots of <code>STATIFILES_DIRS</code>.</p> <p>Only one of <code>template_file</code>, <code>get_template_name</code>, <code>template</code> or <code>get_template</code> must be defined.</p>"},{"location":"reference/api/#django_components.Component.inject","title":"inject","text":"<pre><code>inject(key: str, default: Optional[Any] = None) -&gt; Any\n</code></pre> <p>See source code</p> <p>Use this method to retrieve the data that was passed to a <code>{% provide %}</code> tag with the corresponding key.</p> <p>To retrieve the data, <code>inject()</code> must be called inside a component that's inside the <code>{% provide %}</code> tag.</p> <p>You may also pass a default that will be used if the <code>provide</code> tag with given key was NOT found.</p> <p>This method mut be used inside the <code>get_context_data()</code> method and raises an error if called elsewhere.</p> <p>Example:</p> <p>Given this template: <pre><code>{% provide \"provider\" hello=\"world\" %}\n    {% component \"my_comp\" %}\n    {% endcomponent %}\n{% endprovide %}\n</code></pre></p> <p>And given this definition of \"my_comp\" component: <pre><code>from django_components import Component, register\n\n@register(\"my_comp\")\nclass MyComp(Component):\n    template = \"hi {{ data.hello }}!\"\n    def get_context_data(self):\n        data = self.inject(\"provider\")\n        return {\"data\": data}\n</code></pre></p> <p>This renders into: <pre><code>hi world!\n</code></pre></p> <p>As the <code>{{ data.hello }}</code> is taken from the \"provider\".</p>"},{"location":"reference/api/#django_components.Component.on_render_after","title":"on_render_after","text":"<pre><code>on_render_after(context: Context, template: Template, content: str) -&gt; Optional[SlotResult]\n</code></pre> <p>See source code</p> <p>Hook that runs just after the component's template was rendered. It receives the rendered output as the last argument.</p> <p>You can use this hook to access the context or the template, but modifying them won't have any effect.</p> <p>To override the content that gets rendered, you can return a string or SafeString from this hook.</p>"},{"location":"reference/api/#django_components.Component.on_render_before","title":"on_render_before","text":"<pre><code>on_render_before(context: Context, template: Template) -&gt; None\n</code></pre> <p>See source code</p> <p>Hook that runs just before the component's template is rendered.</p> <p>You can use this hook to access or modify the context or the template.</p>"},{"location":"reference/api/#django_components.Component.render","title":"render  <code>classmethod</code>","text":"<pre><code>render(\n    context: Optional[Union[Dict[str, Any], Context]] = None,\n    args: Optional[ArgsType] = None,\n    kwargs: Optional[KwargsType] = None,\n    slots: Optional[SlotsType] = None,\n    escape_slots_content: bool = True,\n    type: RenderType = \"document\",\n    render_dependencies: bool = True,\n    request: Optional[HttpRequest] = None,\n) -&gt; str\n</code></pre> <p>See source code</p> <p>Render the component into a string.</p> <p>Inputs: - <code>args</code> - Positional args for the component. This is the same as calling the component   as <code>{% component \"my_comp\" arg1 arg2 ... %}</code> - <code>kwargs</code> - Kwargs for the component. This is the same as calling the component   as <code>{% component \"my_comp\" key1=val1 key2=val2 ... %}</code> - <code>slots</code> - Component slot fills. This is the same as pasing <code>{% fill %}</code> tags to the component.     Accepts a dictionary of <code>{ slot_name: slot_content }</code> where <code>slot_content</code> can be a string     or render function. - <code>escape_slots_content</code> - Whether the content from <code>slots</code> should be escaped. - <code>context</code> - A context (dictionary or Django's Context) within which the component   is rendered. The keys on the context can be accessed from within the template.     - NOTE: In \"isolated\" mode, context is NOT accessible, and data MUST be passed via       component's args and kwargs. - <code>type</code> - Configure how to handle JS and CSS dependencies.     - <code>\"document\"</code> (default) - JS dependencies are inserted into <code>{% component_js_dependencies %}</code>,       or to the end of the <code>&lt;body&gt;</code> tag. CSS dependencies are inserted into       <code>{% component_css_dependencies %}</code>, or the end of the <code>&lt;head&gt;</code> tag. - <code>render_dependencies</code> - Set this to <code>False</code> if you want to insert the resulting HTML into another component. - <code>request</code> - The request object. This is only required when needing to use RequestContext,               e.g. to enable template <code>context_processors</code>. Example: <pre><code>MyComponent.render(\n    args=[1, \"two\", {}],\n    kwargs={\n        \"key\": 123,\n    },\n    slots={\n        \"header\": 'STATIC TEXT HERE',\n        \"footer\": lambda ctx, slot_kwargs, slot_ref: f'CTX: {ctx['hello']} SLOT_DATA: {slot_kwargs['abc']}',\n    },\n    escape_slots_content=False,\n)\n</code></pre></p>"},{"location":"reference/api/#django_components.Component.render_to_response","title":"render_to_response  <code>classmethod</code>","text":"<pre><code>render_to_response(\n    context: Optional[Union[Dict[str, Any], Context]] = None,\n    slots: Optional[SlotsType] = None,\n    escape_slots_content: bool = True,\n    args: Optional[ArgsType] = None,\n    kwargs: Optional[KwargsType] = None,\n    type: RenderType = \"document\",\n    request: Optional[HttpRequest] = None,\n    *response_args: Any,\n    **response_kwargs: Any\n) -&gt; HttpResponse\n</code></pre> <p>See source code</p> <p>Render the component and wrap the content in the response class.</p> <p>The response class is taken from <code>Component.response_class</code>. Defaults to <code>django.http.HttpResponse</code>.</p> <p>This is the interface for the <code>django.views.View</code> class which allows us to use components as Django views with <code>component.as_view()</code>.</p> <p>Inputs: - <code>args</code> - Positional args for the component. This is the same as calling the component   as <code>{% component \"my_comp\" arg1 arg2 ... %}</code> - <code>kwargs</code> - Kwargs for the component. This is the same as calling the component   as <code>{% component \"my_comp\" key1=val1 key2=val2 ... %}</code> - <code>slots</code> - Component slot fills. This is the same as pasing <code>{% fill %}</code> tags to the component.     Accepts a dictionary of <code>{ slot_name: slot_content }</code> where <code>slot_content</code> can be a string     or render function. - <code>escape_slots_content</code> - Whether the content from <code>slots</code> should be escaped. - <code>context</code> - A context (dictionary or Django's Context) within which the component   is rendered. The keys on the context can be accessed from within the template.     - NOTE: In \"isolated\" mode, context is NOT accessible, and data MUST be passed via       component's args and kwargs. - <code>type</code> - Configure how to handle JS and CSS dependencies.     - <code>\"document\"</code> (default) - JS dependencies are inserted into <code>{% component_js_dependencies %}</code>,       or to the end of the <code>&lt;body&gt;</code> tag. CSS dependencies are inserted into       <code>{% component_css_dependencies %}</code>, or the end of the <code>&lt;head&gt;</code> tag. - <code>request</code> - The request object. This is only required when needing to use RequestContext,               e.g. to enable template <code>context_processors</code>.</p> <p>Any additional args and kwargs are passed to the <code>response_class</code>.</p> <p>Example: <pre><code>MyComponent.render_to_response(\n    args=[1, \"two\", {}],\n    kwargs={\n        \"key\": 123,\n    },\n    slots={\n        \"header\": 'STATIC TEXT HERE',\n        \"footer\": lambda ctx, slot_kwargs, slot_ref: f'CTX: {ctx['hello']} SLOT_DATA: {slot_kwargs['abc']}',\n    },\n    escape_slots_content=False,\n    # HttpResponse input\n    status=201,\n    headers={...},\n)\n# HttpResponse(content=..., status=201, headers=...)\n</code></pre></p>"},{"location":"reference/api/#django_components.ComponentCommand","title":"ComponentCommand","text":"<p>Bases: <code>object</code></p> <p>See source code</p> <p>Definition of a CLI command.</p> <p>This class is based on Python's <code>argparse</code> module and Django's <code>BaseCommand</code> class. <code>ComponentCommand</code> allows you to define:</p> <ul> <li>Command name, description, and help text</li> <li>Arguments and options (e.g. <code>--name John</code>)</li> <li>Group arguments (see argparse groups)</li> <li>Subcommands (e.g. <code>components ext run my_ext hello</code>)</li> <li>Handler behavior</li> </ul> <p>Each extension can add its own commands, which will be available to run with <code>components ext run</code>.</p> <p>Extensions use the <code>ComponentCommand</code> class to define their commands.</p> <p>For example, if you define and install the following extension:</p> <pre><code>from django_components ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n    def handle(self, *args, **kwargs):\n        print(\"Hello, world!\")\n\nclass MyExt(ComponentExtension):\n    name = \"my_ext\"\n    commands = [HelloCommand]\n</code></pre> <p>You can run the <code>hello</code> command with:</p> <pre><code>python manage.py components ext run my_ext hello\n</code></pre> <p>You can also define arguments for the command, which will be passed to the command's <code>handle</code> method.</p> <pre><code>from django_components import CommandArg, ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n    arguments = [\n        CommandArg(name=\"name\", help=\"The name to say hello to\"),\n        CommandArg(name=[\"--shout\", \"-s\"], action=\"store_true\"),\n    ]\n\n    def handle(self, name: str, *args, **kwargs):\n        shout = kwargs.get(\"shout\", False)\n        msg = f\"Hello, {name}!\"\n        if shout:\n            msg = msg.upper()\n        print(msg)\n</code></pre> <p>You can run the command with:</p> <pre><code>python manage.py components ext run my_ext hello --name John --shout\n</code></pre> <p>Note</p> <p>Command arguments and options are based on Python's <code>argparse</code> module.</p> <p>For more information, see the argparse documentation.</p> <p>Attributes:</p> <ul> <li> <code>arguments</code>               (<code>Sequence[Union[CommandArg, CommandArgGroup]]</code>)           \u2013            </li> <li> <code>handle</code>               (<code>Optional[CommandHandler]</code>)           \u2013            </li> <li> <code>help</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>parser_input</code>               (<code>Optional[CommandParserInput]</code>)           \u2013            </li> <li> <code>subcommands</code>               (<code>Sequence[Type[ComponentCommand]]</code>)           \u2013            </li> <li> <code>subparser_input</code>               (<code>Optional[CommandSubcommand]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentCommand.arguments","title":"arguments  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>arguments: Sequence[Union[CommandArg, CommandArgGroup]] = ()\n</code></pre> <p>See source code</p> <p>argparse arguments for the command</p>"},{"location":"reference/api/#django_components.ComponentCommand.handle","title":"handle  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>handle: Optional[CommandHandler] = None\n</code></pre> <p>See source code</p> <p>The function that is called when the command is run. If <code>None</code>, the command will print the help message.</p>"},{"location":"reference/api/#django_components.ComponentCommand.help","title":"help  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>help: Optional[str] = None\n</code></pre> <p>See source code</p> <p>The help text for the command</p>"},{"location":"reference/api/#django_components.ComponentCommand.name","title":"name  <code>instance-attribute</code>","text":"<pre><code>name: str\n</code></pre> <p>See source code</p> <p>The name of the command - this is what is used to call the command</p>"},{"location":"reference/api/#django_components.ComponentCommand.parser_input","title":"parser_input  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>parser_input: Optional[CommandParserInput] = None\n</code></pre> <p>See source code</p> <p>The input to use when creating the <code>ArgumentParser</code> for this command. If <code>None</code>, the default values will be used.</p>"},{"location":"reference/api/#django_components.ComponentCommand.subcommands","title":"subcommands  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>subcommands: Sequence[Type[ComponentCommand]] = ()\n</code></pre> <p>See source code</p> <p>Subcommands for the command</p>"},{"location":"reference/api/#django_components.ComponentCommand.subparser_input","title":"subparser_input  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>subparser_input: Optional[CommandSubcommand] = None\n</code></pre> <p>See source code</p> <p>The input to use when this command is a subcommand installed with <code>add_subparser()</code>. If <code>None</code>, the default values will be used.</p>"},{"location":"reference/api/#django_components.ComponentExtension","title":"ComponentExtension","text":"<p>Bases: <code>object</code></p> <p>See source code</p> <p>Base class for all extensions.</p> <p>Read more on Extensions.</p> <p>Methods:</p> <ul> <li> <code>on_component_class_created</code>             \u2013              </li> <li> <code>on_component_class_deleted</code>             \u2013              </li> <li> <code>on_component_data</code>             \u2013              </li> <li> <code>on_component_input</code>             \u2013              </li> <li> <code>on_component_registered</code>             \u2013              </li> <li> <code>on_component_unregistered</code>             \u2013              </li> <li> <code>on_registry_created</code>             \u2013              </li> <li> <code>on_registry_deleted</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>ExtensionClass</code>           \u2013            </li> <li> <code>class_name</code>               (<code>str</code>)           \u2013            </li> <li> <code>commands</code>               (<code>List[Type[ComponentCommand]]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>urls</code>               (<code>List[URLRoute]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentExtension.ExtensionClass","title":"ExtensionClass  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>ExtensionClass = BaseExtensionClass\n</code></pre> <p>See source code</p> <p>Base class that the \"extension class\" nested within a <code>Component</code> class will inherit from.</p> <p>This is where you can define new methods and attributes that will be available to the component instance.</p> <p>Background:</p> <p>The extension may add new features to the <code>Component</code> class by allowing users to define and access a nested class in the <code>Component</code> class. E.g.:</p> <pre><code>class MyComp(Component):\n    class MyExtension:\n        ...\n\n    def get_context_data(self):\n        return {\n            \"my_extension\": self.my_extension.do_something(),\n        }\n</code></pre> <p>When rendering a component, the nested extension class will be set as a subclass of <code>ExtensionClass</code>. So it will be same as if the user had directly inherited from <code>ExtensionClass</code>. E.g.:</p> <pre><code>class MyComp(Component):\n    class MyExtension(ComponentExtension.ExtensionClass):\n        ...\n</code></pre> <p>This setting decides what the extension class will inherit from.</p>"},{"location":"reference/api/#django_components.ComponentExtension.class_name","title":"class_name  <code>instance-attribute</code>","text":"<pre><code>class_name: str\n</code></pre> <p>See source code</p> <p>Name of the extension class.</p> <p>By default, this is the same as <code>name</code>, but with snake_case converted to PascalCase.</p> <p>So if the extension name is <code>\"my_extension\"</code>, then the extension class name will be <code>\"MyExtension\"</code>.</p> <pre><code>class MyComp(Component):\n    class MyExtension:  # &lt;--- This is the extension class\n        ...\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.commands","title":"commands  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>commands: List[Type[ComponentCommand]] = []\n</code></pre> <p>See source code</p> <p>List of commands that can be run by the extension.</p> <p>These commands will be available to the user as <code>components ext run &lt;extension&gt; &lt;command&gt;</code>.</p> <p>Commands are defined as subclasses of <code>ComponentCommand</code>.</p> <p>Example:</p> <p>This example defines an extension with a command that prints \"Hello world\". To run the command, the user would run <code>components ext run hello_world hello</code>.</p> <pre><code>from django_components import ComponentCommand, ComponentExtension, CommandArg, CommandArgGroup\n\nclass HelloWorldCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Hello world command.\"\n\n    # Allow to pass flags `--foo`, `--bar` and `--baz`.\n    # Argument parsing is managed by `argparse`.\n    arguments = [\n        CommandArg(\n            name_or_flags=\"--foo\",\n            help=\"Foo description.\",\n        ),\n        # When printing the command help message, `bar` and `baz`\n        # will be grouped under \"group bar\".\n        CommandArgGroup(\n            title=\"group bar\",\n            description=\"Group description.\",\n            arguments=[\n                CommandArg(\n                    name_or_flags=\"--bar\",\n                    help=\"Bar description.\",\n                ),\n                CommandArg(\n                    name_or_flags=\"--baz\",\n                    help=\"Baz description.\",\n                ),\n            ],\n        ),\n    ]\n\n    # Callback that receives the parsed arguments and options.\n    def handle(self, *args, **kwargs):\n        print(f\"HelloWorldCommand.handle: args={args}, kwargs={kwargs}\")\n\n# Associate the command with the extension\nclass HelloWorldExtension(ComponentExtension):\n    name = \"hello_world\"\n\n    commands = [\n        HelloWorldCommand,\n    ]\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.name","title":"name  <code>instance-attribute</code>","text":"<pre><code>name: str\n</code></pre> <p>See source code</p> <p>Name of the extension.</p> <p>Name must be lowercase, and must be a valid Python identifier (e.g. <code>\"my_extension\"</code>).</p> <p>The extension may add new features to the <code>Component</code> class by allowing users to define and access a nested class in the <code>Component</code> class.</p> <p>The extension name determines the name of the nested class in the <code>Component</code> class, and the attribute under which the extension will be accessible.</p> <p>E.g. if the extension name is <code>\"my_extension\"</code>, then the nested class in the <code>Component</code> class will be <code>MyExtension</code>, and the extension will be accessible as <code>MyComp.my_extension</code>.</p> <pre><code>class MyComp(Component):\n    class MyExtension:\n        ...\n\n    def get_context_data(self):\n        return {\n            \"my_extension\": self.my_extension.do_something(),\n        }\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.urls","title":"urls  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>urls: List[URLRoute] = []\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_class_created","title":"on_component_class_created","text":"<pre><code>on_component_class_created(ctx: OnComponentClassCreatedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a new <code>Component</code> class is created.</p> <p>This hook is called after the <code>Component</code> class is fully defined but before it's registered.</p> <p>Use this hook to perform any initialization or validation of the <code>Component</code> class.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentClassCreatedContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_class_created(self, ctx: OnComponentClassCreatedContext) -&gt; None:\n        # Add a new attribute to the Component class\n        ctx.component_cls.my_attr = \"my_value\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_class_deleted","title":"on_component_class_deleted","text":"<pre><code>on_component_class_deleted(ctx: OnComponentClassDeletedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is being deleted.</p> <p>This hook is called before the <code>Component</code> class is deleted from memory.</p> <p>Use this hook to perform any cleanup related to the <code>Component</code> class.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentClassDeletedContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_class_deleted(self, ctx: OnComponentClassDeletedContext) -&gt; None:\n        # Remove Component class from the extension's cache on deletion\n        self.cache.pop(ctx.component_cls, None)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_data","title":"on_component_data","text":"<pre><code>on_component_data(ctx: OnComponentDataContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a Component was triggered to render, after a component's context and data methods have been processed.</p> <p>This hook is called after <code>Component.get_context_data()</code>, <code>Component.get_js_data()</code> and <code>Component.get_css_data()</code>.</p> <p>This hook runs after <code>on_component_input</code>.</p> <p>Use this hook to modify or validate the component's data before rendering.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentDataContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_data(self, ctx: OnComponentDataContext) -&gt; None:\n        # Add extra template variable to all components when they are rendered\n        ctx.context_data[\"my_template_var\"] = \"my_value\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_input","title":"on_component_input","text":"<pre><code>on_component_input(ctx: OnComponentInputContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> was triggered to render, but before a component's context and data methods are invoked.</p> <p>This hook is called before <code>Component.get_context_data()</code>, <code>Component.get_js_data()</code> and <code>Component.get_css_data()</code>.</p> <p>Use this hook to modify or validate component inputs before they're processed.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentInputContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_input(self, ctx: OnComponentInputContext) -&gt; None:\n        # Add extra kwarg to all components when they are rendered\n        ctx.kwargs[\"my_input\"] = \"my_value\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_registered","title":"on_component_registered","text":"<pre><code>on_component_registered(ctx: OnComponentRegisteredContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is registered with a <code>ComponentRegistry</code>.</p> <p>This hook is called after a <code>Component</code> class is successfully registered.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentRegisteredContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_registered(self, ctx: OnComponentRegisteredContext) -&gt; None:\n        print(f\"Component {ctx.component_cls} registered to {ctx.registry} as '{ctx.name}'\")\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_component_unregistered","title":"on_component_unregistered","text":"<pre><code>on_component_unregistered(ctx: OnComponentUnregisteredContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is unregistered from a <code>ComponentRegistry</code>.</p> <p>This hook is called after a <code>Component</code> class is removed from the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentUnregisteredContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_unregistered(self, ctx: OnComponentUnregisteredContext) -&gt; None:\n        print(f\"Component {ctx.component_cls} unregistered from {ctx.registry} as '{ctx.name}'\")\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_registry_created","title":"on_registry_created","text":"<pre><code>on_registry_created(ctx: OnRegistryCreatedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a new <code>ComponentRegistry</code> is created.</p> <p>This hook is called after a new <code>ComponentRegistry</code> instance is initialized.</p> <p>Use this hook to perform any initialization needed for the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnRegistryCreatedContext\n\nclass MyExtension(ComponentExtension):\n    def on_registry_created(self, ctx: OnRegistryCreatedContext) -&gt; None:\n        # Add a new attribute to the registry\n        ctx.registry.my_attr = \"my_value\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentExtension.on_registry_deleted","title":"on_registry_deleted","text":"<pre><code>on_registry_deleted(ctx: OnRegistryDeletedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>ComponentRegistry</code> is being deleted.</p> <p>This hook is called before a <code>ComponentRegistry</code> instance is deleted.</p> <p>Use this hook to perform any cleanup related to the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnRegistryDeletedContext\n\nclass MyExtension(ComponentExtension):\n    def on_registry_deleted(self, ctx: OnRegistryDeletedContext) -&gt; None:\n        # Remove registry from the extension's cache on deletion\n        self.cache.pop(ctx.registry, None)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentFileEntry","title":"ComponentFileEntry","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>Result returned by <code>get_component_files()</code>.</p> <p>Attributes:</p> <ul> <li> <code>dot_path</code>               (<code>str</code>)           \u2013            </li> <li> <code>filepath</code>               (<code>Path</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentFileEntry.dot_path","title":"dot_path  <code>instance-attribute</code>","text":"<pre><code>dot_path: str\n</code></pre> <p>See source code</p> <p>The python import path for the module. E.g. <code>app.components.mycomp</code></p>"},{"location":"reference/api/#django_components.ComponentFileEntry.filepath","title":"filepath  <code>instance-attribute</code>","text":"<pre><code>filepath: Path\n</code></pre> <p>See source code</p> <p>The filesystem path to the module. E.g. <code>/path/to/project/app/components/mycomp.py</code></p>"},{"location":"reference/api/#django_components.ComponentMediaInput","title":"ComponentMediaInput","text":"<p>Bases: <code>typing.Protocol</code></p> <p>See source code</p> <p>Defines JS and CSS media files associated with a <code>Component</code>.</p> <pre><code>class MyTable(Component):\n    class Media:\n        js = [\n            \"path/to/script.js\",\n            \"https://unpkg.com/alpinejs@3.14.7/dist/cdn.min.js\",  # AlpineJS\n        ]\n        css = {\n            \"all\": [\n                \"path/to/style.css\",\n                \"https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css\",  # TailwindCSS\n            ],\n            \"print\": [\"path/to/style2.css\"],\n        }\n</code></pre> <p>Attributes:</p> <ul> <li> <code>css</code>               (<code>Optional[Union[ComponentMediaInputPath, List[ComponentMediaInputPath], Dict[str, ComponentMediaInputPath], Dict[str, List[ComponentMediaInputPath]]]]</code>)           \u2013            </li> <li> <code>extend</code>               (<code>Union[bool, List[Type[Component]]]</code>)           \u2013            </li> <li> <code>js</code>               (<code>Optional[Union[ComponentMediaInputPath, List[ComponentMediaInputPath]]]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentMediaInput.css","title":"css  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>css: Optional[\n    Union[\n        ComponentMediaInputPath, List[ComponentMediaInputPath], Dict[str, ComponentMediaInputPath], Dict[str, List[ComponentMediaInputPath]]\n    ]\n] = None\n</code></pre> <p>See source code</p> <p>CSS files associated with a <code>Component</code>.</p> <ul> <li> <p>If a string, it's assumed to be a path to a CSS file.</p> </li> <li> <p>If a list, each entry is assumed to be a path to a CSS file.</p> </li> <li> <p>If a dict, the keys are media types (e.g. \"all\", \"print\", \"screen\", etc.), and the values are either:</p> <ul> <li>A string, assumed to be a path to a CSS file.</li> <li>A list, each entry is assumed to be a path to a CSS file.</li> </ul> </li> </ul> <p>Each entry can be a string, bytes, SafeString, PathLike, or a callable that returns one of the former (see <code>ComponentMediaInputPath</code>).</p> <p>Examples: <pre><code>class MyComponent(Component):\n    class Media:\n        css = \"path/to/style.css\"\n</code></pre></p> <pre><code>class MyComponent(Component):\n    class Media:\n        css = [\"path/to/style1.css\", \"path/to/style2.css\"]\n</code></pre> <pre><code>class MyComponent(Component):\n    class Media:\n        css = {\n            \"all\": \"path/to/style.css\",\n            \"print\": \"path/to/print.css\",\n        }\n</code></pre> <pre><code>class MyComponent(Component):\n    class Media:\n        css = {\n            \"all\": [\"path/to/style1.css\", \"path/to/style2.css\"],\n            \"print\": \"path/to/print.css\",\n        }\n</code></pre>"},{"location":"reference/api/#django_components.ComponentMediaInput.extend","title":"extend  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>extend: Union[bool, List[Type[Component]]] = True\n</code></pre> <p>See source code</p> <p>Configures whether the component should inherit the media files from the parent component.</p> <ul> <li>If <code>True</code>, the component inherits the media files from the parent component.</li> <li>If <code>False</code>, the component does not inherit the media files from the parent component.</li> <li>If a list of components classes, the component inherits the media files ONLY from these specified components.</li> </ul> <p>Read more in Controlling Media Inheritance section.</p> <p>Example:</p> <p>Disable media inheritance:</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        extend = False  # Don't inherit parent media\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"script.js\"]\n</code></pre> <p>Specify which components to inherit from. In this case, the media files are inherited ONLY from the specified components, and NOT from the original parent components:</p> <pre><code>class ParentComponent(Component):\n    class Media:\n        js = [\"parent.js\"]\n\nclass MyComponent(ParentComponent):\n    class Media:\n        # Only inherit from these, ignoring the files from the parent\n        extend = [OtherComponent1, OtherComponent2]\n\n        js = [\"script.js\"]\n\nprint(MyComponent.media._js)  # [\"script.js\", \"other1.js\", \"other2.js\"]\n</code></pre>"},{"location":"reference/api/#django_components.ComponentMediaInput.js","title":"js  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>js: Optional[Union[ComponentMediaInputPath, List[ComponentMediaInputPath]]] = None\n</code></pre> <p>See source code</p> <p>JS files associated with a <code>Component</code>.</p> <ul> <li> <p>If a string, it's assumed to be a path to a JS file.</p> </li> <li> <p>If a list, each entry is assumed to be a path to a JS file.</p> </li> </ul> <p>Each entry can be a string, bytes, SafeString, PathLike, or a callable that returns one of the former (see <code>ComponentMediaInputPath</code>).</p> <p>Examples: <pre><code>class MyComponent(Component):\n    class Media:\n        js = \"path/to/script.js\"\n</code></pre></p> <pre><code>class MyComponent(Component):\n    class Media:\n        js = [\"path/to/script1.js\", \"path/to/script2.js\"]\n</code></pre> <pre><code>class MyComponent(Component):\n    class Media:\n        js = lambda: [\"path/to/script1.js\", \"path/to/script2.js\"]\n</code></pre>"},{"location":"reference/api/#django_components.ComponentMediaInputPath","title":"ComponentMediaInputPath  <code>module-attribute</code>","text":"<pre><code>ComponentMediaInputPath = Union[str, bytes, SafeData, Path, PathLike, Callable[[], Union[str, bytes, SafeData, Path, PathLike]]]\n</code></pre> <p>See source code</p> <p>A type representing an entry in Media.js or Media.css.</p> <p>If an entry is a SafeString (or has <code>__html__</code> method), then entry is assumed to be a formatted HTML tag. Otherwise, it's assumed to be a path to a file.</p> <p>Example:</p> <pre><code>class MyComponent\n    class Media:\n        js = [\n            \"path/to/script.js\",\n            b\"script.js\",\n            SafeString(\"&lt;script src='path/to/script.js'&gt;&lt;/script&gt;\"),\n        ]\n        css = [\n            Path(\"path/to/style.css\"),\n            lambda: \"path/to/style.css\",\n            lambda: Path(\"path/to/style.css\"),\n        ]\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry","title":"ComponentRegistry","text":"<pre><code>ComponentRegistry(\n    library: Optional[Library] = None, settings: Optional[Union[RegistrySettings, Callable[[ComponentRegistry], RegistrySettings]]] = None\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Manages components and makes them available in the template, by default as <code>{% component %}</code> tags.</p> <pre><code>{% component \"my_comp\" key=value %}\n{% endcomponent %}\n</code></pre> <p>To enable a component to be used in a template, the component must be registered with a component registry.</p> <p>When you register a component to a registry, behind the scenes the registry automatically adds the component's template tag (e.g. <code>{% component %}</code> to the <code>Library</code>. And the opposite happens when you unregister a component - the tag is removed.</p> <p>See Registering components.</p> <p>Parameters:</p> <ul> <li> <code>library</code>               (<code>Library</code>, default:                   <code>None</code> )           \u2013            <p>Django            <code>Library</code>            associated with this registry. If omitted, the default Library instance from django_components is used.</p> </li> <li> <code>settings</code>               (<code>Union[RegistrySettings, Callable[[ComponentRegistry], RegistrySettings]]</code>, default:                   <code>None</code> )           \u2013            <p>Configure            how the components registered with this registry will behave when rendered.            See <code>RegistrySettings</code>. Can be either            a static value or a callable that returns the settings. If omitted, the settings from            <code>COMPONENTS</code> are used.</p> </li> </ul> <p>Notes:</p> <ul> <li>The default registry is available as <code>django_components.registry</code>.</li> <li>The default registry is used when registering components with <code>@register</code> decorator.</li> </ul> <p>Example:</p> <pre><code># Use with default Library\nregistry = ComponentRegistry()\n\n# Or a custom one\nmy_lib = Library()\nregistry = ComponentRegistry(library=my_lib)\n\n# Usage\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\nregistry.all()\nregistry.clear()\nregistry.get(\"button\")\nregistry.has(\"button\")\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry--using-registry-to-share-components","title":"Using registry to share components","text":"<p>You can use component registry for isolating or \"packaging\" components:</p> <ol> <li> <p>Create new instance of <code>ComponentRegistry</code> and Library:     <pre><code>my_comps = Library()\nmy_comps_reg = ComponentRegistry(library=my_comps)\n</code></pre></p> </li> <li> <p>Register components to the registry:     <pre><code>my_comps_reg.register(\"my_button\", ButtonComponent)\nmy_comps_reg.register(\"my_card\", CardComponent)\n</code></pre></p> </li> <li> <p>In your target project, load the Library associated with the registry:     <pre><code>{% load my_comps %}\n</code></pre></p> </li> <li> <p>Use the registered components in your templates:     <pre><code>{% component \"button\" %}\n{% endcomponent %}\n</code></pre></p> </li> </ol> <p>Methods:</p> <ul> <li> <code>all</code>             \u2013              </li> <li> <code>clear</code>             \u2013              </li> <li> <code>get</code>             \u2013              </li> <li> <code>has</code>             \u2013              </li> <li> <code>register</code>             \u2013              </li> <li> <code>unregister</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>library</code>               (<code>Library</code>)           \u2013            </li> <li> <code>settings</code>               (<code>InternalRegistrySettings</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentRegistry.library","title":"library  <code>property</code>","text":"<pre><code>library: Library\n</code></pre> <p>See source code</p> <p>The template tag <code>Library</code> that is associated with the registry.</p>"},{"location":"reference/api/#django_components.ComponentRegistry.settings","title":"settings  <code>property</code>","text":"<pre><code>settings: InternalRegistrySettings\n</code></pre> <p>See source code</p> <p>Registry settings configured for this registry.</p>"},{"location":"reference/api/#django_components.ComponentRegistry.all","title":"all","text":"<pre><code>all() -&gt; Dict[str, Type[Component]]\n</code></pre> <p>See source code</p> <p>Retrieve all registered <code>Component</code> classes.</p> <p>Returns:</p> <ul> <li> <code>Dict[str, Type[Component]]</code>           \u2013            <p>Dict[str, Type[Component]]: A dictionary of component names to component classes</p> </li> </ul> <p>Example:</p> <pre><code># First register components\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\n# Then get all\nregistry.all()\n# &gt; {\n# &gt;   \"button\": ButtonComponent,\n# &gt;   \"card\": CardComponent,\n# &gt; }\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.clear","title":"clear","text":"<pre><code>clear() -&gt; None\n</code></pre> <p>See source code</p> <p>Clears the registry, unregistering all components.</p> <p>Example:</p> <pre><code># First register components\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\n# Then clear\nregistry.clear()\n# Then get all\nregistry.all()\n# &gt; {}\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.get","title":"get","text":"<pre><code>get(name: str) -&gt; Type[Component]\n</code></pre> <p>See source code</p> <p>Retrieve a <code>Component</code> class registered under the given name.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>The name under which the component was registered. Required.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>Type[Component]</code>           \u2013            <p>Type[Component]: The component class registered under the given name.</p> </li> </ul> <p>Raises:</p> <ul> <li><code>NotRegistered</code>   if the given name is not registered.</li> </ul> <p>Example:</p> <pre><code># First register component\nregistry.register(\"button\", ButtonComponent)\n# Then get\nregistry.get(\"button\")\n# &gt; ButtonComponent\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.has","title":"has","text":"<pre><code>has(name: str) -&gt; bool\n</code></pre> <p>See source code</p> <p>Check if a <code>Component</code> class is registered under the given name.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>The name under which the component was registered. Required.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>bool</code> (              <code>bool</code> )          \u2013            <p><code>True</code> if the component is registered, <code>False</code> otherwise.</p> </li> </ul> <p>Example:</p> <pre><code># First register component\nregistry.register(\"button\", ButtonComponent)\n# Then check\nregistry.has(\"button\")\n# &gt; True\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.register","title":"register","text":"<pre><code>register(name: str, component: Type[Component]) -&gt; None\n</code></pre> <p>See source code</p> <p>Register a <code>Component</code> class with this registry under the given name.</p> <p>A component MUST be registered before it can be used in a template such as: <pre><code>{% component \"my_comp\" %}\n{% endcomponent %}\n</code></pre></p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>The name under which the component will be registered. Required.</p> </li> <li> <code>component</code>               (<code>Type[Component]</code>)           \u2013            <p>The component class to register. Required.</p> </li> </ul> <p>Raises:</p> <ul> <li><code>AlreadyRegistered</code> if a different component was already registered under the same name.</li> </ul> <p>Example:</p> <pre><code>registry.register(\"button\", ButtonComponent)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentRegistry.unregister","title":"unregister","text":"<pre><code>unregister(name: str) -&gt; None\n</code></pre> <p>See source code</p> <p>Unregister the <code>Component</code> class that was registered under the given name.</p> <p>Once a component is unregistered, it is no longer available in the templates.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>The name under which the component is registered. Required.</p> </li> </ul> <p>Raises:</p> <ul> <li><code>NotRegistered</code> if the given name is not registered.</li> </ul> <p>Example:</p> <pre><code># First register component\nregistry.register(\"button\", ButtonComponent)\n# Then unregister\nregistry.unregister(\"button\")\n</code></pre>"},{"location":"reference/api/#django_components.ComponentVars","title":"ComponentVars","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>Type for the variables available inside the component templates.</p> <p>All variables here are scoped under <code>component_vars.</code>, so e.g. attribute <code>is_filled</code> on this class is accessible inside the template as:</p> <pre><code>{{ component_vars.is_filled }}\n</code></pre> <p>Attributes:</p> <ul> <li> <code>is_filled</code>               (<code>Dict[str, bool]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentVars.is_filled","title":"is_filled  <code>instance-attribute</code>","text":"<pre><code>is_filled: Dict[str, bool]\n</code></pre> <p>See source code</p> <p>Dictonary describing which component slots are filled (<code>True</code>) or are not (<code>False</code>).</p> <p>New in version 0.70</p> <p>Use as <code>{{ component_vars.is_filled }}</code></p> <p>Example:</p> <pre><code>{# Render wrapping HTML only if the slot is defined #}\n{% if component_vars.is_filled.my_slot %}\n    &lt;div class=\"slot-wrapper\"&gt;\n        {% slot \"my_slot\" / %}\n    &lt;/div&gt;\n{% endif %}\n</code></pre> <p>This is equivalent to checking if a given key is among the slot fills:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"my_slot_filled\": \"my_slot\" in self.input.slots\n        }\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView","title":"ComponentView","text":"<pre><code>ComponentView(component: Component, **kwargs: Any)\n</code></pre> <p>Bases: <code>django_components.extension.BaseExtensionClass</code>, <code>django.views.generic.base.View</code></p> <p>See source code</p> <p>Subclass of <code>django.views.View</code> where the <code>Component</code> instance is available via <code>self.component</code>.</p> <p>Methods:</p> <ul> <li> <code>delete</code>             \u2013              </li> <li> <code>get</code>             \u2013              </li> <li> <code>head</code>             \u2013              </li> <li> <code>options</code>             \u2013              </li> <li> <code>patch</code>             \u2013              </li> <li> <code>post</code>             \u2013              </li> <li> <code>put</code>             \u2013              </li> <li> <code>trace</code>             \u2013              </li> </ul> <p>Attributes:</p> <ul> <li> <code>component</code>           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentView.component","title":"component  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>component = cast('Component', None)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.delete","title":"delete","text":"<pre><code>delete(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.get","title":"get","text":"<pre><code>get(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.head","title":"head","text":"<pre><code>head(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.options","title":"options","text":"<pre><code>options(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.patch","title":"patch","text":"<pre><code>patch(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.post","title":"post","text":"<pre><code>post(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.put","title":"put","text":"<pre><code>put(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentView.trace","title":"trace","text":"<pre><code>trace(request: HttpRequest, *args: Any, **kwargs: Any) -&gt; HttpResponse\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings","title":"ComponentsSettings","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>Settings available for django_components.</p> <p>Example:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    autodiscover=False,\n    dirs = [BASE_DIR / \"components\"],\n)\n</code></pre> <p>Attributes:</p> <ul> <li> <code>app_dirs</code>               (<code>Optional[Sequence[str]]</code>)           \u2013            </li> <li> <code>autodiscover</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>cache</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>context_behavior</code>               (<code>Optional[ContextBehaviorType]</code>)           \u2013            </li> <li> <code>debug_highlight_components</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>debug_highlight_slots</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>dirs</code>               (<code>Optional[Sequence[Union[str, PathLike, Tuple[str, str], Tuple[str, PathLike]]]]</code>)           \u2013            </li> <li> <code>dynamic_component_name</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>extensions</code>               (<code>Optional[Sequence[Union[Type[ComponentExtension], str]]]</code>)           \u2013            </li> <li> <code>forbidden_static_files</code>               (<code>Optional[List[Union[str, Pattern]]]</code>)           \u2013            </li> <li> <code>libraries</code>               (<code>Optional[List[str]]</code>)           \u2013            </li> <li> <code>multiline_tags</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>reload_on_file_change</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>reload_on_template_change</code>               (<code>Optional[bool]</code>)           \u2013            </li> <li> <code>static_files_allowed</code>               (<code>Optional[List[Union[str, Pattern]]]</code>)           \u2013            </li> <li> <code>static_files_forbidden</code>               (<code>Optional[List[Union[str, Pattern]]]</code>)           \u2013            </li> <li> <code>tag_formatter</code>               (<code>Optional[Union[TagFormatterABC, str]]</code>)           \u2013            </li> <li> <code>template_cache_size</code>               (<code>Optional[int]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ComponentsSettings.app_dirs","title":"app_dirs  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>app_dirs: Optional[Sequence[str]] = None\n</code></pre> <p>See source code</p> <p>Specify the app-level directories that contain your components.</p> <p>Defaults to <code>[\"components\"]</code>. That is, for each Django app, we search <code>&lt;app&gt;/components/</code> for components.</p> <p>The paths must be relative to app, e.g.:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    app_dirs=[\"my_comps\"],\n)\n</code></pre> <p>To search for <code>&lt;app&gt;/my_comps/</code>.</p> <p>These locations are searched during autodiscovery, or when you define HTML, JS, or CSS as separate files.</p> <p>Set to empty list to disable app-level components:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    app_dirs=[],\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.autodiscover","title":"autodiscover  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>autodiscover: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Toggle whether to run autodiscovery at the Django server startup.</p> <p>Defaults to <code>True</code></p> <pre><code>COMPONENTS = ComponentsSettings(\n    autodiscover=False,\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.cache","title":"cache  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>cache: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the Django cache to be used for storing component's JS and CSS files.</p> <p>If <code>None</code>, a <code>LocMemCache</code> is used with default settings.</p> <p>Defaults to <code>None</code>.</p> <p>Read more about caching.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    cache=\"my_cache\",\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.context_behavior","title":"context_behavior  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>context_behavior: Optional[ContextBehaviorType] = None\n</code></pre> <p>See source code</p> <p>Configure whether, inside a component template, you can use variables from the outside (<code>\"django\"</code>) or not (<code>\"isolated\"</code>). This also affects what variables are available inside the <code>{% fill %}</code> tags.</p> <p>Also see Component context and scope.</p> <p>Defaults to <code>\"django\"</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    context_behavior=\"isolated\",\n)\n</code></pre> <p>NOTE: <code>context_behavior</code> and <code>slot_context_behavior</code> options were merged in v0.70.</p> <p>If you are migrating from BEFORE v0.67, set <code>context_behavior</code> to <code>\"django\"</code>. From v0.67 to v0.78 (incl) the default value was <code>\"isolated\"</code>.</p> <p>For v0.79 and later, the default is again <code>\"django\"</code>. See the rationale for change here.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.debug_highlight_components","title":"debug_highlight_components  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>debug_highlight_components: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable component highlighting. See Troubleshooting for more details.</p> <p>Defaults to <code>False</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    debug_highlight_components=True,\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.debug_highlight_slots","title":"debug_highlight_slots  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>debug_highlight_slots: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable slot highlighting. See Troubleshooting for more details.</p> <p>Defaults to <code>False</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    debug_highlight_slots=True,\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.dirs","title":"dirs  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>dirs: Optional[Sequence[Union[str, PathLike, Tuple[str, str], Tuple[str, PathLike]]]] = None\n</code></pre> <p>See source code</p> <p>Specify the directories that contain your components.</p> <p>Defaults to <code>[Path(settings.BASE_DIR) / \"components\"]</code>. That is, the root <code>components/</code> app.</p> <p>Directories must be full paths, same as with STATICFILES_DIRS.</p> <p>These locations are searched during autodiscovery, or when you define HTML, JS, or CSS as separate files.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    dirs=[BASE_DIR / \"components\"],\n)\n</code></pre> <p>Set to empty list to disable global components directories:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    dirs=[],\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.dynamic_component_name","title":"dynamic_component_name  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>dynamic_component_name: Optional[str] = None\n</code></pre> <p>See source code</p> <p>By default, the dynamic component is registered under the name <code>\"dynamic\"</code>.</p> <p>In case of a conflict, you can use this setting to change the component name used for the dynamic components.</p> <pre><code># settings.py\nCOMPONENTS = ComponentsSettings(\n    dynamic_component_name=\"my_dynamic\",\n)\n</code></pre> <p>After which you will be able to use the dynamic component with the new name:</p> <pre><code>{% component \"my_dynamic\" is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.extensions","title":"extensions  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>extensions: Optional[Sequence[Union[Type[ComponentExtension], str]]] = None\n</code></pre> <p>See source code</p> <p>List of extensions to be loaded.</p> <p>The extensions can be specified as:</p> <ul> <li>Python import path, e.g. <code>\"path.to.my_extension.MyExtension\"</code>.</li> <li>Extension class, e.g. <code>my_extension.MyExtension</code>.</li> </ul> <pre><code>COMPONENTS = ComponentsSettings(\n    extensions=[\n        \"path.to.my_extension.MyExtension\",\n        StorybookExtension,\n    ],\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.forbidden_static_files","title":"forbidden_static_files  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>forbidden_static_files: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>COMPONENTS.static_files_forbidden</code> instead.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.libraries","title":"libraries  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>libraries: Optional[List[str]] = None\n</code></pre> <p>See source code</p> <p>Configure extra python modules that should be loaded.</p> <p>This may be useful if you are not using the autodiscovery feature, or you need to load components from non-standard locations. Thus you can have a structure of components that is independent from your apps.</p> <p>Expects a list of python module paths. Defaults to empty list.</p> <p>Example:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    libraries=[\n        \"mysite.components.forms\",\n        \"mysite.components.buttons\",\n        \"mysite.components.cards\",\n    ],\n)\n</code></pre> <p>This would be the equivalent of importing these modules from within Django's <code>AppConfig.ready()</code>:</p> <pre><code>class MyAppConfig(AppConfig):\n    def ready(self):\n        import \"mysite.components.forms\"\n        import \"mysite.components.buttons\"\n        import \"mysite.components.cards\"\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.libraries--manually-loading-libraries","title":"Manually loading libraries","text":"<p>In the rare case that you need to manually trigger the import of libraries, you can use the <code>import_libraries()</code> function:</p> <pre><code>from django_components import import_libraries\n\nimport_libraries()\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.multiline_tags","title":"multiline_tags  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>multiline_tags: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable multiline support for template tags. If <code>True</code>, template tags like <code>{% component %}</code> or <code>{{ my_var }}</code> can span multiple lines.</p> <p>Defaults to <code>True</code>.</p> <p>Disable this setting if you are making custom modifications to Django's regular expression for parsing templates at <code>django.template.base.tag_re</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    multiline_tags=False,\n)\n</code></pre>"},{"location":"reference/api/#django_components.ComponentsSettings.reload_on_file_change","title":"reload_on_file_change  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>reload_on_file_change: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>This is relevant if you are using the project structure where HTML, JS, CSS and Python are in separate files and nested in a directory.</p> <p>In this case you may notice that when you are running a development server, the server sometimes does not reload when you change component files.</p> <p>Django's native live reload logic handles only Python files and HTML template files. It does NOT reload when other file types change or when template files are nested more than one level deep.</p> <p>The setting <code>reload_on_file_change</code> fixes this, reloading the dev server even when your component's HTML, JS, or CSS changes.</p> <p>If <code>True</code>, django_components configures Django to reload when files inside <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> change.</p> <p>See Reload dev server on component file changes.</p> <p>Defaults to <code>False</code>.</p> <p>Warning</p> <p>This setting should be enabled only for the dev environment!</p>"},{"location":"reference/api/#django_components.ComponentsSettings.reload_on_template_change","title":"reload_on_template_change  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>reload_on_template_change: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>COMPONENTS.reload_on_file_change</code> instead.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.static_files_allowed","title":"static_files_allowed  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>static_files_allowed: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>A list of file extensions (including the leading dot) that define which files within <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> are treated as static files.</p> <p>If a file is matched against any of the patterns, it's considered a static file. Such files are collected when running <code>collectstatic</code>, and can be accessed under the static file endpoint.</p> <p>You can also pass in compiled regexes (<code>re.Pattern</code>) for more advanced patterns.</p> <p>By default, JS, CSS, and common image and font file formats are considered static files:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    static_files_allowed=[\n        \".css\",\n        \".js\", \".jsx\", \".ts\", \".tsx\",\n        # Images\n        \".apng\", \".png\", \".avif\", \".gif\", \".jpg\",\n        \".jpeg\",  \".jfif\", \".pjpeg\", \".pjp\", \".svg\",\n        \".webp\", \".bmp\", \".ico\", \".cur\", \".tif\", \".tiff\",\n        # Fonts\n        \".eot\", \".ttf\", \".woff\", \".otf\", \".svg\",\n    ],\n)\n</code></pre> <p>Warning</p> <p>Exposing your Python files can be a security vulnerability. See Security notes.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.static_files_forbidden","title":"static_files_forbidden  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>static_files_forbidden: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>A list of file extensions (including the leading dot) that define which files within <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> will NEVER be treated as static files.</p> <p>If a file is matched against any of the patterns, it will never be considered a static file, even if the file matches a pattern in <code>static_files_allowed</code>.</p> <p>Use this setting together with <code>static_files_allowed</code> for a fine control over what file types will be exposed.</p> <p>You can also pass in compiled regexes (<code>re.Pattern</code>) for more advanced patterns.</p> <p>By default, any HTML and Python are considered NOT static files:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    static_files_forbidden=[\n        \".html\", \".django\", \".dj\", \".tpl\",\n        # Python files\n        \".py\", \".pyc\",\n    ],\n)\n</code></pre> <p>Warning</p> <p>Exposing your Python files can be a security vulnerability. See Security notes.</p>"},{"location":"reference/api/#django_components.ComponentsSettings.tag_formatter","title":"tag_formatter  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>tag_formatter: Optional[Union[TagFormatterABC, str]] = None\n</code></pre> <p>See source code</p> <p>Configure what syntax is used inside Django templates to render components. See the available tag formatters.</p> <p>Defaults to <code>\"django_components.component_formatter\"</code>.</p> <p>Learn more about Customizing component tags with TagFormatter.</p> <p>Can be set either as direct reference:</p> <pre><code>from django_components import component_formatter\n\nCOMPONENTS = ComponentsSettings(\n    \"tag_formatter\": component_formatter\n)\n</code></pre> <p>Or as an import string;</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_formatter\"\n)\n</code></pre> <p>Examples:</p> <ul> <li> <p><code>\"django_components.component_formatter\"</code></p> <p>Set</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_formatter\"\n)\n</code></pre> <p>To write components like this:</p> <pre><code>{% component \"button\" href=\"...\" %}\n    Click me!\n{% endcomponent %}\n</code></pre> </li> <li> <p><code>django_components.component_shorthand_formatter</code></p> <p>Set</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_shorthand_formatter\"\n)\n</code></pre> <p>To write components like this:</p> <pre><code>{% button href=\"...\" %}\n    Click me!\n{% endbutton %}\n</code></pre> </li> </ul>"},{"location":"reference/api/#django_components.ComponentsSettings.template_cache_size","title":"template_cache_size  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>template_cache_size: Optional[int] = None\n</code></pre> <p>See source code</p> <p>Configure the maximum amount of Django templates to be cached.</p> <p>Defaults to <code>128</code>.</p> <p>Each time a Django template is rendered, it is cached to a global in-memory cache (using Python's <code>lru_cache</code> decorator). This speeds up the next render of the component. As the same component is often used many times on the same page, these savings add up.</p> <p>By default the cache holds 128 component templates in memory, which should be enough for most sites. But if you have a lot of components, or if you are overriding <code>Component.get_template()</code> to render many dynamic templates, you can increase this number.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    template_cache_size=256,\n)\n</code></pre> <p>To remove the cache limit altogether and cache everything, set <code>template_cache_size</code> to <code>None</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    template_cache_size=None,\n)\n</code></pre> <p>If you want to add templates to the cache yourself, you can use <code>cached_template()</code>:</p> <pre><code>from django_components import cached_template\n\ncached_template(\"Variable: {{ variable }}\")\n\n# You can optionally specify Template class, and other Template inputs:\nclass MyTemplate(Template):\n    pass\n\ncached_template(\n    \"Variable: {{ variable }}\",\n    template_cls=MyTemplate,\n    name=...\n    origin=...\n    engine=...\n)\n</code></pre>"},{"location":"reference/api/#django_components.ContextBehavior","title":"ContextBehavior","text":"<p>Bases: <code>str</code>, <code>enum.Enum</code></p> <p>See source code</p> <p>Configure how (and whether) the context is passed to the component fills and what variables are available inside the <code>{% fill %}</code> tags.</p> <p>Also see Component context and scope.</p> <p>Options:</p> <ul> <li><code>django</code>: With this setting, component fills behave as usual Django tags.</li> <li><code>isolated</code>: This setting makes the component fills behave similar to Vue or React.</li> </ul> <p>Attributes:</p> <ul> <li> <code>DJANGO</code>           \u2013            </li> <li> <code>ISOLATED</code>           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.ContextBehavior.DJANGO","title":"DJANGO  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>DJANGO = 'django'\n</code></pre> <p>See source code</p> <p>With this setting, component fills behave as usual Django tags. That is, they enrich the context, and pass it along.</p> <ol> <li>Component fills use the context of the component they are within.</li> <li>Variables from <code>Component.get_context_data()</code> are available to the component fill.</li> </ol> <p>Example:</p> <p>Given this template <pre><code>{% with cheese=\"feta\" %}\n  {% component 'my_comp' %}\n    {{ my_var }}  # my_var\n    {{ cheese }}  # cheese\n  {% endcomponent %}\n{% endwith %}\n</code></pre></p> <p>and this context returned from the <code>Component.get_context_data()</code> method <pre><code>{ \"my_var\": 123 }\n</code></pre></p> <p>Then if component \"my_comp\" defines context <pre><code>{ \"my_var\": 456 }\n</code></pre></p> <p>Then this will render: <pre><code>456   # my_var\nfeta  # cheese\n</code></pre></p> <p>Because \"my_comp\" overrides the variable \"my_var\", so <code>{{ my_var }}</code> equals <code>456</code>.</p> <p>And variable \"cheese\" will equal <code>feta</code>, because the fill CAN access the current context.</p>"},{"location":"reference/api/#django_components.ContextBehavior.ISOLATED","title":"ISOLATED  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>ISOLATED = 'isolated'\n</code></pre> <p>See source code</p> <p>This setting makes the component fills behave similar to Vue or React, where the fills use EXCLUSIVELY the context variables defined in <code>Component.get_context_data()</code>.</p> <p>Example:</p> <p>Given this template <pre><code>{% with cheese=\"feta\" %}\n  {% component 'my_comp' %}\n    {{ my_var }}  # my_var\n    {{ cheese }}  # cheese\n  {% endcomponent %}\n{% endwith %}\n</code></pre></p> <p>and this context returned from the <code>get_context_data()</code> method <pre><code>{ \"my_var\": 123 }\n</code></pre></p> <p>Then if component \"my_comp\" defines context <pre><code>{ \"my_var\": 456 }\n</code></pre></p> <p>Then this will render: <pre><code>123   # my_var\n      # cheese\n</code></pre></p> <p>Because both variables \"my_var\" and \"cheese\" are taken from the root context. Since \"cheese\" is not defined in root context, it's empty.</p>"},{"location":"reference/api/#django_components.EmptyDict","title":"EmptyDict","text":"<p>Bases: <code>dict</code></p> <p>See source code</p> <p>TypedDict with no members.</p> <p>You can use this to define a Component that accepts NO kwargs, or NO slots, or returns NO data from <code>Component.get_context_data()</code> / <code>Component.get_js_data()</code> / <code>Component.get_css_data()</code>:</p> <p>Accepts NO kwargs:</p> <pre><code>from django_components import Component, EmptyDict\n\nclass Table(Component(Any, EmptyDict, Any, Any, Any, Any))\n    ...\n</code></pre> <p>Accepts NO slots:</p> <pre><code>from django_components import Component, EmptyDict\n\nclass Table(Component(Any, Any, EmptyDict, Any, Any, Any))\n    ...\n</code></pre> <p>Returns NO data from <code>get_context_data()</code>:</p> <pre><code>from django_components import Component, EmptyDict\n\nclass Table(Component(Any, Any, Any, EmptyDict, Any, Any))\n    ...\n</code></pre> <p>Going back to the example with NO kwargs, when you then call <code>Component.render()</code> or <code>Component.render_to_response()</code>, the <code>kwargs</code> parameter will raise type error if <code>kwargs</code> is anything else than an empty dict.</p> <pre><code>Table.render(\n    kwargs: {},\n)\n</code></pre> <p>Omitting <code>kwargs</code> is also fine:</p> <pre><code>Table.render()\n</code></pre> <p>Other values are not allowed. This will raise an error with MyPy:</p> <pre><code>Table.render(\n    kwargs: {\n        \"one\": 2,\n        \"three\": 4,\n    },\n)\n</code></pre>"},{"location":"reference/api/#django_components.EmptyTuple","title":"EmptyTuple  <code>module-attribute</code>","text":"<pre><code>EmptyTuple = Tuple[]\n</code></pre> <p>See source code</p> <p>Tuple with no members.</p> <p>You can use this to define a Component that accepts NO positional arguments:</p> <pre><code>from django_components import Component, EmptyTuple\n\nclass Table(Component(EmptyTuple, Any, Any, Any, Any, Any))\n    ...\n</code></pre> <p>After that, when you call <code>Component.render()</code> or <code>Component.render_to_response()</code>, the <code>args</code> parameter will raise type error if <code>args</code> is anything else than an empty tuple.</p> <pre><code>Table.render(\n    args: (),\n)\n</code></pre> <p>Omitting <code>args</code> is also fine:</p> <pre><code>Table.render()\n</code></pre> <p>Other values are not allowed. This will raise an error with MyPy:</p> <pre><code>Table.render(\n    args: (\"one\", 2, \"three\"),\n)\n</code></pre>"},{"location":"reference/api/#django_components.OnComponentClassCreatedContext","title":"OnComponentClassCreatedContext","text":"<p>Attributes:</p> <ul> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentClassCreatedContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The created Component class</p>"},{"location":"reference/api/#django_components.OnComponentClassDeletedContext","title":"OnComponentClassDeletedContext","text":"<p>Attributes:</p> <ul> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentClassDeletedContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The to-be-deleted Component class</p>"},{"location":"reference/api/#django_components.OnComponentDataContext","title":"OnComponentDataContext","text":"<p>Attributes:</p> <ul> <li> <code>component</code>               (<code>Component</code>)           \u2013            </li> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> <li> <code>component_id</code>               (<code>str</code>)           \u2013            </li> <li> <code>context_data</code>               (<code>Dict</code>)           \u2013            </li> <li> <code>css_data</code>               (<code>Dict</code>)           \u2013            </li> <li> <code>js_data</code>               (<code>Dict</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentDataContext.component","title":"component  <code>instance-attribute</code>","text":"<pre><code>component: Component\n</code></pre> <p>See source code</p> <p>The Component instance that is being rendered</p>"},{"location":"reference/api/#django_components.OnComponentDataContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The Component class</p>"},{"location":"reference/api/#django_components.OnComponentDataContext.component_id","title":"component_id  <code>instance-attribute</code>","text":"<pre><code>component_id: str\n</code></pre> <p>See source code</p> <p>The unique identifier for this component instance</p>"},{"location":"reference/api/#django_components.OnComponentDataContext.context_data","title":"context_data  <code>instance-attribute</code>","text":"<pre><code>context_data: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of context data from <code>Component.get_context_data()</code></p>"},{"location":"reference/api/#django_components.OnComponentDataContext.css_data","title":"css_data  <code>instance-attribute</code>","text":"<pre><code>css_data: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of CSS data from <code>Component.get_css_data()</code></p>"},{"location":"reference/api/#django_components.OnComponentDataContext.js_data","title":"js_data  <code>instance-attribute</code>","text":"<pre><code>js_data: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of JavaScript data from <code>Component.get_js_data()</code></p>"},{"location":"reference/api/#django_components.OnComponentInputContext","title":"OnComponentInputContext","text":"<p>Attributes:</p> <ul> <li> <code>args</code>               (<code>List</code>)           \u2013            </li> <li> <code>component</code>               (<code>Component</code>)           \u2013            </li> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> <li> <code>component_id</code>               (<code>str</code>)           \u2013            </li> <li> <code>context</code>               (<code>Context</code>)           \u2013            </li> <li> <code>kwargs</code>               (<code>Dict</code>)           \u2013            </li> <li> <code>slots</code>               (<code>Dict</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentInputContext.args","title":"args  <code>instance-attribute</code>","text":"<pre><code>args: List\n</code></pre> <p>See source code</p> <p>List of positional arguments passed to the component</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.component","title":"component  <code>instance-attribute</code>","text":"<pre><code>component: Component\n</code></pre> <p>See source code</p> <p>The Component instance that received the input and is being rendered</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The Component class</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.component_id","title":"component_id  <code>instance-attribute</code>","text":"<pre><code>component_id: str\n</code></pre> <p>See source code</p> <p>The unique identifier for this component instance</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.context","title":"context  <code>instance-attribute</code>","text":"<pre><code>context: Context\n</code></pre> <p>See source code</p> <p>The Django template Context object</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.kwargs","title":"kwargs  <code>instance-attribute</code>","text":"<pre><code>kwargs: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of keyword arguments passed to the component</p>"},{"location":"reference/api/#django_components.OnComponentInputContext.slots","title":"slots  <code>instance-attribute</code>","text":"<pre><code>slots: Dict\n</code></pre> <p>See source code</p> <p>Dictionary of slot definitions</p>"},{"location":"reference/api/#django_components.OnComponentRegisteredContext","title":"OnComponentRegisteredContext","text":"<p>Attributes:</p> <ul> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>registry</code>               (<code>ComponentRegistry</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentRegisteredContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The registered Component class</p>"},{"location":"reference/api/#django_components.OnComponentRegisteredContext.name","title":"name  <code>instance-attribute</code>","text":"<pre><code>name: str\n</code></pre> <p>See source code</p> <p>The name the component was registered under</p>"},{"location":"reference/api/#django_components.OnComponentRegisteredContext.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry: ComponentRegistry\n</code></pre> <p>See source code</p> <p>The registry the component was registered to</p>"},{"location":"reference/api/#django_components.OnComponentUnregisteredContext","title":"OnComponentUnregisteredContext","text":"<p>Attributes:</p> <ul> <li> <code>component_cls</code>               (<code>Type[Component]</code>)           \u2013            </li> <li> <code>name</code>               (<code>str</code>)           \u2013            </li> <li> <code>registry</code>               (<code>ComponentRegistry</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnComponentUnregisteredContext.component_cls","title":"component_cls  <code>instance-attribute</code>","text":"<pre><code>component_cls: Type[Component]\n</code></pre> <p>See source code</p> <p>The unregistered Component class</p>"},{"location":"reference/api/#django_components.OnComponentUnregisteredContext.name","title":"name  <code>instance-attribute</code>","text":"<pre><code>name: str\n</code></pre> <p>See source code</p> <p>The name the component was registered under</p>"},{"location":"reference/api/#django_components.OnComponentUnregisteredContext.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry: ComponentRegistry\n</code></pre> <p>See source code</p> <p>The registry the component was unregistered from</p>"},{"location":"reference/api/#django_components.OnRegistryCreatedContext","title":"OnRegistryCreatedContext","text":"<p>Attributes:</p> <ul> <li> <code>registry</code>               (<code>ComponentRegistry</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnRegistryCreatedContext.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry: ComponentRegistry\n</code></pre> <p>See source code</p> <p>The created ComponentRegistry instance</p>"},{"location":"reference/api/#django_components.OnRegistryDeletedContext","title":"OnRegistryDeletedContext","text":"<p>Attributes:</p> <ul> <li> <code>registry</code>               (<code>ComponentRegistry</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.OnRegistryDeletedContext.registry","title":"registry  <code>instance-attribute</code>","text":"<pre><code>registry: ComponentRegistry\n</code></pre> <p>See source code</p> <p>The to-be-deleted ComponentRegistry instance</p>"},{"location":"reference/api/#django_components.RegistrySettings","title":"RegistrySettings","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>Configuration for a <code>ComponentRegistry</code>.</p> <p>These settings define how the components registered with this registry will behave when rendered.</p> <pre><code>from django_components import ComponentRegistry, RegistrySettings\n\nregistry_settings = RegistrySettings(\n    context_behavior=\"django\",\n    tag_formatter=\"django_components.component_shorthand_formatter\",\n)\n\nregistry = ComponentRegistry(settings=registry_settings)\n</code></pre> <p>Attributes:</p> <ul> <li> <code>CONTEXT_BEHAVIOR</code>               (<code>Optional[ContextBehaviorType]</code>)           \u2013            </li> <li> <code>TAG_FORMATTER</code>               (<code>Optional[Union[TagFormatterABC, str]]</code>)           \u2013            </li> <li> <code>context_behavior</code>               (<code>Optional[ContextBehaviorType]</code>)           \u2013            </li> <li> <code>tag_formatter</code>               (<code>Optional[Union[TagFormatterABC, str]]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.RegistrySettings.CONTEXT_BEHAVIOR","title":"CONTEXT_BEHAVIOR  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>CONTEXT_BEHAVIOR: Optional[ContextBehaviorType] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>context_behavior</code> instead. Will be removed in v1.</p> <p>Same as the global <code>COMPONENTS.context_behavior</code> setting, but for this registry.</p> <p>If omitted, defaults to the global <code>COMPONENTS.context_behavior</code> setting.</p>"},{"location":"reference/api/#django_components.RegistrySettings.TAG_FORMATTER","title":"TAG_FORMATTER  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>TAG_FORMATTER: Optional[Union[TagFormatterABC, str]] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>tag_formatter</code> instead. Will be removed in v1.</p> <p>Same as the global <code>COMPONENTS.tag_formatter</code> setting, but for this registry.</p> <p>If omitted, defaults to the global <code>COMPONENTS.tag_formatter</code> setting.</p>"},{"location":"reference/api/#django_components.RegistrySettings.context_behavior","title":"context_behavior  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>context_behavior: Optional[ContextBehaviorType] = None\n</code></pre> <p>See source code</p> <p>Same as the global <code>COMPONENTS.context_behavior</code> setting, but for this registry.</p> <p>If omitted, defaults to the global <code>COMPONENTS.context_behavior</code> setting.</p>"},{"location":"reference/api/#django_components.RegistrySettings.tag_formatter","title":"tag_formatter  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>tag_formatter: Optional[Union[TagFormatterABC, str]] = None\n</code></pre> <p>See source code</p> <p>Same as the global <code>COMPONENTS.tag_formatter</code> setting, but for this registry.</p> <p>If omitted, defaults to the global <code>COMPONENTS.tag_formatter</code> setting.</p>"},{"location":"reference/api/#django_components.Slot","title":"Slot  <code>dataclass</code>","text":"<pre><code>Slot(\n    content_func: SlotFunc[TSlotData],\n    escaped: bool = False,\n    component_name: Optional[str] = None,\n    slot_name: Optional[str] = None,\n    nodelist: Optional[NodeList] = None,\n)\n</code></pre> <p>Bases: <code>typing.Generic</code></p> <p>See source code</p> <p>This class holds the slot content function along with related metadata.</p> <p>Attributes:</p> <ul> <li> <code>component_name</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>content_func</code>               (<code>SlotFunc[TSlotData]</code>)           \u2013            </li> <li> <code>do_not_call_in_templates</code>               (<code>bool</code>)           \u2013            </li> <li> <code>escaped</code>               (<code>bool</code>)           \u2013            </li> <li> <code>nodelist</code>               (<code>Optional[NodeList]</code>)           \u2013            </li> <li> <code>slot_name</code>               (<code>Optional[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.Slot.component_name","title":"component_name  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>component_name: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the component that originally defined or accepted this slot fill.</p>"},{"location":"reference/api/#django_components.Slot.content_func","title":"content_func  <code>instance-attribute</code>","text":"<pre><code>content_func: SlotFunc[TSlotData]\n</code></pre>"},{"location":"reference/api/#django_components.Slot.do_not_call_in_templates","title":"do_not_call_in_templates  <code>property</code>","text":"<pre><code>do_not_call_in_templates: bool\n</code></pre>"},{"location":"reference/api/#django_components.Slot.escaped","title":"escaped  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>escaped: bool = False\n</code></pre> <p>See source code</p> <p>Whether the slot content has been escaped.</p>"},{"location":"reference/api/#django_components.Slot.nodelist","title":"nodelist  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>nodelist: Optional[NodeList] = None\n</code></pre> <p>See source code</p> <p>Nodelist of the slot content.</p>"},{"location":"reference/api/#django_components.Slot.slot_name","title":"slot_name  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>slot_name: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the slot that originally defined or accepted this slot fill.</p>"},{"location":"reference/api/#django_components.SlotContent","title":"SlotContent  <code>module-attribute</code>","text":"<pre><code>SlotContent = Union[SlotResult, SlotFunc[TSlotData], Slot[TSlotData]]\n</code></pre>"},{"location":"reference/api/#django_components.SlotFunc","title":"SlotFunc","text":""},{"location":"reference/api/#django_components.SlotRef","title":"SlotRef","text":"<pre><code>SlotRef(slot: SlotNode, context: Context)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>SlotRef allows to treat a slot as a variable. The slot is rendered only once the instance is coerced to string.</p> <p>This is used to access slots as variables inside the templates. When a SlotRef is rendered in the template with <code>{{ my_lazy_slot }}</code>, it will output the contents of the slot.</p>"},{"location":"reference/api/#django_components.SlotResult","title":"SlotResult  <code>module-attribute</code>","text":"<pre><code>SlotResult = Union[str, SafeString]\n</code></pre>"},{"location":"reference/api/#django_components.TagFormatterABC","title":"TagFormatterABC","text":"<p>Bases: <code>abc.ABC</code></p> <p>See source code</p> <p>Abstract base class for defining custom tag formatters.</p> <p>Tag formatters define how the component tags are used in the template.</p> <p>Read more about Tag formatter.</p> <p>For example, with the default tag formatter (<code>ComponentFormatter</code>), components are written as:</p> <pre><code>{% component \"comp_name\" %}\n{% endcomponent %}\n</code></pre> <p>While with the shorthand tag formatter (<code>ShorthandComponentFormatter</code>), components are written as: <pre><code>{% comp_name %}\n{% endcomp_name %}\n</code></pre></p> <p>Example:</p> <p>Implementation for <code>ShorthandComponentFormatter</code>:</p> <pre><code>from djagno_components import TagFormatterABC, TagResult\n\nclass ShorthandComponentFormatter(TagFormatterABC):\n    def start_tag(self, name: str) -&gt; str:\n        return name\n\n    def end_tag(self, name: str) -&gt; str:\n        return f\"end{name}\"\n\n    def parse(self, tokens: List[str]) -&gt; TagResult:\n        tokens = [*tokens]\n        name = tokens.pop(0)\n        return TagResult(name, tokens)\n</code></pre> <p>Methods:</p> <ul> <li> <code>end_tag</code>             \u2013              </li> <li> <code>parse</code>             \u2013              </li> <li> <code>start_tag</code>             \u2013              </li> </ul>"},{"location":"reference/api/#django_components.TagFormatterABC.end_tag","title":"end_tag  <code>abstractmethod</code>","text":"<pre><code>end_tag(name: str) -&gt; str\n</code></pre> <p>See source code</p> <p>Formats the end tag of a block component.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>Component's registered name. Required.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>str</code> (              <code>str</code> )          \u2013            <p>The formatted end tag.</p> </li> </ul>"},{"location":"reference/api/#django_components.TagFormatterABC.parse","title":"parse  <code>abstractmethod</code>","text":"<pre><code>parse(tokens: List[str]) -&gt; TagResult\n</code></pre> <p>See source code</p> <p>Given the tokens (words) passed to a component start tag, this function extracts the component name from the tokens list, and returns <code>TagResult</code>, which is a tuple of <code>(component_name, remaining_tokens)</code>.</p> <p>Parameters:</p> <ul> <li> <code>tokens</code>               (<code>[List(str]</code>)           \u2013            <p>List of tokens passed to the component tag.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>TagResult</code> (              <code>TagResult</code> )          \u2013            <p>Parsed component name and remaining tokens.</p> </li> </ul> <p>Example:</p> <p>Assuming we used a component in a template like this:</p> <pre><code>{% component \"my_comp\" key=val key2=val2 %}\n{% endcomponent %}\n</code></pre> <p>This function receives a list of tokens:</p> <pre><code>['component', '\"my_comp\"', 'key=val', 'key2=val2']\n</code></pre> <ul> <li><code>component</code> is the tag name, which we drop.</li> <li><code>\"my_comp\"</code> is the component name, but we must remove the extra quotes.</li> <li>The remaining tokens we pass unmodified, as that's the input to the component.</li> </ul> <p>So in the end, we return:</p> <pre><code>TagResult('my_comp', ['key=val', 'key2=val2'])\n</code></pre>"},{"location":"reference/api/#django_components.TagFormatterABC.start_tag","title":"start_tag  <code>abstractmethod</code>","text":"<pre><code>start_tag(name: str) -&gt; str\n</code></pre> <p>See source code</p> <p>Formats the start tag of a component.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>Component's registered name. Required.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>str</code> (              <code>str</code> )          \u2013            <p>The formatted start tag.</p> </li> </ul>"},{"location":"reference/api/#django_components.TagResult","title":"TagResult","text":"<p>Bases: <code>tuple</code></p> <p>See source code</p> <p>The return value from <code>TagFormatter.parse()</code>.</p> <p>Read more about Tag formatter.</p> <p>Attributes:</p> <ul> <li> <code>component_name</code>               (<code>str</code>)           \u2013            </li> <li> <code>tokens</code>               (<code>List[str]</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.TagResult.component_name","title":"component_name  <code>instance-attribute</code>","text":"<pre><code>component_name: str\n</code></pre> <p>See source code</p> <p>Component name extracted from the template tag</p> <p>For example, if we had tag</p> <pre><code>{% component \"my_comp\" key=val key2=val2 %}\n</code></pre> <p>Then <code>component_name</code> would be <code>my_comp</code>.</p>"},{"location":"reference/api/#django_components.TagResult.tokens","title":"tokens  <code>instance-attribute</code>","text":"<pre><code>tokens: List[str]\n</code></pre> <p>See source code</p> <p>Remaining tokens (words) that were passed to the tag, with component name removed</p> <p>For example, if we had tag</p> <pre><code>{% component \"my_comp\" key=val key2=val2 %}\n</code></pre> <p>Then <code>tokens</code> would be <code>['key=val', 'key2=val2']</code>.</p>"},{"location":"reference/api/#django_components.URLRoute","title":"URLRoute  <code>dataclass</code>","text":"<pre><code>URLRoute(\n    path: str,\n    handler: Optional[URLRouteHandler] = None,\n    children: List[URLRoute] = list(),\n    name: Optional[str] = None,\n    extra: Dict[str, Any] = dict(),\n)\n</code></pre> <p>Bases: <code>object</code></p> <p>See source code</p> <p>Framework-agnostic route definition.</p> <p>This is similar to Django's <code>URLPattern</code> object created with <code>django.urls.path()</code>.</p> <p>The <code>URLRoute</code> must either define a <code>handler</code> function or have a list of child routes <code>children</code>. If both are defined, an error will be raised.</p> <p>Example:</p> <pre><code>URLRoute(\"/my/path\", handler=my_handler, name=\"my_name\", extra={\"kwargs\": {\"my_extra\": \"my_value\"}})\n</code></pre> <p>Is equivalent to:</p> <pre><code>django.urls.path(\"/my/path\", my_handler, name=\"my_name\", kwargs={\"my_extra\": \"my_value\"})\n</code></pre> <p>With children:</p> <pre><code>URLRoute(\n    \"/my/path\",\n    name=\"my_name\",\n    extra={\"kwargs\": {\"my_extra\": \"my_value\"}},\n    children=[\n        URLRoute(\n            \"/child/&lt;str:name&gt;/\",\n            handler=my_handler,\n            name=\"my_name\",\n            extra={\"kwargs\": {\"my_extra\": \"my_value\"}},\n        ),\n        URLRoute(\"/other/&lt;int:id&gt;/\", handler=other_handler),\n    ],\n)\n</code></pre> <p>Attributes:</p> <ul> <li> <code>children</code>               (<code>List[URLRoute]</code>)           \u2013            </li> <li> <code>extra</code>               (<code>Dict[str, Any]</code>)           \u2013            </li> <li> <code>handler</code>               (<code>Optional[URLRouteHandler]</code>)           \u2013            </li> <li> <code>name</code>               (<code>Optional[str]</code>)           \u2013            </li> <li> <code>path</code>               (<code>str</code>)           \u2013            </li> </ul>"},{"location":"reference/api/#django_components.URLRoute.children","title":"children  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>children: List[URLRoute] = field(default_factory=list)\n</code></pre>"},{"location":"reference/api/#django_components.URLRoute.extra","title":"extra  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>extra: Dict[str, Any] = field(default_factory=dict)\n</code></pre>"},{"location":"reference/api/#django_components.URLRoute.handler","title":"handler  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>handler: Optional[URLRouteHandler] = None\n</code></pre>"},{"location":"reference/api/#django_components.URLRoute.name","title":"name  <code>class-attribute</code> <code>instance-attribute</code>","text":"<pre><code>name: Optional[str] = None\n</code></pre>"},{"location":"reference/api/#django_components.URLRoute.path","title":"path  <code>instance-attribute</code>","text":"<pre><code>path: str\n</code></pre>"},{"location":"reference/api/#django_components.URLRouteHandler","title":"URLRouteHandler","text":"<p>Bases: <code>typing.Protocol</code></p> <p>See source code</p> <p>Framework-agnostic 'view' function for routes</p>"},{"location":"reference/api/#django_components.all_components","title":"all_components","text":"<pre><code>all_components() -&gt; List[Type[Component]]\n</code></pre> <p>See source code</p> <p>Get a list of all created <code>Component</code> classes.</p>"},{"location":"reference/api/#django_components.all_registries","title":"all_registries","text":"<pre><code>all_registries() -&gt; List[ComponentRegistry]\n</code></pre> <p>See source code</p> <p>Get a list of all created <code>ComponentRegistry</code> instances.</p>"},{"location":"reference/api/#django_components.autodiscover","title":"autodiscover","text":"<pre><code>autodiscover(map_module: Optional[Callable[[str], str]] = None) -&gt; List[str]\n</code></pre> <p>See source code</p> <p>Search for all python files in <code>COMPONENTS.dirs</code> and <code>COMPONENTS.app_dirs</code> and import them.</p> <p>See Autodiscovery.</p> <p>NOTE: Subdirectories and files starting with an underscore <code>_</code> (except for <code>__init__.py</code> are ignored.</p> <p>Parameters:</p> <ul> <li> <code>map_module</code>               (<code>Callable[[str], str]</code>, default:                   <code>None</code> )           \u2013            <p>Map the module paths with <code>map_module</code> function.        This serves as an escape hatch for when you need to use this function in tests.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>List[str]</code>           \u2013            <p>List[str]: A list of module paths of imported files.</p> </li> </ul> <p>To get the same list of modules that <code>autodiscover()</code> would return, but without importing them, use <code>get_component_files()</code>:</p> <pre><code>from django_components import get_component_files\n\nmodules = get_component_files(\".py\")\n</code></pre>"},{"location":"reference/api/#django_components.cached_template","title":"cached_template","text":"<pre><code>cached_template(\n    template_string: str,\n    template_cls: Optional[Type[Template]] = None,\n    origin: Optional[Origin] = None,\n    name: Optional[str] = None,\n    engine: Optional[Any] = None,\n) -&gt; Template\n</code></pre> <p>See source code</p> <p>Create a Template instance that will be cached as per the <code>COMPONENTS.template_cache_size</code> setting.</p> <p>Parameters:</p> <ul> <li> <code>template_string</code>               (<code>str</code>)           \u2013            <p>Template as a string, same as the first argument to Django's            <code>Template</code>. Required.</p> </li> <li> <code>template_cls</code>               (<code>Type[Template]</code>, default:                   <code>None</code> )           \u2013            <p>Specify the Template class that should be instantiated.            Defaults to Django's <code>Template</code> class.</p> </li> <li> <code>origin</code>               (<code>Type[Origin]</code>, default:                   <code>None</code> )           \u2013            <p>Sets             <code>Template.Origin</code>.</p> </li> <li> <code>name</code>               (<code>Type[str]</code>, default:                   <code>None</code> )           \u2013            <p>Sets <code>Template.name</code></p> </li> <li> <code>engine</code>               (<code>Type[Any]</code>, default:                   <code>None</code> )           \u2013            <p>Sets <code>Template.engine</code></p> </li> </ul> <pre><code>from django_components import cached_template\n\ntemplate = cached_template(\"Variable: {{ variable }}\")\n\n# You can optionally specify Template class, and other Template inputs:\nclass MyTemplate(Template):\n    pass\n\ntemplate = cached_template(\n    \"Variable: {{ variable }}\",\n    template_cls=MyTemplate,\n    name=...\n    origin=...\n    engine=...\n)\n</code></pre>"},{"location":"reference/api/#django_components.get_component_dirs","title":"get_component_dirs","text":"<pre><code>get_component_dirs(include_apps: bool = True) -&gt; List[Path]\n</code></pre> <p>See source code</p> <p>Get directories that may contain component files.</p> <p>This is the heart of all features that deal with filesystem and file lookup. Autodiscovery, Django template resolution, static file resolution - They all use this.</p> <p>Parameters:</p> <ul> <li> <code>include_apps</code>               (<code>bool</code>, default:                   <code>True</code> )           \u2013            <p>Include directories from installed Django apps.            Defaults to <code>True</code>.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>List[Path]</code>           \u2013            <p>List[Path]: A list of directories that may contain component files.</p> </li> </ul> <p><code>get_component_dirs()</code> searches for dirs set in <code>COMPONENTS.dirs</code> settings. If none set, defaults to searching for a <code>\"components\"</code> app.</p> <p>In addition to that, also all installed Django apps are checked whether they contain directories as set in <code>COMPONENTS.app_dirs</code> (e.g. <code>[app]/components</code>).</p> <p>Notes:</p> <ul> <li> <p>Paths that do not point to directories are ignored.</p> </li> <li> <p><code>BASE_DIR</code> setting is required.</p> </li> <li> <p>The paths in <code>COMPONENTS.dirs</code>     must be absolute paths.</p> </li> </ul>"},{"location":"reference/api/#django_components.get_component_files","title":"get_component_files","text":"<pre><code>get_component_files(suffix: Optional[str] = None) -&gt; List[ComponentFileEntry]\n</code></pre> <p>See source code</p> <p>Search for files within the component directories (as defined in <code>get_component_dirs()</code>).</p> <p>Requires <code>BASE_DIR</code> setting to be set.</p> <p>Subdirectories and files starting with an underscore <code>_</code> (except <code>__init__.py</code>) are ignored.</p> <p>Parameters:</p> <ul> <li> <code>suffix</code>               (<code>Optional[str]</code>, default:                   <code>None</code> )           \u2013            <p>The suffix to search for. E.g. <code>.py</code>, <code>.js</code>, <code>.css</code>.            Defaults to <code>None</code>, which will search for all files.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>List[ComponentFileEntry]</code>           \u2013            <p>List[ComponentFileEntry] A list of entries that contain both the filesystem path and             the python import path (dot path).</p> </li> </ul> <p>Example:</p> <pre><code>from django_components import get_component_files\n\nmodules = get_component_files(\".py\")\n</code></pre>"},{"location":"reference/api/#django_components.import_libraries","title":"import_libraries","text":"<pre><code>import_libraries(map_module: Optional[Callable[[str], str]] = None) -&gt; List[str]\n</code></pre> <p>See source code</p> <p>Import modules set in <code>COMPONENTS.libraries</code> setting.</p> <p>See Autodiscovery.</p> <p>Parameters:</p> <ul> <li> <code>map_module</code>               (<code>Callable[[str], str]</code>, default:                   <code>None</code> )           \u2013            <p>Map the module paths with <code>map_module</code> function.        This serves as an escape hatch for when you need to use this function in tests.</p> </li> </ul> <p>Returns:</p> <ul> <li> <code>List[str]</code>           \u2013            <p>List[str]: A list of module paths of imported files.</p> </li> </ul> <p>Examples:</p> <p>Normal usage - load libraries after Django has loaded <pre><code>from django_components import import_libraries\n\nclass MyAppConfig(AppConfig):\n    def ready(self):\n        import_libraries()\n</code></pre></p> <p>Potential usage in tests <pre><code>from django_components import import_libraries\n\nimport_libraries(lambda path: path.replace(\"tests.\", \"myapp.\"))\n</code></pre></p>"},{"location":"reference/api/#django_components.register","title":"register","text":"<pre><code>register(name: str, registry: Optional[ComponentRegistry] = None) -&gt; Callable[\n    [Type[Component[ArgsType, KwargsType, SlotsType, DataType, JsDataType, CssDataType]]],\n    Type[Component[ArgsType, KwargsType, SlotsType, DataType, JsDataType, CssDataType]],\n]\n</code></pre> <p>See source code</p> <p>Class decorator for registering a component to a component registry.</p> <p>See Registering components.</p> <p>Parameters:</p> <ul> <li> <code>name</code>               (<code>str</code>)           \u2013            <p>Registered name. This is the name by which the component will be accessed            from within a template when using the <code>{% component %}</code> tag. Required.</p> </li> <li> <code>registry</code>               (<code>ComponentRegistry</code>, default:                   <code>None</code> )           \u2013            <p>Specify the registry            to which to register this component. If omitted, component is registered to the default registry.</p> </li> </ul> <p>Raises:</p> <ul> <li> <code>AlreadyRegistered</code>             \u2013            <p>If there is already a component registered under the same name.</p> </li> </ul> <p>Examples:</p> <pre><code>from django_components import Component, register\n\n@register(\"my_component\")\nclass MyComponent(Component):\n    ...\n</code></pre> <p>Specifing <code>ComponentRegistry</code> the component should be registered to by setting the <code>registry</code> kwarg:</p> <pre><code>from django.template import Library\nfrom django_components import Component, ComponentRegistry, register\n\nmy_lib = Library()\nmy_reg = ComponentRegistry(library=my_lib)\n\n@register(\"my_component\", registry=my_reg)\nclass MyComponent(Component):\n    ...\n</code></pre>"},{"location":"reference/api/#django_components.registry","title":"registry  <code>module-attribute</code>","text":"<pre><code>registry: ComponentRegistry = ComponentRegistry()\n</code></pre> <p>See source code</p> <p>The default and global component registry. Use this instance to directly register or remove components:</p> <p>See Registering components.</p> <pre><code># Register components\nregistry.register(\"button\", ButtonComponent)\nregistry.register(\"card\", CardComponent)\n\n# Get single\nregistry.get(\"button\")\n\n# Get all\nregistry.all()\n\n# Check if component is registered\nregistry.has(\"button\")\n\n# Unregister single\nregistry.unregister(\"button\")\n\n# Unregister all\nregistry.clear()\n</code></pre>"},{"location":"reference/api/#django_components.render_dependencies","title":"render_dependencies","text":"<pre><code>render_dependencies(content: TContent, type: RenderType = 'document') -&gt; TContent\n</code></pre> <p>See source code</p> <p>Given a string that contains parts that were rendered by components, this function inserts all used JS and CSS.</p> <p>By default, the string is parsed as an HTML and: - CSS is inserted at the end of <code>&lt;head&gt;</code> (if present) - JS is inserted at the end of <code>&lt;body&gt;</code> (if present)</p> <p>If you used <code>{% component_js_dependencies %}</code> or <code>{% component_css_dependencies %}</code>, then the JS and CSS will be inserted only at these locations.</p> <p>Example: <pre><code>def my_view(request):\n    template = Template('''\n        {% load components %}\n        &lt;!doctype html&gt;\n        &lt;html&gt;\n            &lt;head&gt;&lt;/head&gt;\n            &lt;body&gt;\n                &lt;h1&gt;{{ table_name }}&lt;/h1&gt;\n                {% component \"table\" name=table_name / %}\n            &lt;/body&gt;\n        &lt;/html&gt;\n    ''')\n\n    html = template.render(\n        Context({\n            \"table_name\": request.GET[\"name\"],\n        })\n    )\n\n    # This inserts components' JS and CSS\n    processed_html = render_dependencies(html)\n\n    return HttpResponse(processed_html)\n</code></pre></p>"},{"location":"reference/api/#django_components.template_tag","title":"template_tag","text":"<pre><code>template_tag(\n    library: Library, tag: str, end_tag: Optional[str] = None, allowed_flags: Optional[List[str]] = None\n) -&gt; Callable[[Callable], Callable]\n</code></pre> <p>See source code</p> <p>A simplified version of creating a template tag based on <code>BaseNode</code>.</p> <p>Instead of defining the whole class, you can just define the <code>render()</code> method.</p> <pre><code>from django.template import Context, Library\nfrom django_components import BaseNode, template_tag\n\nlibrary = Library()\n\n@template_tag(\n    library,\n    tag=\"mytag\",\n    end_tag=\"endmytag\",\n    allowed_flags=[\"required\"],\n)\ndef mytag(node: BaseNode, context: Context, name: str, **kwargs: Any) -&gt; str:\n    return f\"Hello, {name}!\"\n</code></pre> <p>This will allow the template tag <code>{% mytag %}</code> to be used like this:</p> <pre><code>{% mytag name=\"John\" %}\n{% mytag name=\"John\" required %} ... {% endmytag %}\n</code></pre> <p>The given function will be wrapped in a class that inherits from <code>BaseNode</code>.</p> <p>And this class will be registered with the given library.</p> <p>The function MUST accept at least two positional arguments: <code>node</code> and <code>context</code></p> <ul> <li><code>node</code> is the <code>BaseNode</code> instance.</li> <li><code>context</code> is the <code>Context</code>     of the template.</li> </ul> <p>Any extra parameters defined on this function will be part of the tag's input parameters.</p> <p>For more info, see <code>BaseNode.render()</code>.</p>"},{"location":"reference/commands/","title":"Commands","text":""},{"location":"reference/commands/#commands","title":"Commands","text":"<p>These are all the Django management commands that will be added by installing <code>django_components</code>:</p>"},{"location":"reference/commands/#components","title":"<code>components</code>","text":"<pre><code>usage: python manage.py  components [-h] {create,upgrade,ext,list} ...\n</code></pre> <p>See source code</p> <p>The entrypoint for the 'components' commands.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> </ul> <p>Subcommands:</p> <ul> <li><code>create</code><ul> <li>Create a new django component.</li> </ul> </li> <li><code>upgrade</code><ul> <li>Upgrade django components syntax from '{% component_block ... %}' to '{% component ... %}'.</li> </ul> </li> <li><code>ext</code><ul> <li>Run extension commands.</li> </ul> </li> <li><code>list</code><ul> <li>List all components created in this project.</li> </ul> </li> </ul> <p>The entrypoint for the \"components\" commands.</p> <pre><code>python manage.py components list\npython manage.py components create &lt;name&gt;\npython manage.py components upgrade\npython manage.py components ext list\npython manage.py components ext run &lt;extension&gt; &lt;command&gt;\n</code></pre>"},{"location":"reference/commands/#components-create","title":"<code>components create</code>","text":"<pre><code>usage: python manage.py components create [-h] [--path PATH] [--js JS] [--css CSS] [--template TEMPLATE]\n              [--force] [--verbose] [--dry-run]\n              name\n</code></pre> <p>See source code</p> <p>Create a new django component.</p> <p>Positional Arguments:</p> <ul> <li><code>name</code><ul> <li>The name of the component to create. This is a required argument.</li> </ul> </li> </ul> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--path PATH</code><ul> <li>The path to the component's directory. This is an optional argument. If not provided, the command will use the <code>COMPONENTS.dirs</code> setting from your Django settings.</li> </ul> </li> <li><code>--js JS</code><ul> <li>The name of the JavaScript file. This is an optional argument. The default value is <code>script.js</code>.</li> </ul> </li> <li><code>--css CSS</code><ul> <li>The name of the CSS file. This is an optional argument. The default value is <code>style.css</code>.</li> </ul> </li> <li><code>--template TEMPLATE</code><ul> <li>The name of the template file. This is an optional argument. The default value is <code>template.html</code>.</li> </ul> </li> <li><code>--force</code><ul> <li>This option allows you to overwrite existing files if they exist. This is an optional argument.</li> </ul> </li> <li><code>--verbose</code><ul> <li>This option allows the command to print additional information during component creation. This is an optional argument.</li> </ul> </li> <li><code>--dry-run</code><ul> <li>This option allows you to simulate component creation without actually creating any files. This is an optional argument. The default value is <code>False</code>.</li> </ul> </li> </ul>"},{"location":"reference/commands/#usage","title":"Usage","text":"<p>To use the command, run the following command in your terminal:</p> <pre><code>python manage.py components create &lt;name&gt; --path &lt;path&gt; --js &lt;js_filename&gt; --css &lt;css_filename&gt; --template &lt;template_filename&gt; --force --verbose --dry-run\n</code></pre> <p>Replace <code>&lt;name&gt;</code>, <code>&lt;path&gt;</code>, <code>&lt;js_filename&gt;</code>, <code>&lt;css_filename&gt;</code>, and <code>&lt;template_filename&gt;</code> with your desired values.</p>"},{"location":"reference/commands/#examples","title":"Examples","text":"<p>Here are some examples of how you can use the command:</p> <p>Creating a Component with Default Settings</p> <p>To create a component with the default settings, you only need to provide the name of the component:</p> <pre><code>python manage.py components create my_component\n</code></pre> <p>This will create a new component named <code>my_component</code> in the <code>components</code> directory of your Django project. The JavaScript, CSS, and template files will be named <code>script.js</code>, <code>style.css</code>, and <code>template.html</code>, respectively.</p> <p>Creating a Component with Custom Settings</p> <p>You can also create a component with custom settings by providing additional arguments:</p> <pre><code>python manage.py components create new_component --path my_components --js my_script.js --css my_style.css --template my_template.html\n</code></pre> <p>This will create a new component named <code>new_component</code> in the <code>my_components</code> directory. The JavaScript, CSS, and template files will be named <code>my_script.js</code>, <code>my_style.css</code>, and <code>my_template.html</code>, respectively.</p> <p>Overwriting an Existing Component</p> <p>If you want to overwrite an existing component, you can use the <code>--force</code> option:</p> <pre><code>python manage.py components create my_component --force\n</code></pre> <p>This will overwrite the existing <code>my_component</code> if it exists.</p> <p>Simulating Component Creation</p> <p>If you want to simulate the creation of a component without actually creating any files, you can use the <code>--dry-run</code> option:</p> <pre><code>python manage.py components create my_component --dry-run\n</code></pre> <p>This will simulate the creation of <code>my_component</code> without creating any files.</p>"},{"location":"reference/commands/#components-upgrade","title":"<code>components upgrade</code>","text":"<pre><code>usage: python manage.py components upgrade [-h] [--path PATH]\n</code></pre> <p>See source code</p> <p>Upgrade django components syntax from '{% component_block ... %}' to '{% component ... %}'.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--path PATH</code><ul> <li>Path to search for components</li> </ul> </li> </ul>"},{"location":"reference/commands/#components-ext","title":"<code>components ext</code>","text":"<pre><code>usage: python manage.py components ext [-h] {list,run} ...\n</code></pre> <p>See source code</p> <p>Run extension commands.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> </ul> <p>Subcommands:</p> <ul> <li><code>list</code><ul> <li>List all extensions.</li> </ul> </li> <li><code>run</code><ul> <li>Run a command added by an extension.</li> </ul> </li> </ul> <p>Run extension commands.</p> <pre><code>python manage.py components ext list\npython manage.py components ext run &lt;extension&gt; &lt;command&gt;\n</code></pre>"},{"location":"reference/commands/#components-ext-list","title":"<code>components ext list</code>","text":"<pre><code>usage: python manage.py components ext list [-h] [--all] [--columns COLUMNS] [-s]\n</code></pre> <p>See source code</p> <p>List all extensions.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--all</code><ul> <li>Show all columns. Same as <code>--columns name</code>.</li> </ul> </li> <li><code>--columns COLUMNS</code><ul> <li>Comma-separated list of columns to show. Available columns: name. Defaults to <code>--columns name</code>.</li> </ul> </li> <li><code>-s</code>, <code>--simple</code><ul> <li>Only show table data, without headers. Use this option for generating machine-readable output.</li> </ul> </li> </ul> <p>List all extensions.</p> <pre><code>python manage.py components ext list\n</code></pre> <p>Prints the list of installed extensions:</p> <pre><code>name\n==============\nview\nmy_extension\n</code></pre> <p>To specify which columns to show, use the <code>--columns</code> flag:</p> <pre><code>python manage.py components ext list --columns name\n</code></pre> <p>Which prints:</p> <pre><code>name\n==============\nview\nmy_extension\n</code></pre> <p>To print out all columns, use the <code>--all</code> flag:</p> <pre><code>python manage.py components ext list --all\n</code></pre> <p>If you need to omit the title in order to programmatically post-process the output, you can use the <code>--simple</code> (or <code>-s</code>) flag:</p> <pre><code>python manage.py components ext list --simple\n</code></pre> <p>Which prints just:</p> <pre><code>view\nmy_extension\n</code></pre>"},{"location":"reference/commands/#components-ext-run","title":"<code>components ext run</code>","text":"<pre><code>usage: python manage.py components ext run [-h]\n</code></pre> <p>See source code</p> <p>Run a command added by an extension.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> </ul> <p>Run a command added by an extension.</p> <p>Each extension can add its own commands, which will be available to run with this command.</p> <p>For example, if you define and install the following extension:</p> <pre><code>from django_components import ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n    def handle(self, *args, **kwargs):\n        print(\"Hello, world!\")\n\nclass MyExt(ComponentExtension):\n    name = \"my_ext\"\n    commands = [HelloCommand]\n</code></pre> <p>You can run the <code>hello</code> command with:</p> <pre><code>python manage.py components ext run my_ext hello\n</code></pre> <p>You can also define arguments for the command, which will be passed to the command's <code>handle</code> method.</p> <pre><code>from django_components import CommandArg, ComponentCommand, ComponentExtension\n\nclass HelloCommand(ComponentCommand):\n    name = \"hello\"\n    help = \"Say hello\"\n    arguments = [\n        CommandArg(name=\"name\", help=\"The name to say hello to\"),\n        CommandArg(name=[\"--shout\", \"-s\"], action=\"store_true\"),\n    ]\n\n    def handle(self, name: str, *args, **kwargs):\n        shout = kwargs.get(\"shout\", False)\n        msg = f\"Hello, {name}!\"\n        if shout:\n            msg = msg.upper()\n        print(msg)\n</code></pre> <p>You can run the command with:</p> <pre><code>python manage.py components ext run my_ext hello --name John --shout\n</code></pre> <p>Note</p> <p>Command arguments and options are based on Python's <code>argparse</code> module.</p> <p>For more information, see the argparse documentation.</p>"},{"location":"reference/commands/#components-list","title":"<code>components list</code>","text":"<pre><code>usage: python manage.py components list [-h] [--all] [--columns COLUMNS] [-s]\n</code></pre> <p>See source code</p> <p>List all components created in this project.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--all</code><ul> <li>Show all columns. Same as <code>--columns name,full_name,path</code>.</li> </ul> </li> <li><code>--columns COLUMNS</code><ul> <li>Comma-separated list of columns to show. Available columns: name, full_name, path. Defaults to <code>--columns full_name,path</code>.</li> </ul> </li> <li><code>-s</code>, <code>--simple</code><ul> <li>Only show table data, without headers. Use this option for generating machine-readable output.</li> </ul> </li> </ul> <p>List all components.</p> <pre><code>python manage.py components list\n</code></pre> <p>Prints the list of available components:</p> <pre><code>full_name                                                     path\n==================================================================================================\nproject.pages.project.ProjectPage                             ./project/pages/project\nproject.components.dashboard.ProjectDashboard                 ./project/components/dashboard\nproject.components.dashboard_action.ProjectDashboardAction    ./project/components/dashboard_action\n</code></pre> <p>To specify which columns to show, use the <code>--columns</code> flag:</p> <pre><code>python manage.py components list --columns name,full_name,path\n</code></pre> <p>Which prints:</p> <pre><code>name                      full_name                                                     path\n==================================================================================================\nProjectPage               project.pages.project.ProjectPage                             ./project/pages/project\nProjectDashboard          project.components.dashboard.ProjectDashboard                 ./project/components/dashboard\nProjectDashboardAction    project.components.dashboard_action.ProjectDashboardAction    ./project/components/dashboard_action\n</code></pre> <p>To print out all columns, use the <code>--all</code> flag:</p> <pre><code>python manage.py components list --all\n</code></pre> <p>If you need to omit the title in order to programmatically post-process the output, you can use the <code>--simple</code> (or <code>-s</code>) flag:</p> <pre><code>python manage.py components list --simple\n</code></pre> <p>Which prints just:</p> <pre><code>ProjectPage               project.pages.project.ProjectPage                             ./project/pages/project\nProjectDashboard          project.components.dashboard.ProjectDashboard                 ./project/components/dashboard\nProjectDashboardAction    project.components.dashboard_action.ProjectDashboardAction    ./project/components/dashboard_action\n</code></pre>"},{"location":"reference/commands/#upgradecomponent","title":"<code>upgradecomponent</code>","text":"<pre><code>usage: upgradecomponent [-h] [--path PATH] [--version] [-v {0,1,2,3}]\n                        [--settings SETTINGS] [--pythonpath PYTHONPATH]\n                        [--traceback] [--no-color] [--force-color]\n                        [--skip-checks]\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>components upgrade</code> instead.</p> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--path PATH</code><ul> <li>Path to search for components</li> </ul> </li> <li><code>--version</code><ul> <li>Show program's version number and exit.</li> </ul> </li> <li><code>-v</code>, <code>--verbosity {0,1,2,3}</code><ul> <li>Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output</li> </ul> </li> <li><code>--settings SETTINGS</code><ul> <li>The Python path to a settings module, e.g. \"myproject.settings.main\". If this isn't provided, the DJANGO_SETTINGS_MODULE environment variable will be used.</li> </ul> </li> <li><code>--pythonpath PYTHONPATH</code><ul> <li>A directory to add to the Python path, e.g. \"/home/djangoprojects/myproject\".</li> </ul> </li> <li><code>--traceback</code><ul> <li>Raise on CommandError exceptions.</li> </ul> </li> <li><code>--no-color</code><ul> <li>Don't colorize the command output.</li> </ul> </li> <li><code>--force-color</code><ul> <li>Force colorization of the command output.</li> </ul> </li> <li><code>--skip-checks</code><ul> <li>Skip system checks.</li> </ul> </li> </ul> <p>Deprecated. Use <code>components upgrade</code> instead.</p>"},{"location":"reference/commands/#startcomponent","title":"<code>startcomponent</code>","text":"<pre><code>usage: startcomponent [-h] [--path PATH] [--js JS] [--css CSS]\n                      [--template TEMPLATE] [--force] [--verbose] [--dry-run]\n                      [--version] [-v {0,1,2,3}] [--settings SETTINGS]\n                      [--pythonpath PYTHONPATH] [--traceback] [--no-color]\n                      [--force-color] [--skip-checks]\n                      name\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>components create</code> instead.</p> <p>Positional Arguments:</p> <ul> <li><code>name</code><ul> <li>The name of the component to create. This is a required argument.</li> </ul> </li> </ul> <p>Options:</p> <ul> <li><code>-h</code>, <code>--help</code><ul> <li>show this help message and exit</li> </ul> </li> <li><code>--path PATH</code><ul> <li>The path to the component's directory. This is an optional argument. If not provided, the command will use the <code>COMPONENTS.dirs</code> setting from your Django settings.</li> </ul> </li> <li><code>--js JS</code><ul> <li>The name of the JavaScript file. This is an optional argument. The default value is <code>script.js</code>.</li> </ul> </li> <li><code>--css CSS</code><ul> <li>The name of the CSS file. This is an optional argument. The default value is <code>style.css</code>.</li> </ul> </li> <li><code>--template TEMPLATE</code><ul> <li>The name of the template file. This is an optional argument. The default value is <code>template.html</code>.</li> </ul> </li> <li><code>--force</code><ul> <li>This option allows you to overwrite existing files if they exist. This is an optional argument.</li> </ul> </li> <li><code>--verbose</code><ul> <li>This option allows the command to print additional information during component creation. This is an optional argument.</li> </ul> </li> <li><code>--dry-run</code><ul> <li>This option allows you to simulate component creation without actually creating any files. This is an optional argument. The default value is <code>False</code>.</li> </ul> </li> <li><code>--version</code><ul> <li>Show program's version number and exit.</li> </ul> </li> <li><code>-v</code>, <code>--verbosity {0,1,2,3}</code><ul> <li>Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output</li> </ul> </li> <li><code>--settings SETTINGS</code><ul> <li>The Python path to a settings module, e.g. \"myproject.settings.main\". If this isn't provided, the DJANGO_SETTINGS_MODULE environment variable will be used.</li> </ul> </li> <li><code>--pythonpath PYTHONPATH</code><ul> <li>A directory to add to the Python path, e.g. \"/home/djangoprojects/myproject\".</li> </ul> </li> <li><code>--traceback</code><ul> <li>Raise on CommandError exceptions.</li> </ul> </li> <li><code>--no-color</code><ul> <li>Don't colorize the command output.</li> </ul> </li> <li><code>--force-color</code><ul> <li>Force colorization of the command output.</li> </ul> </li> <li><code>--skip-checks</code><ul> <li>Skip system checks.</li> </ul> </li> </ul> <p>Deprecated. Use <code>components create</code> instead.</p>"},{"location":"reference/components/","title":"Components","text":""},{"location":"reference/components/#components","title":"Components","text":"<p>These are the components provided by django_components.</p>"},{"location":"reference/components/#django_components.components.dynamic.DynamicComponent","title":"<code>DynamicComponent</code>","text":"<p>Bases: <code>django_components.component.Component</code></p> <p>See source code</p> <p>This component is given a registered name or a reference to another component, and behaves as if the other component was in its place.</p> <p>The args, kwargs, and slot fills are all passed down to the underlying component.</p> <p>Parameters:</p> <ul> <li> <code>is</code>               (<code>str | Type[Component]</code>)           \u2013            <p>Component that should be rendered. Either a registered name of a component, or a Component class directly. Required.</p> </li> <li> <code>registry</code>               (<code>ComponentRegistry</code>, default:                   <code>None</code> )           \u2013            <p>Specify the registry            to search for the registered name. If omitted, all registries are searched until the first match.</p> </li> <li> <code>*args</code>           \u2013            <p>Additional data passed to the component.</p> </li> <li> <code>**kwargs</code>           \u2013            <p>Additional data passed to the component.</p> </li> </ul> <p>Slots:</p> <ul> <li>Any slots, depending on the actual component.</li> </ul> <p>Examples:</p> <p>Django <pre><code>{% component \"dynamic\" is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre></p> <p>Or in case you use the <code>django_components.component_shorthand_formatter</code> tag formatter:</p> <pre><code>{% dynamic is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% enddynamic %}\n</code></pre> <p>Python <pre><code>from django_components import DynamicComponent\n\nDynamicComponent.render(\n    kwargs={\n        \"is\": table_comp,\n        \"data\": table_data,\n        \"headers\": table_headers,\n    },\n    slots={\n        \"pagination\": PaginationComponent.render(\n            render_dependencies=False,\n        ),\n    },\n)\n</code></pre></p>"},{"location":"reference/components/#django_components.components.dynamic.DynamicComponent--use-cases","title":"Use cases","text":"<p>Dynamic components are suitable if you are writing something like a form component. You may design it such that users give you a list of input types, and you render components depending on the input types.</p> <p>While you could handle this with a series of if / else statements, that's not an extensible approach. Instead, you can use the dynamic component in place of normal components.</p>"},{"location":"reference/components/#django_components.components.dynamic.DynamicComponent--component-name","title":"Component name","text":"<p>By default, the dynamic component is registered under the name <code>\"dynamic\"</code>. In case of a conflict, you can set the <code>COMPONENTS.dynamic_component_name</code> setting to change the name used for the dynamic components.</p> <pre><code># settings.py\nCOMPONENTS = ComponentsSettings(\n    dynamic_component_name=\"my_dynamic\",\n)\n</code></pre> <p>After which you will be able to use the dynamic component with the new name: <pre><code>{% component \"my_dynamic\" is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre></p>"},{"location":"reference/exceptions/","title":"Exceptions","text":""},{"location":"reference/exceptions/#exceptions","title":"Exceptions","text":""},{"location":"reference/exceptions/#django_components.AlreadyRegistered","title":"AlreadyRegistered","text":"<p>Bases: <code>Exception</code></p> <p>See source code</p> <p>Raised when you try to register a Component, but it's already registered with given ComponentRegistry.</p>"},{"location":"reference/exceptions/#django_components.NotRegistered","title":"NotRegistered","text":"<p>Bases: <code>Exception</code></p> <p>See source code</p> <p>Raised when you try to access a Component, but it's NOT registered with given ComponentRegistry.</p>"},{"location":"reference/exceptions/#django_components.TagProtectedError","title":"TagProtectedError","text":"<p>Bases: <code>Exception</code></p> <p>See source code</p> <p>The way the <code>TagFormatter</code> works is that, based on which start and end tags are used for rendering components, the <code>ComponentRegistry</code> behind the scenes un-/registers the template tags with the associated instance of Django's <code>Library</code>.</p> <p>In other words, if I have registered a component <code>\"table\"</code>, and I use the shorthand syntax:</p> <pre><code>{% table ... %}\n{% endtable %}\n</code></pre> <p>Then <code>ComponentRegistry</code> registers the tag <code>table</code> onto the Django's Library instance.</p> <p>However, that means that if we registered a component <code>\"slot\"</code>, then we would overwrite the <code>{% slot %}</code> tag from django_components.</p> <p>Thus, this exception is raised when a component is attempted to be registered under a forbidden name, such that it would overwrite one of django_component's own template tags.</p>"},{"location":"reference/extension_hooks/","title":"Extension hooks","text":""},{"location":"reference/extension_hooks/#extension-hooks","title":"Extension Hooks","text":"<p>Overview of all the extension hooks available in Django Components.</p> <p>Read more on Extensions.</p> <p>Available data:</p> name type description <code>component_cls</code> <code>Type[Component]</code> The created Component class <p>Available data:</p> name type description <code>component_cls</code> <code>Type[Component]</code> The to-be-deleted Component class <p>Available data:</p> name type description <code>component</code> <code>Component</code> The Component instance that is being rendered <code>component_cls</code> <code>Type[Component]</code> The Component class <code>component_id</code> <code>str</code> The unique identifier for this component instance <code>context_data</code> <code>Dict</code> Dictionary of context data from <code>Component.get_context_data()</code> <code>css_data</code> <code>Dict</code> Dictionary of CSS data from <code>Component.get_css_data()</code> <code>js_data</code> <code>Dict</code> Dictionary of JavaScript data from <code>Component.get_js_data()</code> <p>Available data:</p> name type description <code>args</code> <code>List</code> List of positional arguments passed to the component <code>component</code> <code>Component</code> The Component instance that received the input and is being rendered <code>component_cls</code> <code>Type[Component]</code> The Component class <code>component_id</code> <code>str</code> The unique identifier for this component instance <code>context</code> <code>Context</code> The Django template Context object <code>kwargs</code> <code>Dict</code> Dictionary of keyword arguments passed to the component <code>slots</code> <code>Dict</code> Dictionary of slot definitions <p>Available data:</p> name type description <code>component_cls</code> <code>Type[Component]</code> The registered Component class <code>name</code> <code>str</code> The name the component was registered under <code>registry</code> <code>ComponentRegistry</code> The registry the component was registered to <p>Available data:</p> name type description <code>component_cls</code> <code>Type[Component]</code> The unregistered Component class <code>name</code> <code>str</code> The name the component was registered under <code>registry</code> <code>ComponentRegistry</code> The registry the component was unregistered from <p>Available data:</p> name type description <code>registry</code> <code>ComponentRegistry</code> The created ComponentRegistry instance <p>Available data:</p> name type description <code>registry</code> <code>ComponentRegistry</code> The to-be-deleted ComponentRegistry instance"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_class_created","title":"on_component_class_created","text":"<pre><code>on_component_class_created(ctx: OnComponentClassCreatedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a new <code>Component</code> class is created.</p> <p>This hook is called after the <code>Component</code> class is fully defined but before it's registered.</p> <p>Use this hook to perform any initialization or validation of the <code>Component</code> class.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentClassCreatedContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_class_created(self, ctx: OnComponentClassCreatedContext) -&gt; None:\n        # Add a new attribute to the Component class\n        ctx.component_cls.my_attr = \"my_value\"\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_class_deleted","title":"on_component_class_deleted","text":"<pre><code>on_component_class_deleted(ctx: OnComponentClassDeletedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is being deleted.</p> <p>This hook is called before the <code>Component</code> class is deleted from memory.</p> <p>Use this hook to perform any cleanup related to the <code>Component</code> class.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentClassDeletedContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_class_deleted(self, ctx: OnComponentClassDeletedContext) -&gt; None:\n        # Remove Component class from the extension's cache on deletion\n        self.cache.pop(ctx.component_cls, None)\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_data","title":"on_component_data","text":"<pre><code>on_component_data(ctx: OnComponentDataContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a Component was triggered to render, after a component's context and data methods have been processed.</p> <p>This hook is called after <code>Component.get_context_data()</code>, <code>Component.get_js_data()</code> and <code>Component.get_css_data()</code>.</p> <p>This hook runs after <code>on_component_input</code>.</p> <p>Use this hook to modify or validate the component's data before rendering.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentDataContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_data(self, ctx: OnComponentDataContext) -&gt; None:\n        # Add extra template variable to all components when they are rendered\n        ctx.context_data[\"my_template_var\"] = \"my_value\"\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_input","title":"on_component_input","text":"<pre><code>on_component_input(ctx: OnComponentInputContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> was triggered to render, but before a component's context and data methods are invoked.</p> <p>This hook is called before <code>Component.get_context_data()</code>, <code>Component.get_js_data()</code> and <code>Component.get_css_data()</code>.</p> <p>Use this hook to modify or validate component inputs before they're processed.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentInputContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_input(self, ctx: OnComponentInputContext) -&gt; None:\n        # Add extra kwarg to all components when they are rendered\n        ctx.kwargs[\"my_input\"] = \"my_value\"\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_registered","title":"on_component_registered","text":"<pre><code>on_component_registered(ctx: OnComponentRegisteredContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is registered with a <code>ComponentRegistry</code>.</p> <p>This hook is called after a <code>Component</code> class is successfully registered.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentRegisteredContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_registered(self, ctx: OnComponentRegisteredContext) -&gt; None:\n        print(f\"Component {ctx.component_cls} registered to {ctx.registry} as '{ctx.name}'\")\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_component_unregistered","title":"on_component_unregistered","text":"<pre><code>on_component_unregistered(ctx: OnComponentUnregisteredContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>Component</code> class is unregistered from a <code>ComponentRegistry</code>.</p> <p>This hook is called after a <code>Component</code> class is removed from the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnComponentUnregisteredContext\n\nclass MyExtension(ComponentExtension):\n    def on_component_unregistered(self, ctx: OnComponentUnregisteredContext) -&gt; None:\n        print(f\"Component {ctx.component_cls} unregistered from {ctx.registry} as '{ctx.name}'\")\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_registry_created","title":"on_registry_created","text":"<pre><code>on_registry_created(ctx: OnRegistryCreatedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a new <code>ComponentRegistry</code> is created.</p> <p>This hook is called after a new <code>ComponentRegistry</code> instance is initialized.</p> <p>Use this hook to perform any initialization needed for the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnRegistryCreatedContext\n\nclass MyExtension(ComponentExtension):\n    def on_registry_created(self, ctx: OnRegistryCreatedContext) -&gt; None:\n        # Add a new attribute to the registry\n        ctx.registry.my_attr = \"my_value\"\n</code></pre>"},{"location":"reference/extension_hooks/#django_components.extension.ComponentExtension.on_registry_deleted","title":"on_registry_deleted","text":"<pre><code>on_registry_deleted(ctx: OnRegistryDeletedContext) -&gt; None\n</code></pre> <p>See source code</p> <p>Called when a <code>ComponentRegistry</code> is being deleted.</p> <p>This hook is called before a <code>ComponentRegistry</code> instance is deleted.</p> <p>Use this hook to perform any cleanup related to the registry.</p> <p>Example:</p> <pre><code>from django_components import ComponentExtension, OnRegistryDeletedContext\n\nclass MyExtension(ComponentExtension):\n    def on_registry_deleted(self, ctx: OnRegistryDeletedContext) -&gt; None:\n        # Remove registry from the extension's cache on deletion\n        self.cache.pop(ctx.registry, None)\n</code></pre>"},{"location":"reference/middlewares/","title":"Middlewares","text":""},{"location":"reference/middlewares/#middlewares","title":"Middlewares","text":""},{"location":"reference/middlewares/#django_components.dependencies.ComponentDependencyMiddleware","title":"<code>ComponentDependencyMiddleware</code>","text":"<p>Bases: <code>object</code></p> <p>See source code</p> <p>Middleware that inserts CSS/JS dependencies for all rendered components at points marked with template tags.</p>"},{"location":"reference/settings/","title":"Settings","text":""},{"location":"reference/settings/#settings","title":"Settings","text":"<p>You can configure django_components with a global <code>COMPONENTS</code> variable in your Django settings file, e.g. <code>settings.py</code>. By default you don't need it set, there are resonable defaults.</p> <p>To configure the settings you can instantiate <code>ComponentsSettings</code> for validation and type hints. Or, for backwards compatibility, you can also use plain dictionary:</p> <pre><code># settings.py\nfrom django_components import ComponentsSettings\n\nCOMPONENTS = ComponentsSettings(\n    autodiscover=True,\n    ...\n)\n\n# or\n\nCOMPONENTS = {\n    \"autodiscover\": True,\n    ...\n}\n</code></pre>"},{"location":"reference/settings/#settings-defaults","title":"Settings defaults","text":"<p>Here's overview of all available settings and their defaults:</p> <pre><code>defaults = ComponentsSettings(\n    autodiscover=True,\n    cache=None,\n    context_behavior=ContextBehavior.DJANGO.value,  # \"django\" | \"isolated\"\n    # Root-level \"components\" dirs, e.g. `/path/to/proj/components/`\n    dirs=[Path(settings.BASE_DIR) / \"components\"],\n    # App-level \"components\" dirs, e.g. `[app]/components/`\n    app_dirs=[\"components\"],\n    debug_highlight_components=False,\n    debug_highlight_slots=False,\n    dynamic_component_name=\"dynamic\",\n    extensions=[],\n    libraries=[],  # E.g. [\"mysite.components.forms\", ...]\n    multiline_tags=True,\n    reload_on_file_change=False,\n    static_files_allowed=[\n        \".css\",\n        \".js\", \".jsx\", \".ts\", \".tsx\",\n        # Images\n        \".apng\", \".png\", \".avif\", \".gif\", \".jpg\",\n        \".jpeg\", \".jfif\", \".pjpeg\", \".pjp\", \".svg\",\n        \".webp\", \".bmp\", \".ico\", \".cur\", \".tif\", \".tiff\",\n        # Fonts\n        \".eot\", \".ttf\", \".woff\", \".otf\", \".svg\",\n    ],\n    static_files_forbidden=[\n        # See https://marketplace.visualstudio.com/items?itemName=junstyle.vscode-django-support\n        \".html\", \".django\", \".dj\", \".tpl\",\n        # Python files\n        \".py\", \".pyc\",\n    ],\n    tag_formatter=\"django_components.component_formatter\",\n    template_cache_size=128,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.app_dirs","title":"app_dirs","text":"<pre><code>app_dirs: Optional[Sequence[str]] = None\n</code></pre> <p>See source code</p> <p>Specify the app-level directories that contain your components.</p> <p>Defaults to <code>[\"components\"]</code>. That is, for each Django app, we search <code>&lt;app&gt;/components/</code> for components.</p> <p>The paths must be relative to app, e.g.:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    app_dirs=[\"my_comps\"],\n)\n</code></pre> <p>To search for <code>&lt;app&gt;/my_comps/</code>.</p> <p>These locations are searched during autodiscovery, or when you define HTML, JS, or CSS as separate files.</p> <p>Set to empty list to disable app-level components:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    app_dirs=[],\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.autodiscover","title":"autodiscover","text":"<pre><code>autodiscover: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Toggle whether to run autodiscovery at the Django server startup.</p> <p>Defaults to <code>True</code></p> <pre><code>COMPONENTS = ComponentsSettings(\n    autodiscover=False,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.cache","title":"cache","text":"<pre><code>cache: Optional[str] = None\n</code></pre> <p>See source code</p> <p>Name of the Django cache to be used for storing component's JS and CSS files.</p> <p>If <code>None</code>, a <code>LocMemCache</code> is used with default settings.</p> <p>Defaults to <code>None</code>.</p> <p>Read more about caching.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    cache=\"my_cache\",\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.context_behavior","title":"context_behavior","text":"<pre><code>context_behavior: Optional[ContextBehaviorType] = None\n</code></pre> <p>See source code</p> <p>Configure whether, inside a component template, you can use variables from the outside (<code>\"django\"</code>) or not (<code>\"isolated\"</code>). This also affects what variables are available inside the <code>{% fill %}</code> tags.</p> <p>Also see Component context and scope.</p> <p>Defaults to <code>\"django\"</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    context_behavior=\"isolated\",\n)\n</code></pre> <p>NOTE: <code>context_behavior</code> and <code>slot_context_behavior</code> options were merged in v0.70.</p> <p>If you are migrating from BEFORE v0.67, set <code>context_behavior</code> to <code>\"django\"</code>. From v0.67 to v0.78 (incl) the default value was <code>\"isolated\"</code>.</p> <p>For v0.79 and later, the default is again <code>\"django\"</code>. See the rationale for change here.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_components","title":"debug_highlight_components","text":"<pre><code>debug_highlight_components: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable component highlighting. See Troubleshooting for more details.</p> <p>Defaults to <code>False</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    debug_highlight_components=True,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_slots","title":"debug_highlight_slots","text":"<pre><code>debug_highlight_slots: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable slot highlighting. See Troubleshooting for more details.</p> <p>Defaults to <code>False</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    debug_highlight_slots=True,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.dirs","title":"dirs","text":"<pre><code>dirs: Optional[Sequence[Union[str, PathLike, Tuple[str, str], Tuple[str, PathLike]]]] = None\n</code></pre> <p>See source code</p> <p>Specify the directories that contain your components.</p> <p>Defaults to <code>[Path(settings.BASE_DIR) / \"components\"]</code>. That is, the root <code>components/</code> app.</p> <p>Directories must be full paths, same as with STATICFILES_DIRS.</p> <p>These locations are searched during autodiscovery, or when you define HTML, JS, or CSS as separate files.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    dirs=[BASE_DIR / \"components\"],\n)\n</code></pre> <p>Set to empty list to disable global components directories:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    dirs=[],\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.dynamic_component_name","title":"dynamic_component_name","text":"<pre><code>dynamic_component_name: Optional[str] = None\n</code></pre> <p>See source code</p> <p>By default, the dynamic component is registered under the name <code>\"dynamic\"</code>.</p> <p>In case of a conflict, you can use this setting to change the component name used for the dynamic components.</p> <pre><code># settings.py\nCOMPONENTS = ComponentsSettings(\n    dynamic_component_name=\"my_dynamic\",\n)\n</code></pre> <p>After which you will be able to use the dynamic component with the new name:</p> <pre><code>{% component \"my_dynamic\" is=table_comp data=table_data headers=table_headers %}\n    {% fill \"pagination\" %}\n        {% component \"pagination\" / %}\n    {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.extensions","title":"extensions","text":"<pre><code>extensions: Optional[Sequence[Union[Type[ComponentExtension], str]]] = None\n</code></pre> <p>See source code</p> <p>List of extensions to be loaded.</p> <p>The extensions can be specified as:</p> <ul> <li>Python import path, e.g. <code>\"path.to.my_extension.MyExtension\"</code>.</li> <li>Extension class, e.g. <code>my_extension.MyExtension</code>.</li> </ul> <pre><code>COMPONENTS = ComponentsSettings(\n    extensions=[\n        \"path.to.my_extension.MyExtension\",\n        StorybookExtension,\n    ],\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.forbidden_static_files","title":"forbidden_static_files","text":"<pre><code>forbidden_static_files: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>COMPONENTS.static_files_forbidden</code> instead.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.libraries","title":"libraries","text":"<pre><code>libraries: Optional[List[str]] = None\n</code></pre> <p>See source code</p> <p>Configure extra python modules that should be loaded.</p> <p>This may be useful if you are not using the autodiscovery feature, or you need to load components from non-standard locations. Thus you can have a structure of components that is independent from your apps.</p> <p>Expects a list of python module paths. Defaults to empty list.</p> <p>Example:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    libraries=[\n        \"mysite.components.forms\",\n        \"mysite.components.buttons\",\n        \"mysite.components.cards\",\n    ],\n)\n</code></pre> <p>This would be the equivalent of importing these modules from within Django's <code>AppConfig.ready()</code>:</p> <pre><code>class MyAppConfig(AppConfig):\n    def ready(self):\n        import \"mysite.components.forms\"\n        import \"mysite.components.buttons\"\n        import \"mysite.components.cards\"\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.libraries--manually-loading-libraries","title":"Manually loading libraries","text":"<p>In the rare case that you need to manually trigger the import of libraries, you can use the <code>import_libraries()</code> function:</p> <pre><code>from django_components import import_libraries\n\nimport_libraries()\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.multiline_tags","title":"multiline_tags","text":"<pre><code>multiline_tags: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Enable / disable multiline support for template tags. If <code>True</code>, template tags like <code>{% component %}</code> or <code>{{ my_var }}</code> can span multiple lines.</p> <p>Defaults to <code>True</code>.</p> <p>Disable this setting if you are making custom modifications to Django's regular expression for parsing templates at <code>django.template.base.tag_re</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    multiline_tags=False,\n)\n</code></pre>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.reload_on_file_change","title":"reload_on_file_change","text":"<pre><code>reload_on_file_change: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>This is relevant if you are using the project structure where HTML, JS, CSS and Python are in separate files and nested in a directory.</p> <p>In this case you may notice that when you are running a development server, the server sometimes does not reload when you change component files.</p> <p>Django's native live reload logic handles only Python files and HTML template files. It does NOT reload when other file types change or when template files are nested more than one level deep.</p> <p>The setting <code>reload_on_file_change</code> fixes this, reloading the dev server even when your component's HTML, JS, or CSS changes.</p> <p>If <code>True</code>, django_components configures Django to reload when files inside <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> change.</p> <p>See Reload dev server on component file changes.</p> <p>Defaults to <code>False</code>.</p> <p>Warning</p> <p>This setting should be enabled only for the dev environment!</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.reload_on_template_change","title":"reload_on_template_change","text":"<pre><code>reload_on_template_change: Optional[bool] = None\n</code></pre> <p>See source code</p> <p>Deprecated. Use <code>COMPONENTS.reload_on_file_change</code> instead.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.static_files_allowed","title":"static_files_allowed","text":"<pre><code>static_files_allowed: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>A list of file extensions (including the leading dot) that define which files within <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> are treated as static files.</p> <p>If a file is matched against any of the patterns, it's considered a static file. Such files are collected when running <code>collectstatic</code>, and can be accessed under the static file endpoint.</p> <p>You can also pass in compiled regexes (<code>re.Pattern</code>) for more advanced patterns.</p> <p>By default, JS, CSS, and common image and font file formats are considered static files:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    static_files_allowed=[\n        \".css\",\n        \".js\", \".jsx\", \".ts\", \".tsx\",\n        # Images\n        \".apng\", \".png\", \".avif\", \".gif\", \".jpg\",\n        \".jpeg\",  \".jfif\", \".pjpeg\", \".pjp\", \".svg\",\n        \".webp\", \".bmp\", \".ico\", \".cur\", \".tif\", \".tiff\",\n        # Fonts\n        \".eot\", \".ttf\", \".woff\", \".otf\", \".svg\",\n    ],\n)\n</code></pre> <p>Warning</p> <p>Exposing your Python files can be a security vulnerability. See Security notes.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.static_files_forbidden","title":"static_files_forbidden","text":"<pre><code>static_files_forbidden: Optional[List[Union[str, Pattern]]] = None\n</code></pre> <p>See source code</p> <p>A list of file extensions (including the leading dot) that define which files within <code>COMPONENTS.dirs</code> or <code>COMPONENTS.app_dirs</code> will NEVER be treated as static files.</p> <p>If a file is matched against any of the patterns, it will never be considered a static file, even if the file matches a pattern in <code>static_files_allowed</code>.</p> <p>Use this setting together with <code>static_files_allowed</code> for a fine control over what file types will be exposed.</p> <p>You can also pass in compiled regexes (<code>re.Pattern</code>) for more advanced patterns.</p> <p>By default, any HTML and Python are considered NOT static files:</p> <pre><code>COMPONENTS = ComponentsSettings(\n    static_files_forbidden=[\n        \".html\", \".django\", \".dj\", \".tpl\",\n        # Python files\n        \".py\", \".pyc\",\n    ],\n)\n</code></pre> <p>Warning</p> <p>Exposing your Python files can be a security vulnerability. See Security notes.</p>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.tag_formatter","title":"tag_formatter","text":"<pre><code>tag_formatter: Optional[Union[TagFormatterABC, str]] = None\n</code></pre> <p>See source code</p> <p>Configure what syntax is used inside Django templates to render components. See the available tag formatters.</p> <p>Defaults to <code>\"django_components.component_formatter\"</code>.</p> <p>Learn more about Customizing component tags with TagFormatter.</p> <p>Can be set either as direct reference:</p> <pre><code>from django_components import component_formatter\n\nCOMPONENTS = ComponentsSettings(\n    \"tag_formatter\": component_formatter\n)\n</code></pre> <p>Or as an import string;</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_formatter\"\n)\n</code></pre> <p>Examples:</p> <ul> <li> <p><code>\"django_components.component_formatter\"</code></p> <p>Set</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_formatter\"\n)\n</code></pre> <p>To write components like this:</p> <pre><code>{% component \"button\" href=\"...\" %}\n    Click me!\n{% endcomponent %}\n</code></pre> </li> <li> <p><code>django_components.component_shorthand_formatter</code></p> <p>Set</p> <pre><code>COMPONENTS = ComponentsSettings(\n    \"tag_formatter\": \"django_components.component_shorthand_formatter\"\n)\n</code></pre> <p>To write components like this:</p> <pre><code>{% button href=\"...\" %}\n    Click me!\n{% endbutton %}\n</code></pre> </li> </ul>"},{"location":"reference/settings/#django_components.app_settings.ComponentsSettings.template_cache_size","title":"template_cache_size","text":"<pre><code>template_cache_size: Optional[int] = None\n</code></pre> <p>See source code</p> <p>Configure the maximum amount of Django templates to be cached.</p> <p>Defaults to <code>128</code>.</p> <p>Each time a Django template is rendered, it is cached to a global in-memory cache (using Python's <code>lru_cache</code> decorator). This speeds up the next render of the component. As the same component is often used many times on the same page, these savings add up.</p> <p>By default the cache holds 128 component templates in memory, which should be enough for most sites. But if you have a lot of components, or if you are overriding <code>Component.get_template()</code> to render many dynamic templates, you can increase this number.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    template_cache_size=256,\n)\n</code></pre> <p>To remove the cache limit altogether and cache everything, set <code>template_cache_size</code> to <code>None</code>.</p> <pre><code>COMPONENTS = ComponentsSettings(\n    template_cache_size=None,\n)\n</code></pre> <p>If you want to add templates to the cache yourself, you can use <code>cached_template()</code>:</p> <pre><code>from django_components import cached_template\n\ncached_template(\"Variable: {{ variable }}\")\n\n# You can optionally specify Template class, and other Template inputs:\nclass MyTemplate(Template):\n    pass\n\ncached_template(\n    \"Variable: {{ variable }}\",\n    template_cls=MyTemplate,\n    name=...\n    origin=...\n    engine=...\n)\n</code></pre>"},{"location":"reference/signals/","title":"Signals","text":""},{"location":"reference/signals/#signals","title":"Signals","text":"<p>Below are the signals that are sent by or during the use of django-components.</p>"},{"location":"reference/signals/#template_rendered","title":"template_rendered","text":"<p>Django's <code>template_rendered</code> signal. This signal is sent when a template is rendered.</p> <p>Django-components triggers this signal when a component is rendered. If there are nested components, the signal is triggered for each component.</p> <p>Import from django as <code>django.test.signals.template_rendered</code>.</p> <pre><code>from django.test.signals import template_rendered\n\n# Setup a callback function\ndef my_callback(sender, **kwargs):\n    ...\n\ntemplate_rendered.connect(my_callback)\n\nclass MyTable(Component):\n    template = \"\"\"\n    &lt;table&gt;\n        &lt;tr&gt;\n            &lt;th&gt;Header&lt;/th&gt;\n        &lt;/tr&gt;\n        &lt;tr&gt;\n            &lt;td&gt;Cell&lt;/td&gt;\n        &lt;/tr&gt;\n    \"\"\"\n\n# This will trigger the signal\nMyTable().render()\n</code></pre>"},{"location":"reference/tag_formatters/","title":"Tag formatters","text":""},{"location":"reference/tag_formatters/#tag-formatters","title":"Tag Formatters","text":"<p>Tag formatters allow you to change the syntax for calling components from within the Django templates.</p> <p>Tag formatter are set via the tag_formatter setting.</p>"},{"location":"reference/tag_formatters/#available-tag-formatters","title":"Available tag formatters","text":"<ul> <li> <p><code>django_components.component_formatter</code> for ComponentFormatter</p> </li> <li> <p><code>django_components.component_shorthand_formatter</code> for ShorthandComponentFormatter </p> </li> </ul>"},{"location":"reference/tag_formatters/#django_components.tag_formatter.ComponentFormatter","title":"<code>ComponentFormatter</code>","text":"<p>Bases: <code>django_components.tag_formatter.TagFormatterABC</code></p> <p>See source code</p> <p>The original django_component's component tag formatter, it uses the <code>{% component %}</code> and <code>{% endcomponent %}</code> tags, and the component name is given as the first positional arg.</p> <p>Example as block: <pre><code>{% component \"mycomp\" abc=123 %}\n    {% fill \"myfill\" %}\n        ...\n    {% endfill %}\n{% endcomponent %}\n</code></pre></p> <p>Example as inlined tag: <pre><code>{% component \"mycomp\" abc=123 / %}\n</code></pre></p>"},{"location":"reference/tag_formatters/#django_components.tag_formatter.ShorthandComponentFormatter","title":"<code>ShorthandComponentFormatter</code>","text":"<p>Bases: <code>django_components.tag_formatter.TagFormatterABC</code></p> <p>See source code</p> <p>The component tag formatter that uses <code>{% &lt;name&gt; %}</code> / <code>{% end&lt;name&gt; %}</code> tags.</p> <p>This is similar to django-web-components and django-slippers syntax.</p> <p>Example as block: <pre><code>{% mycomp abc=123 %}\n    {% fill \"myfill\" %}\n        ...\n    {% endfill %}\n{% endmycomp %}\n</code></pre></p> <p>Example as inlined tag: <pre><code>{% mycomp abc=123 / %}\n</code></pre></p>"},{"location":"reference/template_tags/","title":"Template tags","text":""},{"location":"reference/template_tags/#template-tags","title":"Template tags","text":"<p>All following template tags are defined in</p> <p><code>django_components.templatetags.component_tags</code></p> <p>Import as <pre><code>{% load component_tags %}\n</code></pre></p>"},{"location":"reference/template_tags/#component_css_dependencies","title":"component_css_dependencies","text":"<pre><code>{% component_css_dependencies  %}\n</code></pre> <p>See source code</p> <p>Marks location where CSS link tags should be rendered after the whole HTML has been generated.</p> <p>Generally, this should be inserted into the <code>&lt;head&gt;</code> tag of the HTML.</p> <p>If the generated HTML does NOT contain any <code>{% component_css_dependencies %}</code> tags, CSS links are by default inserted into the <code>&lt;head&gt;</code> tag of the HTML. (See JS and CSS output locations)</p> <p>Note that there should be only one <code>{% component_css_dependencies %}</code> for the whole HTML document. If you insert this tag multiple times, ALL CSS links will be duplicately inserted into ALL these places.</p>"},{"location":"reference/template_tags/#component_js_dependencies","title":"component_js_dependencies","text":"<pre><code>{% component_js_dependencies  %}\n</code></pre> <p>See source code</p> <p>Marks location where JS link tags should be rendered after the whole HTML has been generated.</p> <p>Generally, this should be inserted at the end of the <code>&lt;body&gt;</code> tag of the HTML.</p> <p>If the generated HTML does NOT contain any <code>{% component_js_dependencies %}</code> tags, JS scripts are by default inserted at the end of the <code>&lt;body&gt;</code> tag of the HTML. (See JS and CSS output locations)</p> <p>Note that there should be only one <code>{% component_js_dependencies %}</code> for the whole HTML document. If you insert this tag multiple times, ALL JS scripts will be duplicately inserted into ALL these places.</p>"},{"location":"reference/template_tags/#component","title":"component","text":"<pre><code>{% component *args: Any, **kwargs: Any [only] %}\n{% endcomponent %}\n</code></pre> <p>See source code</p> <p>Renders one of the components that was previously registered with <code>@register()</code> decorator.</p> <p>Args:</p> <ul> <li><code>name</code> (str, required): Registered name of the component to render</li> <li>All other args and kwargs are defined based on the component itself.</li> </ul> <p>If you defined a component <code>\"my_table\"</code></p> <pre><code>from django_component import Component, register\n\n@register(\"my_table\")\nclass MyTable(Component):\n    template = \"\"\"\n      &lt;table&gt;\n        &lt;thead&gt;\n          {% for header in headers %}\n            &lt;th&gt;{{ header }}&lt;/th&gt;\n          {% endfor %}\n        &lt;/thead&gt;\n        &lt;tbody&gt;\n          {% for row in rows %}\n            &lt;tr&gt;\n              {% for cell in row %}\n                &lt;td&gt;{{ cell }}&lt;/td&gt;\n              {% endfor %}\n            &lt;/tr&gt;\n          {% endfor %}\n        &lt;tbody&gt;\n      &lt;/table&gt;\n    \"\"\"\n\n    def get_context_data(self, rows: List, headers: List):\n        return {\n            \"rows\": rows,\n            \"headers\": headers,\n        }\n</code></pre> <p>Then you can render this component by referring to <code>MyTable</code> via its registered name <code>\"my_table\"</code>:</p> <pre><code>{% component \"my_table\" rows=rows headers=headers ... / %}\n</code></pre>"},{"location":"reference/template_tags/#component-input","title":"Component input","text":"<p>Positional and keyword arguments can be literals or template variables.</p> <p>The component name must be a single- or double-quotes string and must be either:</p> <ul> <li> <p>The first positional argument after <code>component</code>:</p> <pre><code>{% component \"my_table\" rows=rows headers=headers ... / %}\n</code></pre> </li> <li> <p>Passed as kwarg <code>name</code>:</p> <pre><code>{% component rows=rows headers=headers name=\"my_table\" ... / %}\n</code></pre> </li> </ul>"},{"location":"reference/template_tags/#inserting-into-slots","title":"Inserting into slots","text":"<p>If the component defined any slots, you can pass in the content to be placed inside those slots by inserting <code>{% fill %}</code> tags, directly within the <code>{% component %}</code> tag:</p> <pre><code>{% component \"my_table\" rows=rows headers=headers ... / %}\n  {% fill \"pagination\" %}\n    &lt; 1 | 2 | 3 &gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/template_tags/#isolating-components","title":"Isolating components","text":"<p>By default, components behave similarly to Django's <code>{% include %}</code>, and the template inside the component has access to the variables defined in the outer template.</p> <p>You can selectively isolate a component, using the <code>only</code> flag, so that the inner template can access only the data that was explicitly passed to it:</p> <pre><code>{% component \"name\" positional_arg keyword_arg=value ... only %}\n</code></pre>"},{"location":"reference/template_tags/#fill","title":"fill","text":"<pre><code>{% fill name: str, *, data: Optional[str] = None, default: Optional[str] = None %}\n{% endfill %}\n</code></pre> <p>See source code</p> <p>Use this tag to insert content into component's slots.</p> <p><code>{% fill %}</code> tag may be used only within a <code>{% component %}..{% endcomponent %}</code> block. Runtime checks should prohibit other usages.</p> <p>Args:</p> <ul> <li><code>name</code> (str, required): Name of the slot to insert this content into. Use <code>\"default\"</code> for     the default slot.</li> <li><code>default</code> (str, optional): This argument allows you to access the original content of the slot     under the specified variable name. See     Accessing original content of slots</li> <li><code>data</code> (str, optional): This argument allows you to access the data passed to the slot     under the specified variable name. See Scoped slots</li> </ul> <p>Examples:</p> <p>Basic usage: <pre><code>{% component \"my_table\" %}\n  {% fill \"pagination\" %}\n    &lt; 1 | 2 | 3 &gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre></p>"},{"location":"reference/template_tags/#accessing-slots-default-content-with-the-default-kwarg","title":"Accessing slot's default content with the <code>default</code> kwarg","text":"<pre><code>{# my_table.html #}\n&lt;table&gt;\n  ...\n  {% slot \"pagination\" %}\n    &lt; 1 | 2 | 3 &gt;\n  {% endslot %}\n&lt;/table&gt;\n</code></pre> <pre><code>{% component \"my_table\" %}\n  {% fill \"pagination\" default=\"default_pag\" %}\n    &lt;div class=\"my-class\"&gt;\n      {{ default_pag }}\n    &lt;/div&gt;\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/template_tags/#accessing-slots-data-with-the-data-kwarg","title":"Accessing slot's data with the <code>data</code> kwarg","text":"<pre><code>{# my_table.html #}\n&lt;table&gt;\n  ...\n  {% slot \"pagination\" pages=pages %}\n    &lt; 1 | 2 | 3 &gt;\n  {% endslot %}\n&lt;/table&gt;\n</code></pre> <pre><code>{% component \"my_table\" %}\n  {% fill \"pagination\" data=\"slot_data\" %}\n    {% for page in slot_data.pages %}\n        &lt;a href=\"{{ page.link }}\"&gt;\n          {{ page.index }}\n        &lt;/a&gt;\n    {% endfor %}\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/template_tags/#accessing-slot-data-and-default-content-on-the-default-slot","title":"Accessing slot data and default content on the default slot","text":"<p>To access slot data and the default slot content on the default slot, use <code>{% fill %}</code> with <code>name</code> set to <code>\"default\"</code>:</p> <pre><code>{% component \"button\" %}\n  {% fill name=\"default\" data=\"slot_data\" default=\"default_slot\" %}\n    You clicked me {{ slot_data.count }} times!\n    {{ default_slot }}\n  {% endfill %}\n{% endcomponent %}\n</code></pre>"},{"location":"reference/template_tags/#html_attrs","title":"html_attrs","text":"<pre><code>{% html_attrs attrs: Optional[Dict] = None, defaults: Optional[Dict] = None, **kwargs: Any %}\n</code></pre> <p>See source code</p> <p>Generate HTML attributes (<code>key=\"value\"</code>), combining data from multiple sources, whether its template variables or static text.</p> <p>It is designed to easily merge HTML attributes passed from outside with the internal. See how to in Passing HTML attributes to components.</p> <p>Args:</p> <ul> <li><code>attrs</code> (dict, optional): Optional dictionary that holds HTML attributes. On conflict, overrides     values in the <code>default</code> dictionary.</li> <li><code>default</code> (str, optional): Optional dictionary that holds HTML attributes. On conflict, is overriden     with values in the <code>attrs</code> dictionary.</li> <li>Any extra kwargs will be appended to the corresponding keys</li> </ul> <p>The attributes in <code>attrs</code> and <code>defaults</code> are merged and resulting dict is rendered as HTML attributes (<code>key=\"value\"</code>).</p> <p>Extra kwargs (<code>key=value</code>) are concatenated to existing keys. So if we have</p> <pre><code>attrs = {\"class\": \"my-class\"}\n</code></pre> <p>Then</p> <pre><code>{% html_attrs attrs class=\"extra-class\" %}\n</code></pre> <p>will result in <code>class=\"my-class extra-class\"</code>.</p> <p>Example: <pre><code>&lt;div {% html_attrs\n    attrs\n    defaults:class=\"default-class\"\n    class=\"extra-class\"\n    data-id=\"123\"\n%}&gt;\n</code></pre></p> <p>renders</p> <pre><code>&lt;div class=\"my-class extra-class\" data-id=\"123\"&gt;\n</code></pre> <p>See more usage examples in HTML attributes.</p>"},{"location":"reference/template_tags/#provide","title":"provide","text":"<pre><code>{% provide name: str, **kwargs: Any %}\n{% endprovide %}\n</code></pre> <p>See source code</p> <p>The \"provider\" part of the provide / inject feature. Pass kwargs to this tag to define the provider's data. Any components defined within the <code>{% provide %}..{% endprovide %}</code> tags will be able to access this data with <code>Component.inject()</code>.</p> <p>This is similar to React's <code>ContextProvider</code>, or Vue's <code>provide()</code>.</p> <p>Args:</p> <ul> <li><code>name</code> (str, required): Provider name. This is the name you will then use in     <code>Component.inject()</code>.</li> <li><code>**kwargs</code>: Any extra kwargs will be passed as the provided data.</li> </ul> <p>Example:</p> <p>Provide the \"user_data\" in parent component:</p> <pre><code>@register(\"parent\")\nclass Parent(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% provide \"user_data\" user=user %}\n          {% component \"child\" / %}\n        {% endprovide %}\n      &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self, user: User):\n        return {\n            \"user\": user,\n        }\n</code></pre> <p>Since the \"child\" component is used within the <code>{% provide %} / {% endprovide %}</code> tags, we can request the \"user_data\" using <code>Component.inject(\"user_data\")</code>:</p> <pre><code>@register(\"child\")\nclass Child(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        User is: {{ user }}\n      &lt;/div&gt;\n    \"\"\"\n\n    def get_context_data(self):\n        user = self.inject(\"user_data\").user\n        return {\n            \"user\": user,\n        }\n</code></pre> <p>Notice that the keys defined on the <code>{% provide %}</code> tag are then accessed as attributes when accessing them with <code>Component.inject()</code>.</p> <p>\u2705 Do this <pre><code>user = self.inject(\"user_data\").user\n</code></pre></p> <p>\u274c Don't do this <pre><code>user = self.inject(\"user_data\")[\"user\"]\n</code></pre></p>"},{"location":"reference/template_tags/#slot","title":"slot","text":"<pre><code>{% slot name: str, **kwargs: Any [default] [required] %}\n{% endslot %}\n</code></pre> <p>See source code</p> <p>Slot tag marks a place inside a component where content can be inserted from outside.</p> <p>Learn more about using slots.</p> <p>This is similar to slots as seen in Web components, Vue or React's <code>children</code>.</p> <p>Args:</p> <ul> <li><code>name</code> (str, required): Registered name of the component to render</li> <li><code>default</code>: Optional flag. If there is a default slot, you can pass the component slot content     without using the <code>{% fill %}</code> tag. See     Default slot</li> <li><code>required</code>: Optional flag. Will raise an error if a slot is required but not given.</li> <li><code>**kwargs</code>: Any extra kwargs will be passed as the slot data.</li> </ul> <p>Example:</p> <pre><code>@register(\"child\")\nclass Child(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% slot \"content\" default %}\n          This is shown if not overriden!\n        {% endslot %}\n      &lt;/div&gt;\n      &lt;aside&gt;\n        {% slot \"sidebar\" required / %}\n      &lt;/aside&gt;\n    \"\"\"\n</code></pre> <pre><code>@register(\"parent\")\nclass Parent(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% component \"child\" %}\n          {% fill \"content\" %}\n            \ud83d\uddde\ufe0f\ud83d\udcf0\n          {% endfill %}\n\n          {% fill \"sidebar\" %}\n            \ud83c\udf77\ud83e\uddc9\ud83c\udf7e\n          {% endfill %}\n        {% endcomponent %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre>"},{"location":"reference/template_tags/#passing-data-to-slots","title":"Passing data to slots","text":"<p>Any extra kwargs will be considered as slot data, and will be accessible in the <code>{% fill %}</code> tag via fill's <code>data</code> kwarg:</p> <pre><code>@register(\"child\")\nclass Child(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {# Passing data to the slot #}\n        {% slot \"content\" user=user %}\n          This is shown if not overriden!\n        {% endslot %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre> <pre><code>@register(\"parent\")\nclass Parent(Component):\n    template = \"\"\"\n      {# Parent can access the slot data #}\n      {% component \"child\" %}\n        {% fill \"content\" data=\"data\" %}\n          &lt;div class=\"wrapper-class\"&gt;\n            {{ data.user }}\n          &lt;/div&gt;\n        {% endfill %}\n      {% endcomponent %}\n    \"\"\"\n</code></pre>"},{"location":"reference/template_tags/#accessing-default-slot-content","title":"Accessing default slot content","text":"<p>The content between the <code>{% slot %}..{% endslot %}</code> tags is the default content that will be rendered if no fill is given for the slot.</p> <p>This default content can then be accessed from within the <code>{% fill %}</code> tag using the fill's <code>default</code> kwarg. This is useful if you need to wrap / prepend / append the original slot's content.</p> <pre><code>@register(\"child\")\nclass Child(Component):\n    template = \"\"\"\n      &lt;div&gt;\n        {% slot \"content\" %}\n          This is default content!\n        {% endslot %}\n      &lt;/div&gt;\n    \"\"\"\n</code></pre> <pre><code>@register(\"parent\")\nclass Parent(Component):\n    template = \"\"\"\n      {# Parent can access the slot's default content #}\n      {% component \"child\" %}\n        {% fill \"content\" default=\"default\" %}\n          {{ default }}\n        {% endfill %}\n      {% endcomponent %}\n    \"\"\"\n</code></pre>"},{"location":"reference/template_vars/","title":"Template vars","text":""},{"location":"reference/template_vars/#template-variables","title":"Template variables","text":"<p>Here is a list of all variables that are automatically available from inside the component's template and in <code>on_render_before</code> / <code>on_render_after</code> hooks.</p>"},{"location":"reference/template_vars/#django_components.component.ComponentVars.is_filled","title":"is_filled  <code>instance-attribute</code>","text":"<pre><code>is_filled: Dict[str, bool]\n</code></pre> <p>See source code</p> <p>Dictonary describing which component slots are filled (<code>True</code>) or are not (<code>False</code>).</p> <p>New in version 0.70</p> <p>Use as <code>{{ component_vars.is_filled }}</code></p> <p>Example:</p> <pre><code>{# Render wrapping HTML only if the slot is defined #}\n{% if component_vars.is_filled.my_slot %}\n    &lt;div class=\"slot-wrapper\"&gt;\n        {% slot \"my_slot\" / %}\n    &lt;/div&gt;\n{% endif %}\n</code></pre> <p>This is equivalent to checking if a given key is among the slot fills:</p> <pre><code>class MyTable(Component):\n    def get_context_data(self, *args, **kwargs):\n        return {\n            \"my_slot_filled\": \"my_slot\" in self.input.slots\n        }\n</code></pre>"},{"location":"reference/testing_api/","title":"Testing API","text":""},{"location":"reference/testing_api/#testing-api","title":"Testing API","text":""},{"location":"reference/testing_api/#django_components.testing.djc_test","title":"djc_test","text":"<pre><code>djc_test(\n    django_settings: Union[Optional[Dict], Callable, Type] = None,\n    components_settings: Optional[Dict] = None,\n    parametrize: Optional[\n        Union[\n            Tuple[Sequence[str], Sequence[Sequence[Any]]],\n            Tuple[\n                Sequence[str],\n                Sequence[Sequence[Any]],\n                Optional[Union[Iterable[Union[None, str, float, int, bool]], Callable[[Any], Optional[object]]]],\n            ],\n        ]\n    ] = None,\n    gc_collect: bool = True,\n) -&gt; Callable\n</code></pre> <p>See source code</p> <p>Decorator for testing components from django-components.</p> <p><code>@djc_test</code> manages the global state of django-components, ensuring that each test is properly isolated and that components registered in one test do not affect other tests.</p> <p>This decorator can be applied to a function, method, or a class. If applied to a class, it will search for all methods that start with <code>test_</code>, and apply the decorator to them. This is applied recursively to nested classes as well.</p> <p>Examples:</p> <p>Applying to a function: <pre><code>from django_components.testing import djc_test\n\n@djc_test\ndef test_my_component():\n    @register(\"my_component\")\n    class MyComponent(Component):\n        template = \"...\"\n    ...\n</code></pre></p> <p>Applying to a class: <pre><code>from django_components.testing import djc_test\n\n@djc_test\nclass TestMyComponent:\n    def test_something(self):\n        ...\n\n    class Nested:\n        def test_something_else(self):\n            ...\n</code></pre></p> <p>Applying to a class is the same as applying the decorator to each <code>test_</code> method individually: <pre><code>from django_components.testing import djc_test\n\nclass TestMyComponent:\n    @djc_test\n    def test_something(self):\n        ...\n\n    class Nested:\n        @djc_test\n        def test_something_else(self):\n            ...\n</code></pre></p> <p>To use <code>@djc_test</code>, Django must be set up first:</p> <pre><code>import django\nfrom django_components.testing import djc_test\n\ndjango.setup()\n\n@djc_test\ndef test_my_component():\n    ...\n</code></pre> <p>Arguments:</p> <ul> <li> <p><code>django_settings</code>: Django settings, a dictionary passed to Django's   <code>@override_settings</code>.   The test runs within the context of these overridden settings.</p> <p>If <code>django_settings</code> contains django-components settings (<code>COMPONENTS</code> field), these are merged. Other Django settings are simply overridden.</p> </li> <li> <p><code>components_settings</code>: Instead of defining django-components settings under <code>django_settings[\"COMPONENTS\"]</code>,     you can simply set the Components settings here.</p> <p>These settings are merged with the django-components settings from <code>django_settings[\"COMPONENTS\"]</code>.</p> <p>Fields in <code>components_settings</code> override fields in <code>django_settings[\"COMPONENTS\"]</code>.</p> </li> <li> <p><code>parametrize</code>: Parametrize the test function with     <code>pytest.mark.parametrize</code>.     This requires pytest to be installed.</p> <p>The input is a tuple of:</p> <ul> <li><code>(param_names, param_values)</code> or</li> <li><code>(param_names, param_values, ids)</code></li> </ul> <p>Example:</p> <pre><code>from django_components.testing import djc_test\n\n@djc_test(\n    parametrize=(\n         [\"input\", \"expected\"],\n         [[1, \"&lt;div&gt;1&lt;/div&gt;\"], [2, \"&lt;div&gt;2&lt;/div&gt;\"]],\n         ids=[\"1\", \"2\"]\n     )\n)\ndef test_component(input, expected):\n    rendered = MyComponent(input=input).render()\n    assert rendered == expected\n</code></pre> <p>You can parametrize the Django or Components settings by setting up parameters called <code>django_settings</code> and <code>components_settings</code>. These will be merged with the respetive settings from the decorator.</p> <p>Example of parametrizing context_behavior: <pre><code>from django_components.testing import djc_test\n\n@djc_test(\n    components_settings={\n        # Settings shared by all tests\n        \"app_dirs\": [\"custom_dir\"],\n    },\n    parametrize=(\n        # Parametrized settings\n        [\"components_settings\"],\n        [\n            [{\"context_behavior\": \"django\"}],\n            [{\"context_behavior\": \"isolated\"}],\n        ],\n        [\"django\", \"isolated\"],\n    )\n)\ndef test_context_behavior(components_settings):\n    rendered = MyComponent().render()\n    ...\n</code></pre></p> </li> <li> <p><code>gc_collect</code>: By default <code>djc_test</code> runs garbage collection after each test to force the state cleanup.   Set this to <code>False</code> to skip this.</p> </li> </ul> <p>Settings resolution:</p> <p><code>@djc_test</code> accepts settings from different sources. The settings are resolved in the following order:</p> <ul> <li> <p>Django settings:</p> <ol> <li>The defaults are the Django settings that Django was set up with.</li> <li>Those are then overriden with fields in the <code>django_settings</code> kwarg.</li> <li>The parametrized <code>django_settings</code> override the fields on the <code>django_settings</code> kwarg.</li> </ol> <p>Priority: <code>django_settings</code> (parametrized) &gt; <code>django_settings</code> &gt; <code>django.conf.settings</code></p> </li> <li> <p>Components settings:</p> <ol> <li>Same as above, except that the <code>django_settings[\"COMPONENTS\"]</code> field is merged instead of overridden.</li> <li>The <code>components_settings</code> kwarg is then merged with the <code>django_settings[\"COMPONENTS\"]</code> field.</li> <li>The parametrized <code>components_settings</code> override the fields on the <code>components_settings</code> kwarg.</li> </ol> <p>Priority: <code>components_settings</code> (parametrized) &gt; <code>components_settings</code> &gt; <code>django_settings[\"COMPONENTS\"]</code> &gt; <code>django.conf.settings.COMPONENTS</code></p> </li> </ul>"},{"location":"reference/urls/","title":"URLs","text":""},{"location":"reference/urls/#urls","title":"URLs","text":"<p>Below are all the URL patterns that will be added by adding <code>django_components.urls</code>.</p> <p>See Installation on how to add these URLs to your Django project.</p> <p>Django components already prefixes all URLs with <code>components/</code>. So when you are adding the URLs to <code>urlpatterns</code>, you can use an empty string as the first argument:</p> <pre><code>from django.urls import include, path\n\nurlpatterns = [\n    ...\n    path(\"\", include(\"django_components.urls\")),\n]\n</code></pre>"},{"location":"reference/urls/#list-of-urls","title":"List of URLs","text":"<ul> <li> <p><code>components/cache/&lt;str:comp_cls_hash&gt;.&lt;str:input_hash&gt;.&lt;str:script_type&gt;</code></p> </li> <li> <p><code>components/cache/&lt;str:comp_cls_hash&gt;.&lt;str:script_type&gt;</code></p> </li> </ul>"}]}
\ No newline at end of file
diff --git a/dev/sitemap.xml b/dev/sitemap.xml
index 7d1804e6..658bb436 100644
--- a/dev/sitemap.xml
+++ b/dev/sitemap.xml
@@ -2,250 +2,250 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>https://django-components.github.io/django-components/latest/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/migrating_from_safer_staticfiles/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/release_notes/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/authoring_component_libraries/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/component_registry/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/extensions/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/hooks/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/html_fragments/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/provide_inject/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/rendering_js_css/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/tag_formatter/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/template_tags/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/testing/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/advanced/typing_and_validation/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/access_component_input/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/autodiscovery/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/component_context_scope/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/components_as_views/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/components_in_python/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/defining_js_css_html_files/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/html_attributes/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/http_request/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/single_file_components/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/slots/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/subclassing_components/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/concepts/fundamentals/template_tag_syntax/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/getting_started/adding_js_and_css/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/getting_started/adding_slots/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/getting_started/components_in_templates/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/getting_started/parametrising_components/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/getting_started/rendering_components/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/getting_started/your_first_component/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/guides/devguides/dependency_mgmt/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/guides/devguides/slot_rendering/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/guides/devguides/slots_and_blocks/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/guides/other/troubleshooting/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/guides/setup/caching/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/guides/setup/development_server/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/guides/setup/syntax_highlight/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/code_of_conduct/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/community/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/compatibility/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/contributing/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/development/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/installation/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/license/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/performance/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/security_notes/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/overview/welcome/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/api/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/commands/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/components/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/exceptions/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/extension_hooks/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/middlewares/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/settings/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/signals/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/tag_formatters/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/template_tags/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/template_vars/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/testing_api/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
     <url>
          <loc>https://django-components.github.io/django-components/latest/reference/urls/</loc>
-         <lastmod>2025-03-20</lastmod>
+         <lastmod>2025-03-21</lastmod>
     </url>
 </urlset>
\ No newline at end of file
diff --git a/dev/sitemap.xml.gz b/dev/sitemap.xml.gz
index dd9e7a3d..d5201e31 100644
Binary files a/dev/sitemap.xml.gz and b/dev/sitemap.xml.gz differ
diff --git a/versions.json b/versions.json
index e2498e63..cc48976b 100644
--- a/versions.json
+++ b/versions.json
@@ -1,7 +1,7 @@
 [
   {
     "version": "dev",
-    "title": "dev (d0a42a2)",
+    "title": "dev (ab75cfd)",
     "aliases": []
   },
   {