Cameron

@yogeshjain999 So you pass the default layout as the fallback theme?

@yogeshjain999 That being said though.... If I have: ~~~ theme :theme_resolver private def theme_resolver 'a_theme_that_doesnt_exist' || 'a_theme_that_does_exist' || 'application' end ~~~ I'm finding that instead of it falling back to...

@yogeshjain999 The theme may exist but the view for that particular request may not.

In order to get the fallback theme to work I had to do: ~~~ before_action :fallback_theme def fallback_theme self.prepend_view_path 'app/themes/fallback_theme/views' end ~~~

It also turns out that it doesn't actually use the fallback string: ~~~ def theme_resolver params[:theme] || 'I CAN PUT ANYTHING HERE' end ~~~ So it would be good to...

After playing around with this I've come to find that building a Rails Engine is probably a better way forward as then it means you can have everything a Rails...

Also just run into this issue and couldn't understand why the iframe was missing until I came across this discussion. Is there a way to patch this manually until a...

@ElMassimo I've seen that this is merged now, but still not getting the iframe in the Storybook output after updating to the latest version of this gem... do I need...

@eriknygren Yeah I'm seeing the same issue as mentioned in the other conversation with the `iframe.html` being added into `/public/vite` folder instead of `storybook-static`. The comments seem to still suggest...

I've seen some stuff like: http://www.roguesavant.com/bigscreen/ and https://github.com/thibauts/node-castv2-client So it seems like it's perfectly possible.