Suggestion: shorthand for common components about crochet HOT 1 OPEN

There's a thread on the Zulip where we were wrestling with this very question. It's a case where I think real keyword arguments would come in handy.

The reason to use this builder pattern is consistency with the case where you are supplying (in many cases optional) attributes. Another alternative that was discussed is a params struct with { .. Default::default() } to represent optionality. Unfortunately, that also is an unwelcome amount of noise.

Styling is another complex question, and one I'd like to tackle at some point after feeling more confident about the basic reactive architecture. CSS is the devil we know: powerful, and very widely used, but I'm not sure very many people would argue it's the right way to do this. But yes, if there is an out-of-band channel for styling, it might take off some of the pressure to supply attributes when building the view tree.

from crochet.