Type-aware value rendering

ChirpUI'sdescription_itemmacro automatically detects Python types and applies the right CSS variant. Pass raw values from your handlers—no string conversion needed.

How it works

When you calldescription_item(term, detail) without type=, the macro applies the value_typefilter to infer the type:

Explicittype= overrides auto-detection. Use it when you need a specific variant (e.g. type="url") even when the value is a string.

Usage

Pass raw types from handlers

# In your page handler:
return {
    "workspace_root": workspace_root,  # Path, not str(workspace_root)
    "project_initialized": project_initialized,  # bool, not "Yes"/"No"
}

In templates

{% from "chirpui/description_list.html" import description_item %}

{{ description_item("Workspace path", workspace_root) }}
{{ description_item("Project initialized", project_initialized) }}

No type= needed. The macro detects Path and booland applies the right class and rendering.

With items list

{% set items = [
    {"term": "Workspace", "detail": workspace_root},
    {"term": "Ready", "detail": True},
] %}
{{ description_list(items=items) }}

Type is auto-detected from each item's detail when typeis omitted.

Override when needed

{{ description_item("Config URL", config_url, type="url") }}

Use type=when the value is a string but you want a specific variant (e.g. URL styling).

Supported types

Kidatypeoffilter

For generic type names (e.g. debugging), you can use Kida'stypeoffilter:

{{ value | typeof }}

Returns "bool", "int", "float", "path", "list", "dict", "none", or "str" (with bool checked before int).

Best practices

1. Pass raw types — Avoidstr()in handlers for Path and bool. Let templates handle display.
2. Usedescription_item — For key-value pairs, prefer the macro over hand-written markup so type-aware styling applies.
3. Override when needed — Usetype="url"for URLs that arrive as strings.