[](https://opensource.org/licenses/MIT)
[](https://pypi.python.org/pypi/django-render-static/)
[](https://pypi.python.org/pypi/django-render-static/)
[](https://pypi.org/project/django-render-static/)
[](https://pypi.python.org/pypi/django-render-static)
[](http://django-render-static.readthedocs.io/?badge=latest/)
[](https://codecov.io/gh/bckohan/django-render-static)
[](https://github.com/bckohan/django-render-static/actions/workflows/test.yml)
[](https://github.com/bckohan/django-render-static/actions/workflows/lint.yml)
[](https://github.com/psf/black)
# django-render-static
Use Django's template engines to render static files that are collected
during the ``collectstatic`` routine and likely served above Django at runtime.
Files rendered by django-render-static are immediately available to participate
in the normal static file collection pipeline.
For example, a frequently occurring pattern that violates the
[DRY principle](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself) is the presence of defines,
or enum like structures in server side Python code that are simply replicated in client side
JavaScript. Another example might be rebuilding Django URLs from arguments in a
[Single Page Application](https://en.wikipedia.org/wiki/Single-page_application). Single-sourcing
these structures by transpiling client side code from the server side code keeps the stack bone DRY.
**`django-render-static` includes Python to Javascript transpilers for:**
* Django's `reverse` function (`urls_to_js`)
* PEP 435 style Python enumerations (`enums_to_js`)
* Plain data define-like structures in Python classes and modules
(`defines_to_js`)
Transpilation is extremely flexible and may be customized by using override blocks or extending the provided
transpilers.
`django-render-static` also formalizes the concept of a package-time or deployment-time
static file rendering step. It piggybacks off the existing templating engines and configurations
and should therefore be familiar to Django developers. It supports both standard Django templating
and Jinja templates and allows contexts to be specified in python, json or YAML.
You can report bugs and discuss features on the
[issues page](https://github.com/bckohan/django-render-static/issues).
[Contributions](https://github.com/bckohan/django-render-static/blob/main/CONTRIBUTING.rst) are
encouraged!
[Full documentation at read the docs.](https://django-render-static.readthedocs.io/en/latest/)
## Installation
1. Clone django-render-static from [GitHub](http://github.com/bckohan/django-render-static) or install a release off [PyPI](http://pypi.python.org/pypi/django-render-static):
```shell
pip install django-render-static
```
2. Add 'render_static' to your ``INSTALLED_APPS`` :
```python
INSTALLED_APPS = [
'render_static',
]
```
3. Add a ``STATIC_TEMPLATES`` configuration directive to your settings file:
```python
STATIC_TEMPLATES = {
'templates' : [
('path/to/template':, {'context' {'variable': 'value'})
]
}
```
4. Run ``renderstatic`` preceding every run of ``collectstatic`` :
```shell
$> manage.py renderstatic
$> manage.py collectstatic
```
## Usage
### Transpiling Model Field Choices
You have an app with a model with a character field that has several valid choices defined in an
enumeration type way, and you'd like to export those defines to JavaScript. You'd like to include
a template for other's using your app to use to generate a defines.js file. Say your app structure
looks like this::
.
└── examples
├── __init__.py
├── apps.py
├── defines.py
├── models.py
├── static_templates
│ └── examples
│ └── defines.js
└── urls.py
Your defines/model classes might look like this:
```python
class ExampleModel(Defines, models.Model):
DEFINE1 = 'D1'
DEFINE2 = 'D2'
DEFINE3 = 'D3'
DEFINES = (
(DEFINE1, 'Define 1'),
(DEFINE2, 'Define 2'),
(DEFINE3, 'Define 3')
)
define_field = models.CharField(choices=DEFINES, max_length=2)
```
And your defines.js template might look like this:
```js+django
{% defines_to_js modules="examples.models" %}
```
If someone wanted to use your defines template to generate a JavaScript version of your Python
class their settings file might look like this:
```python
STATIC_TEMPLATES = {
'templates': [
'examples/defines.js'
]
}
```
And then of course they would call `renderstatic` before `collectstatic`:
```shell
$> ./manage.py renderstatic
$> ./manage.py collectstatic
```
This would create the following file::
.
└── examples
└── static
└── examples
└── defines.js
Which would look like this:
```javascript
const defines = {
ExampleModel: {
DEFINE1: "D1",
DEFINE2: "D2",
DEFINE3: "D3",
DEFINES: [["D1", "Define 1"], ["D2", "Define 2"], ["D3", "Define 3"]]
}
};
```
### Transpiling Enumerations
Say instead of the usual choices tuple you're using PEP 435 style python enumerations as model
fields using [django-enum](http://pypi.python.org/pypi/django-enum) and
[enum-properties](http://pypi.python.org/pypi/enum-properties). For example we might define a
simple color enumeration like so:
```python
from django.db import models
from django_enum import EnumField, TextChoices
from enum_properties import p, s
class ExampleModel(models.Model):
class Color(TextChoices, s('rgb'), s('hex', case_fold=True)):
# name value label rgb hex
RED = 'R', 'Red', (1, 0, 0), 'ff0000'
GREEN = 'G', 'Green', (0, 1, 0), '00ff00'
BLUE = 'B', 'Blue', (0, 0, 1), '0000ff'
color = EnumField(Color, null=True, default=None)
```
If we define an enum.js template that looks like this:
```js+django
{% enums_to_js enums="examples.models.ExampleModel.Color" %}
```
It will contain a javascript class transpilation of the Color enum that looks
like this:
```javascript
class Color {
static RED = new Color("R", "RED", "Red", [1, 0, 0], "ff0000");
static GREEN = new Color("G", "GREEN", "Green", [0, 1, 0], "00ff00");
static BLUE = new Color("B", "BLUE", "Blue", [0, 0, 1], "0000ff");
constructor (value, name, label, rgb, hex) {
this.value = value;
this.name = name;
this.label = label;
this.rgb = rgb;
this.hex = hex;
}
toString() {
return this.value;
}
static get(value) {
switch(value) {
case "R":
return Color.RED;
case "G":
return Color.GREEN;
case "B":
return Color.BLUE;
}
throw new TypeError(`No Color enumeration maps to value ${value}`);
}
static [Symbol.iterator]() {
return [Color.RED, Color.GREEN, Color.BLUE][Symbol.iterator]();
}
}
```
We can now use our enumeration like so:
```javascript
Color.BLUE === Color.get('B');
for (const color of Color) {
console.log(color);
}
```
### Transpiling URL reversal
You'd like to be able to call something like `reverse` on path names from your client JavaScript
code the same way you do from Python Django code.
Your settings file might look like:
```python
STATIC_TEMPLATES={
'ENGINES': [{
'BACKEND': 'render_static.backends.StaticDjangoTemplates',
'OPTIONS': {
'loaders': [
('render_static.loaders.StaticLocMemLoader', {
'urls.js': '{% urls_to_js %}'
})
]
},
}],
'templates': ['urls.js']
}
```
Then call `renderstatic` before `collectstatic`:
```shell
$> ./manage.py renderstatic
$> ./manage.py collectstatic
```
If your root urls.py looks like this:
```python
from django.contrib import admin
from django.urls import path
from .views import MyView
urlpatterns = [
path('admin/', admin.site.urls),
path('simple', MyView.as_view(), name='simple'),
path('simple/<int:arg1>', MyView.as_view(), name='simple'),
path('different/<int:arg1>/<str:arg2>', MyView.as_view(), name='different'),
]
```
So you can now fetch paths like this, in a way that is roughly API-equivalent
to Django's `reverse` function:
```javascript
import { URLResolver } from '/static/urls.js';
const urls = new URLResolver();
// /different/143/emma
urls.reverse('different', {kwargs: {'arg1': 143, 'arg2': 'emma'}});
// reverse also supports query parameters
// /different/143/emma?intarg=0&listarg=A&listarg=B&listarg=C
urls.reverse(
'different',
{
kwargs: {arg1: 143, arg2: 'emma'},
query: {
intarg: 0,
listarg: ['A', 'B', 'C']
}
}
);
```
### URLGenerationFailed Exceptions & Placeholders
If you encounter a ``URLGenerationFailed`` exception you most likely need to register a placeholder for the argument in question. A placeholder is just a string or object that can be coerced to a string that matches the regular expression for the argument:
```python
from render_static.placeholders import register_variable_placeholder
app_name = 'year_app'
urlpatterns = [
re_path(r'^fetch/(?P<year>\d{4})/$', YearView.as_view(), name='fetch_year')
]
register_variable_placeholder('year', 2000, app_name=app_name)
```
Users should typically use a path instead of re_path and register their own custom converters when needed. Placeholders can be directly registered on the converter (and are then conveniently available to users of your app!):
```python
from django.urls.converters import register_converter
class YearConverter:
regex = '[0-9]{4}'
placeholder = 2000 # this attribute is used by `url_to_js` to reverse paths
def to_python(self, value):
return int(value)
def to_url(self, value):
return str(value)
register_converter(YearConverter, 'year')
urlpatterns = [
path('fetch/<year:year>', YearView.as_view(), name='fetch_year')
]
```
Raw data
{
"_id": null,
"home_page": "https://django-render-static.readthedocs.io",
"name": "django-render-static",
"maintainer": null,
"docs_url": null,
"requires_python": "<4.0,>=3.8",
"maintainer_email": null,
"keywords": "django, static, templates, javascript, url, reverse, defines, transpiler, transpile, enum",
"author": "Brian Kohan",
"author_email": "bckohan@gmail.com",
"download_url": "https://files.pythonhosted.org/packages/b0/0e/e174d7c9a96af4e4a055861d5ef096990d0e36aa0f2183b290b7d5602319/django_render_static-3.1.2.tar.gz",
"platform": null,
"description": "[](https://opensource.org/licenses/MIT)\n[](https://pypi.python.org/pypi/django-render-static/)\n[](https://pypi.python.org/pypi/django-render-static/)\n[](https://pypi.org/project/django-render-static/)\n[](https://pypi.python.org/pypi/django-render-static)\n[](http://django-render-static.readthedocs.io/?badge=latest/)\n[](https://codecov.io/gh/bckohan/django-render-static)\n[](https://github.com/bckohan/django-render-static/actions/workflows/test.yml)\n[](https://github.com/bckohan/django-render-static/actions/workflows/lint.yml)\n[](https://github.com/psf/black)\n\n# django-render-static\n\nUse Django's template engines to render static files that are collected\nduring the ``collectstatic`` routine and likely served above Django at runtime.\nFiles rendered by django-render-static are immediately available to participate\nin the normal static file collection pipeline.\n\nFor example, a frequently occurring pattern that violates the\n[DRY principle](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself) is the presence of defines,\nor enum like structures in server side Python code that are simply replicated in client side\nJavaScript. Another example might be rebuilding Django URLs from arguments in a\n[Single Page Application](https://en.wikipedia.org/wiki/Single-page_application). Single-sourcing\nthese structures by transpiling client side code from the server side code keeps the stack bone DRY.\n\n**`django-render-static` includes Python to Javascript transpilers for:**\n\n* Django's `reverse` function (`urls_to_js`)\n* PEP 435 style Python enumerations (`enums_to_js`)\n* Plain data define-like structures in Python classes and modules\n (`defines_to_js`)\n\nTranspilation is extremely flexible and may be customized by using override blocks or extending the provided \ntranspilers.\n\n`django-render-static` also formalizes the concept of a package-time or deployment-time\nstatic file rendering step. It piggybacks off the existing templating engines and configurations\nand should therefore be familiar to Django developers. It supports both standard Django templating\nand Jinja templates and allows contexts to be specified in python, json or YAML.\n\nYou can report bugs and discuss features on the\n[issues page](https://github.com/bckohan/django-render-static/issues).\n\n[Contributions](https://github.com/bckohan/django-render-static/blob/main/CONTRIBUTING.rst) are\nencouraged!\n\n[Full documentation at read the docs.](https://django-render-static.readthedocs.io/en/latest/)\n\n## Installation\n\n1. Clone django-render-static from [GitHub](http://github.com/bckohan/django-render-static) or install a release off [PyPI](http://pypi.python.org/pypi/django-render-static):\n\n```shell\npip install django-render-static\n```\n\n2. Add 'render_static' to your ``INSTALLED_APPS`` :\n\n```python\nINSTALLED_APPS = [\n 'render_static',\n]\n```\n\n3. Add a ``STATIC_TEMPLATES`` configuration directive to your settings file:\n\n```python\n\nSTATIC_TEMPLATES = {\n 'templates' : [\n ('path/to/template':, {'context' {'variable': 'value'})\n ]\n}\n```\n\n4. Run ``renderstatic`` preceding every run of ``collectstatic`` :\n\n```shell\n$> manage.py renderstatic\n$> manage.py collectstatic\n```\n\n## Usage\n\n### Transpiling Model Field Choices\n\nYou have an app with a model with a character field that has several valid choices defined in an\nenumeration type way, and you'd like to export those defines to JavaScript. You'd like to include\na template for other's using your app to use to generate a defines.js file. Say your app structure\nlooks like this::\n\n .\n \u2514\u2500\u2500 examples\n \u251c\u2500\u2500 __init__.py\n \u251c\u2500\u2500 apps.py\n \u251c\u2500\u2500 defines.py\n \u251c\u2500\u2500 models.py\n \u251c\u2500\u2500 static_templates\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 examples\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 defines.js\n \u2514\u2500\u2500 urls.py\n\n\nYour defines/model classes might look like this:\n\n```python\nclass ExampleModel(Defines, models.Model):\n\n DEFINE1 = 'D1'\n DEFINE2 = 'D2'\n DEFINE3 = 'D3'\n DEFINES = (\n (DEFINE1, 'Define 1'),\n (DEFINE2, 'Define 2'),\n (DEFINE3, 'Define 3')\n )\n\n define_field = models.CharField(choices=DEFINES, max_length=2)\n```\n\nAnd your defines.js template might look like this:\n\n```js+django\n{% defines_to_js modules=\"examples.models\" %}\n```\n\nIf someone wanted to use your defines template to generate a JavaScript version of your Python\nclass their settings file might look like this:\n\n```python\nSTATIC_TEMPLATES = {\n 'templates': [\n 'examples/defines.js'\n ]\n}\n```\n\n\nAnd then of course they would call `renderstatic` before `collectstatic`:\n\n```shell\n$> ./manage.py renderstatic\n$> ./manage.py collectstatic\n```\n\nThis would create the following file::\n\n .\n \u2514\u2500\u2500 examples\n \u2514\u2500\u2500 static\n \u2514\u2500\u2500 examples\n \u2514\u2500\u2500 defines.js\n\nWhich would look like this:\n\n```javascript\nconst defines = {\n ExampleModel: {\n DEFINE1: \"D1\",\n DEFINE2: \"D2\",\n DEFINE3: \"D3\",\n DEFINES: [[\"D1\", \"Define 1\"], [\"D2\", \"Define 2\"], [\"D3\", \"Define 3\"]]\n }\n};\n```\n\n### Transpiling Enumerations\n\nSay instead of the usual choices tuple you're using PEP 435 style python enumerations as model\nfields using [django-enum](http://pypi.python.org/pypi/django-enum) and\n[enum-properties](http://pypi.python.org/pypi/enum-properties). For example we might define a\nsimple color enumeration like so:\n\n```python\nfrom django.db import models\nfrom django_enum import EnumField, TextChoices\nfrom enum_properties import p, s\n\nclass ExampleModel(models.Model):\n\n class Color(TextChoices, s('rgb'), s('hex', case_fold=True)):\n\n # name value label rgb hex\n RED = 'R', 'Red', (1, 0, 0), 'ff0000'\n GREEN = 'G', 'Green', (0, 1, 0), '00ff00'\n BLUE = 'B', 'Blue', (0, 0, 1), '0000ff'\n\n color = EnumField(Color, null=True, default=None)\n```\n\nIf we define an enum.js template that looks like this:\n\n```js+django\n\n {% enums_to_js enums=\"examples.models.ExampleModel.Color\" %}\n```\n\nIt will contain a javascript class transpilation of the Color enum that looks\nlike this:\n\n```javascript\n\nclass Color {\n\n static RED = new Color(\"R\", \"RED\", \"Red\", [1, 0, 0], \"ff0000\");\n static GREEN = new Color(\"G\", \"GREEN\", \"Green\", [0, 1, 0], \"00ff00\");\n static BLUE = new Color(\"B\", \"BLUE\", \"Blue\", [0, 0, 1], \"0000ff\");\n\n constructor (value, name, label, rgb, hex) {\n this.value = value;\n this.name = name;\n this.label = label;\n this.rgb = rgb;\n this.hex = hex;\n }\n\n toString() {\n return this.value;\n }\n\n static get(value) {\n switch(value) {\n case \"R\":\n return Color.RED;\n case \"G\":\n return Color.GREEN;\n case \"B\":\n return Color.BLUE;\n }\n throw new TypeError(`No Color enumeration maps to value ${value}`);\n }\n\n static [Symbol.iterator]() {\n return [Color.RED, Color.GREEN, Color.BLUE][Symbol.iterator]();\n }\n}\n```\n\nWe can now use our enumeration like so:\n\n```javascript\nColor.BLUE === Color.get('B');\nfor (const color of Color) {\n console.log(color);\n}\n```\n\n### Transpiling URL reversal\n\nYou'd like to be able to call something like `reverse` on path names from your client JavaScript\ncode the same way you do from Python Django code.\n\nYour settings file might look like:\n\n```python\n STATIC_TEMPLATES={\n 'ENGINES': [{\n 'BACKEND': 'render_static.backends.StaticDjangoTemplates',\n 'OPTIONS': {\n 'loaders': [\n ('render_static.loaders.StaticLocMemLoader', {\n 'urls.js': '{% urls_to_js %}'\n })\n ]\n },\n }],\n 'templates': ['urls.js']\n }\n```\n\nThen call `renderstatic` before `collectstatic`:\n\n```shell\n$> ./manage.py renderstatic\n$> ./manage.py collectstatic\n```\n\nIf your root urls.py looks like this:\n\n```python\nfrom django.contrib import admin\nfrom django.urls import path\n\nfrom .views import MyView\n\nurlpatterns = [\n path('admin/', admin.site.urls),\n path('simple', MyView.as_view(), name='simple'),\n path('simple/<int:arg1>', MyView.as_view(), name='simple'),\n path('different/<int:arg1>/<str:arg2>', MyView.as_view(), name='different'),\n]\n```\n\nSo you can now fetch paths like this, in a way that is roughly API-equivalent\nto Django's `reverse` function:\n\n```javascript\nimport { URLResolver } from '/static/urls.js';\n\nconst urls = new URLResolver();\n\n// /different/143/emma\nurls.reverse('different', {kwargs: {'arg1': 143, 'arg2': 'emma'}});\n\n// reverse also supports query parameters\n// /different/143/emma?intarg=0&listarg=A&listarg=B&listarg=C\nurls.reverse(\n 'different',\n {\n kwargs: {arg1: 143, arg2: 'emma'},\n query: {\n intarg: 0,\n listarg: ['A', 'B', 'C']\n }\n }\n);\n```\n\n### URLGenerationFailed Exceptions & Placeholders\n\nIf you encounter a ``URLGenerationFailed`` exception you most likely need to register a placeholder for the argument in question. A placeholder is just a string or object that can be coerced to a string that matches the regular expression for the argument:\n\n```python\nfrom render_static.placeholders import register_variable_placeholder\n\napp_name = 'year_app'\nurlpatterns = [\n re_path(r'^fetch/(?P<year>\\d{4})/$', YearView.as_view(), name='fetch_year')\n]\n\nregister_variable_placeholder('year', 2000, app_name=app_name)\n```\n\nUsers should typically use a path instead of re_path and register their own custom converters when needed. Placeholders can be directly registered on the converter (and are then conveniently available to users of your app!):\n\n```python\nfrom django.urls.converters import register_converter\n\nclass YearConverter:\n regex = '[0-9]{4}'\n placeholder = 2000 # this attribute is used by `url_to_js` to reverse paths\n\n def to_python(self, value):\n return int(value)\n\n def to_url(self, value):\n return str(value)\n\n\nregister_converter(YearConverter, 'year')\n\nurlpatterns = [\n path('fetch/<year:year>', YearView.as_view(), name='fetch_year')\n]\n```\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Use Django's template engine to render static files at deployment or package time. Includes transpilers for extending Django's url reversal and enums to JavaScript.",
"version": "3.1.2",
"project_urls": {
"Homepage": "https://django-render-static.readthedocs.io",
"Repository": "https://github.com/bckohan/django-render-static"
},
"split_keywords": [
"django",
" static",
" templates",
" javascript",
" url",
" reverse",
" defines",
" transpiler",
" transpile",
" enum"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "4894d895a2cfb2de296c44aee09ab36dc42bb6dee6ceebed5823f109c621f727",
"md5": "4f8dc4ffb639fe724710553d4831555b",
"sha256": "fd5e2be0d609e8bb3f398be4745bf8581a7d02da2547537c47ca37eedbca1125"
},
"downloads": -1,
"filename": "django_render_static-3.1.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "4f8dc4ffb639fe724710553d4831555b",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "<4.0,>=3.8",
"size": 65868,
"upload_time": "2024-07-18T15:36:46",
"upload_time_iso_8601": "2024-07-18T15:36:46.189802Z",
"url": "https://files.pythonhosted.org/packages/48/94/d895a2cfb2de296c44aee09ab36dc42bb6dee6ceebed5823f109c621f727/django_render_static-3.1.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "b00ee174d7c9a96af4e4a055861d5ef096990d0e36aa0f2183b290b7d5602319",
"md5": "f21fc9ca79756303ad0e5e91cadfa420",
"sha256": "48d2cd6dc2b53848cc2efa52de50abda44c1b5721d91185719925164f59d123b"
},
"downloads": -1,
"filename": "django_render_static-3.1.2.tar.gz",
"has_sig": false,
"md5_digest": "f21fc9ca79756303ad0e5e91cadfa420",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "<4.0,>=3.8",
"size": 57912,
"upload_time": "2024-07-18T15:36:47",
"upload_time_iso_8601": "2024-07-18T15:36:47.955627Z",
"url": "https://files.pythonhosted.org/packages/b0/0e/e174d7c9a96af4e4a055861d5ef096990d0e36aa0f2183b290b7d5602319/django_render_static-3.1.2.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-07-18 15:36:47",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "bckohan",
"github_project": "django-render-static",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "django-render-static"
}
JSON
