Django-components

Latest version: v0.135

Safety actively analyzes 723882 Python packages for vulnerabilities to keep your Python projects secure.

Page 2 of 9

0.129

Fix

- Fix thread unsafe media resolve validation by moving it to ComponentMedia `__post_init` ([977](https://github.com/django-components/django-components/pull/977)
- Fix bug: Relative path in extends and include does not work when using template_file ([976](https://github.com/django-components/django-components/pull/976)
- Fix error when template cache setting (`template_cache_size`) is set to 0 ([974](https://github.com/django-components/django-components/pull/974)

0.128

Feat

- Configurable cache - Set [`COMPONENTS.cache`](https://django-components.github.io/django-components/0.128/reference/settings/#django_components.app_settings.ComponentsSettings.cache) to change where and how django-components caches JS and CSS files. ([946](https://github.com/django-components/django-components/pull/946))

Read more on [Caching](https://django-components.github.io/django-components/0.128/guides/setup/caching).

- Highlight coponents and slots in the UI - We've added two boolean settings [`COMPONENTS.debug_highlight_components`](https://django-components.github.io/django-components/0.128/reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_components) and [`COMPONENTS.debug_highlight_slots`](https://django-components.github.io/django-components/0.128/reference/settings/#django_components.app_settings.ComponentsSettings.debug_highlight_slots), which can be independently set to `True`. First will wrap components in a blue border, the second will wrap slots in a red border. ([942](https://github.com/django-components/django-components/pull/942))

Read more on [Troubleshooting](https://django-components.github.io/django-components/0.128/guides/other/troubleshooting/#component-and-slot-highlighting).

Refactor

- Removed use of eval for node validation ([944](https://github.com/django-components/django-components/pull/944))

Perf

- Components can now be infinitely nested. ([936](https://github.com/django-components/django-components/pull/936))

- Component input validation is now 6-7x faster on CPython and PyPy. This previously made up 10-30% of the total render time. ([945](https://github.com/django-components/django-components/pull/945))

0.127

Fix

- Fix component rendering when using `{% cache %}` with remote cache and multiple web servers ([930](https://github.com/django-components/django-components/issues/930))

0.126

Refactor

- Replaced [BeautifulSoup4](https://www.crummy.com/software/BeautifulSoup/bs4/doc/) with a custom HTML parser.
- The heuristic for inserting JS and CSS dependenies into the default place has changed.
- JS is still inserted at the end of the `<body>`, and CSS at the end of `<head>`.
- However, we find end of `<body>` by searching for **last** occurrence of `</body>`
- And for the end of `<head>` we search for the **first** occurrence of `</head>`

0.125

⚠️ Attention ⚠️ - We migrated from `EmilStenstrom/django-components` to `django-components/django-components`.

**Repo name and documentation URL changed. Package name remains the same.**

If you see any broken links or other issues, please report them in [922](https://github.com/django-components/django-components/issues/922).

Feat

- `template_tag` and `BaseNode` - A decorator and a class that allow you to define
custom template tags that will behave similarly to django-components' own template tags.

Read more on [Template tags](https://django-components.github.io/django-components/0.125/concepts/advanced/template_tags/).

Template tags defined with `template_tag` and `BaseNode` will have the following features:

- Accepting args, kwargs, and flags.

- Allowing literal lists and dicts as inputs as:

`key=[1, 2, 3]` or `key={"a": 1, "b": 2}`
- Using template tags tag inputs as:

`{% my_tag key="{% lorem 3 w %}" / %}`
- Supporting the flat dictionary definition:

`attr:key=value`
- Spreading args and kwargs with `...`:

`{% my_tag ...args ...kwargs / %}`
- Being able to call the template tag as:

`{% my_tag %} ... {% endmy_tag %}` or `{% my_tag / %}`

Refactor

- Refactored template tag input validation. When you now call template tags like
`{% slot %}`, `{% fill %}`, `{% html_attrs %}`, and others, their inputs are now
validated the same way as Python function inputs are.

So, for example

django
{% slot "my_slot" name="content" / %}

will raise an error, because the positional argument `name` is given twice.

NOTE: Special kwargs whose keys are not valid Python variable names are not affected by this change.
So when you define:

django
{% component data-id=123 / %}

The `data-id` will still be accepted as a valid kwarg, assuming that your `get_context_data()`
accepts `**kwargs`:

py
def get_context_data(self, **kwargs):
return {
"data_id": kwargs["data-id"],
}

0.124

Feat

- Instead of inlining the JS and CSS under `Component.js` and `Component.css`, you can move
them to their own files, and link the JS/CSS files with `Component.js_file` and `Component.css_file`.

Even when you specify the JS/CSS with `Component.js_file` or `Component.css_file`, then you can still
access the content under `Component.js` or `Component.css` - behind the scenes, the content of the JS/CSS files
will be set to `Component.js` / `Component.css` upon first access.

The same applies to `Component.template_file`, which will populate `Component.template` upon first access.

With this change, the role of `Component.js/css` and the JS/CSS in `Component.Media` has changed:

- The JS/CSS defined in `Component.js/css` or `Component.js/css_file` is the "main" JS/CSS
- The JS/CSS defined in `Component.Media.js/css` are secondary or additional

See the updated ["Getting Started" tutorial](https://django-components.github.io/django-components/0.124/getting_started/adding_js_and_css/)

Refactor

- The canonical way to define a template file was changed from `template_name` to `template_file`, to align with the rest of the API.

`template_name` remains for backwards compatibility. When you get / set `template_name`,
internally this is proxied to `template_file`.

- The undocumented `Component.component_id` was removed. Instead, use `Component.id`. Changes:

- While `component_id` was unique every time you instantiated `Component`, the new `id` is unique
every time you render the component (e.g. with `Component.render()`)
- The new `id` is available only during render, so e.g. from within `get_context_data()`

- Component's HTML / CSS / JS are now resolved and loaded lazily. That is, if you specify `template_name`/`template_file`,
`js_file`, `css_file`, or `Media.js/css`, the file paths will be resolved only once you:

1. Try to access component's HTML / CSS / JS, or
2. Render the component.

Read more on [Accessing component's HTML / JS / CSS](https://django-components.github.io/django-components/0.124/concepts/fundamentals/defining_js_css_html_files/#customize-how-paths-are-rendered-into-html-tags).

- Component inheritance:

- When you subclass a component, the JS and CSS defined on parent's `Media` class is now inherited by the child component.
- You can disable or customize Media inheritance by setting `extend` attribute on the `Component.Media` nested class. This work similarly to Django's [`Media.extend`](https://docs.djangoproject.com/en/5.1/topics/forms/media/#extend).
- When child component defines either `template` or `template_file`, both of parent's `template` and `template_file` are ignored. The same applies to `js_file` and `css_file`.

- Autodiscovery now ignores files and directories that start with an underscore (`_`), except `__init__.py`

- The [Signals](https://docs.djangoproject.com/en/5.1/topics/signals/) emitted by or during the use of django-components are now documented, together the `template_rendered` signal.

Page 2 of 9

Releases

Has known vulnerabilities

Previous Next

Django-components

Page 2 of 9

0.129

0.128

0.127

0.126

0.125

0.124

Page 2 of 9

Links

Releases