The Code component would do a poor job at nesting code in a body. The point of this project is to make it easy to generate code through an AST, hence the <Code /> "catch call".
Great feedback. The points you make are good. Listed below are the reasons I chose to go with react.
1. I'm getting my feet wet with React rendering (I will be building a full react renderer in the future for another project)
2. It may be useful in the future for dynamic code editing (not sure but a possible use case)
3. Though react really shines in the render lifecycle, it does provide a nice pattern for building components. I see this project being used as a way to componentize composable code generators and snippets.
> I see this project being used as a way to componentize composable code generators and snippets.
You can do this without React though, using only JSX. I've implemented this pattern in a library (not open source yet) that builds in a lot of these composition patterns (pass children as child or prop, etc) so that you can use it in familiar ways while still just being JSX.
