The search, answered by Streamlord
Every keystroke is a real request. The server reads the signal the browser sends, searches the documentation, and patches the results into this page. Nothing here is recorded, and there is no JavaScript of ours on the page.
Results …
Type to search the documentation.
Signals
Datastar's own store, rendered by data-json-signals. No code of ours.
The eight patch modes
One endpoint, one word of difference. The field in the stone is there to be lost:
- Write something in the field.
- Press Outer. The sentence above the field changes, and what you wrote stays. That is a morph.
- Press Replace. What you wrote is gone. That is a replacement.
The other modes lay stones around it or take it away. Rebuild the wall to start over.
A stone in the wall. Aim the eight modes at it.
Press a mode. Whether what you wrote survived will appear here, and under it what the server sent: the mode, the selector, and the elements.
A form, checked on the server
The rules live in Kotlin, once. Nothing that arrives over a network may be trusted, so the server has to check anyway, and a second copy of the rules in the browser is a copy that goes out of step.
Nothing has been sent yet. Type, and the server will answer every four hundred milliseconds.
A stream that stays open
One Flow, one connection, twelve seconds. Every number is an element patch and a signal patch on the same open response. Nothing here is polled.
0
Press Start. The server will hold the connection open and write here.
On the wire
The frames behind the last thing you did on this page, whichever demo it was: a search, a muster, a press of a patch mode, or each tick of the counter as it runs. Encoded by the same SseEncoder the golden-file tests verify. Not a description of them. The frames.
Nothing sent yet.