-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Tags #46
Comments
Hi Sam, |
Hey r0man, I'd replace https://github.com/r0man/sablono/blob/master/src/sablono/compiler.clj#L72 that way the user could extend it to different tags. |
Hi Sam, makeing react-fn a multimethod is not a big deal. However, I Roman |
Okay, I should have some time to play with this in the next week or so. Thanks! |
Updates? |
Haven't worked on this, but converting that function to a multimethod should do it easily. |
I'd also love to be able to plug custom element tags into sablono. If this is hung up on deciding on a name, how about |
I think it's just hung up on someone coding up the multimethod implementation. I'm just not using sablono in my work, so haven't gotten around to it. — On Fri, Jul 31, 2015 at 4:00 PM, Darrick Wiebe [email protected]
|
I would really like this feature because then you can plug-in different renderers and do things closer to jsx: https://react.semantic-ui.com/views/card#card-example-card
|
I'm in love with the idea of allowing qualified keywords as sablono hiccup tag names, to call constructor functions but there is a big caveat: the sablono interpreter + advanced optimization: Since clojurescript function names are subject to renaming, but keywords aren't, the interpreter won't be able to construct such elements, unless all used constructor functions are marked This is really sub-optimal, but maybe rum and om can be persuaded to change their |
I know it explicitly says NOT to do this in the README... BUT, let me make the pitch.
I've written a bunch of components in Om-Bootstrap that could easily be hooked into Sablono's renderer, if I were able to extend specific (namespaced) keywords in the markup to call out to my om-bootstrap components.
For example,
::b/button
would pass the options and children intoom-bootstrap.button/button
.What do you think? Is this a feature you guys would be interested in?
The text was updated successfully, but these errors were encountered: