You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Dataflow uses htl for the html and svg builtin cells, which offers much more functionality than the current builtin html and svg cells in the standard library.
However, it still uses the default markdown builtin md, which I find a little bit awkward. I'm not too sure how to improve it, but here's a few things I've always found annoying with the md builtin, which would be nice to fix:
// #1 tablesmd`|These|columns|are|annoying|to|type|-|-|-|-|-|-${data.map(d=>{returningastringthatgetsconcatenatingintomarkdownwhichcompilestohtml,howweirdreturn`|${d.i}|${d.hate}|${d.this}`})}`// #2 no plugins, like checkboxes or anythingmd`todo list- [ ] this don't work${customCheckbox("you have to build your own custom html component")}`
Then again, markdown parsing doesn't sound too fun, it would probably be backwards incompatible, and doesnt feel too high of a priority
The text was updated successfully, but these errors were encountered:
Currently, Dataflow uses htl for the
html
andsvg
builtin cells, which offers much more functionality than the current builtinhtml
andsvg
cells in the standard library.However, it still uses the default markdown builtin
md
, which I find a little bit awkward. I'm not too sure how to improve it, but here's a few things I've always found annoying with themd
builtin, which would be nice to fix:Then again, markdown parsing doesn't sound too fun, it would probably be backwards incompatible, and doesnt feel too high of a priority
The text was updated successfully, but these errors were encountered: