RatingInput¶
Accessible 1..n rating radios.
| Import | from hedron import RatingInput |
| Distribution | hedron |
| Backend activity | No |
| Normal render mode | RenderMode.FRAGMENT |
Live demo¶
The preview is a local docs simulation (not a running Hedron server). Interactive demos show a “Simulated HTMX” trace when applicable.
Basic use¶
Compose under Page for full documents, or return from a fragment route for HTMX swaps.
How it works¶
Phase 0.15 surface. Prefer native HTML semantics and ordinary HTTP actions.
This component's core behavior is server-rendered HTML and does not require a browser runtime. The preview is ordinary semantic HTML, so keyboard, form, link, and disclosure behavior comes from the platform.
Constructor and parameters¶
RatingInput(name: 'str', legend: 'str', *, maximum: 'int' = 5, value: 'int | None' = None, id: 'str | None' = None, required: 'bool' = False, class_: 'str | None' = None, mark: 'str | None' = None, **kwargs: 'object') -> 'None'
| Parameter | Type | Meaning |
|---|---|---|
name |
str |
Form control name submitted with the request. |
legend |
str |
Accessible group legend for related controls. |
maximum |
int |
Upper bound for progress or rating scales. Default: 5. |
value |
int | None |
Current control value. Default: None. |
id |
str | None |
Optional DOM id. Default: None. |
required |
bool |
Whether the control must be filled before submit. Default: False. |
class_ |
str | None |
Optional CSS class string (class in HTML). Default: None. |
mark |
str | None |
Optional stable test mark (data-hedron-mark). Default: None. |
Composition and backend behavior¶
Keep RatingInput at the smallest semantic boundary. Fragment routes should return only
the replaced region and preserve stable target IDs across success, validation, empty,
loading, and error responses.
RatingInput participates in interaction markup. Pair it with an explicit @app.action POST (and CSRF) when the control mutates state.
Accessibility¶
Keyboard and screen-reader operable; no-JS fallback required where interactive.
Security¶
Escaping and SafeUrl / TrustedHtml are framework concerns; authorization and data
exposure remain application code. Redact secrets before rendering.
Common mistakes¶
- Do not treat client-only hints (geolocation, browser storage) as authorization.
- Do not copy docs-preview JavaScript into an application server.