Use runnable code in README snippets #3
Conversation
| Button("My Button", **data.on("click", "console.log('clicked')").debounce(1000).stop) | ||
| # After next release of FastHTML you don't have to unpack the datastar helpers e.g. | ||
| Button("My Button", data.on("click", "console.log('clicked')").debounce(1000).stop) | ||
| Button(data.on("click", "console.log('clicked')").debounce(1000).stop)("My Button") |
There was a problem hiding this comment.
Is this a new format? I don't see any documentation about it. (Nor for the dictionary form we used above for that matter.)
There was a problem hiding this comment.
Attributes first has actually been in FastHTML for a while, but I do not think it's documented anywhere. The only place I could find it was inside this idiomatic FastHTML app Jeremy Howard recently rewrote:
https://github.com/AnswerDotAI/fasthtml/blob/main/examples/adv_app.py
It's some people's preference because it looks closer to HTML, but the default is the pythonic way of passing everything as arguments to a FT function.
The dict method is demoed here:
https://fastht.ml/docs/explains/explaining_xt_components.html#attributes
|
Unrelated to your change I started thinking we should start off with an example that uses all the nice features. Right now we start off with an example than shows you barely have to use any of the features the SDK gives you. 😆 |
|
You're right I think that the first example should probably demonstrate everything that is on offer in one block, and then break down all of the components afterwards. |
2 participants
I think copy-pastable code is a nice experience for getting started with a library, even when it's not applicable to the particular framework I'm using (everything is pretty generalizable anyway), so I made the few snippets in the readme closer to runnable code. The first snippet can be run if dependencies are present.
I also modified the syntax of the FastHTML data.on attribute generation (I figure since the release is out this also doesn't need the disclaimer anymore).