3 ms·
Take a look at Prismatic's om-tools(1). It adds a defcomponent macro that removes a lot of boilerplate. 1)https://github.com/Prismatic/om-tools https://github
by bkurtz13 12y ago
Take a look at Prismatic's om-tools(1).
It adds a defcomponent macro that removes a lot of boilerplate.
1)https://github.com/Prismatic/om-tools https://github.com/Prismatic/om-tools
- astine 12y agoI actually used om-tools before I switched to reagent. Om-tools does cut out a lot of boilerplate, but I like reagent's approach more from the outset. One thing I found confusing about Om with or without om-tools, was how to manage communication between the components. The tutorials used a lot of core.async to manage that but it was clearly unnecessary. In Reagent you can pass arbitrary parameters to component functions. You don't have to make each component correspond to a branch on your applications state's tree. You can, and you can use a cursor analog if you want to, but you don't have to and I found that very freeing.