feat: Add a method to render a component to string

[jaredcwhite]

Summary

The ability to render a component in any codepath, not just in views.

Something like:

output = Shared::Navbar.new(resource:).render_to_string
puts output

Unresolved Questions

How best to "boot up" a skeleton view context from which a component render can occur…any problematic edge cases? Performance issues? * Note: this is already done from dynamic Roda routes…just need to extract/generalize maybe…

[andrewmcodes]

I'll be watching closely.

A usecase that comes to mind immediately is using this with something like Storybook, specifically @storybook/html.

Not precise code but I think a primitive example would look like:

storiesOf('Callout', module)
  .add('default', () => '<%= Callout.new(type: :alert, message: "A test callout").render_to_string %>')

And then you can just let Bridgetown convert the ERB. which will build your stories when your components change 👏

[jaredcwhite]

@andrewmcodes That's a pretty neat idea!

[jaredcwhite]

(Pushing this off the 1.2 release…there's a bit of a larger refactor I'd like to do around template/component rendering and I want to give that my full attention rather than rush it.)