11 Jun 05:59

mikeckennedy

39b697b

v0.6.1 Latest

Latest

Tighten types and docs across the public API

Complete annotations: NoReturn on not_found, fix template_data: dict -> Any,
modern X | None unions, full param/return types everywhere
Cast the response passthrough (pyrefly caught the flask.Response mismatch)
Pin ty and pyrefly to the venv via pyproject [tool.*] config
Examples sections and module docstrings; document decoration-time
template resolution
Export exceptions at the package root with test coverage
README: badges, default naming, Quart note, direct rendering section
Example app: not_found demo with catalog and 404 templates

Assets 2

21 Nov 20:37

mikeckennedy

v0.6.0

a5696bc

v0.6.0

Release v0.6.0

New Feature: Namespace Restriction Control

Added support for controlling Chameleon's namespace restriction, enabling better compatibility with attribute-based JavaScript frameworks like Vue.js and Alpine.js.

What's New

The global_init() function now accepts a restricted_namespace parameter (defaults to True for backward compatibility). When set to False, Chameleon only treats its own namespaces (TAL, METAL, i18n) specially, allowing all other attributes to pass through unchanged.

Usage

import chameleon_flask

# Turn off namespace restriction for Alpine.js/Vue.js compatibility
chameleon_flask.global_init(
    template_folder='templates',
    auto_reload=True,
    restricted_namespace=False  # <-- Enable attribute-based JS frameworks
)

Why This Matters

With restricted_namespace=False:

Chameleon only processes its own namespaces (tal:, metal:, i18n:)
All other attributes like x-data, x-on:click, x-bind:class, @click, :class are left untouched
Perfect for templates using Alpine.js, Vue.js, or other attribute-based frameworks
No need to escape or work around Chameleon's namespace restrictions

Backward Compatibility

This change is fully backward compatible. The default value is True, maintaining the existing behavior unless explicitly changed.

Assets 2

12 Jan 17:31

mikeckennedy

v0.5.1

669af91

v0.5.1

Things are getting stable now.

This release fixes a bug where the status code is not passed as part of the response. For example, the sync version is status code 201 whereas the async one is status code 200 with this bug (now fixed):

@blueprint.post('/saves/new')
@template('saves/partials/card-processing.pt', status_code=201)
def save_new():
   # ...


@blueprint.post('/saves/new')
@template('saves/partials/card-processing.pt', status_code=201)
async def save_new():
   # ...