Hiccdown Development Notes
Notes about developing the Ruby gem Hiccdown.
Log in or sign up to participate in this discussion.
With an account, you can revise, criticize, and comment on ideas, and submit new ideas.Hiccdown should have support for ids and class names in the tag symbol. Like Hiccup.
[:'div#my-id.my-class.another-class']# => <div id="my-id" class="my-class another-class"></div>
It should also allow mixing:
[:'div#my-id.my-class.another-class', {id: 'override', class: 'additive'}]# => <div id="override" class="my-class another-class additive"></div>
In other words, the id from the hash would override the id from the symbol, and the class from the hash would be added to the classes from the symbol.
Hiccdown is bug-free.
Is there a way to teach user-built helpers how to process Hiccdown? Or maybe intercepting capture already took care of this?
Redirects result in two additional requests, the first of which is a turbo-stream request that renders nothing, thus (presumably) prompting the browser to make another request for the same resource.
Use frame layout for turbo frame requests? https://discuss.rubyonrails.org/t/the-right-way-to-override-render-method/84765/2
Some Reagent-like way to make things reactive using proc as first element? And then the server keeps track of which procs have been rendered, which items have changed, and re-renders that part of the template in a turbo stream?
When an empty block is passed to render, it results in an empty tag '<>'