When rendering a Phlex view from a request with a turbo-frame header, nothing is output

[davekaro]

On phlex-rails main, if a request includes the turbo-frame header, and the rails app renders a Phlex view that renders the turbo frame using turbo_frame_tag output helper, nothing is rendered. This is from the behavior introduced in #154. The issue is because Phlex doesn't render the <turbo-frame> element, it doesn't know about the fragment. Possible solutions include grabbing the id positional arg and putting it in the context.fragments? Same applies for other output helpers that could have an id.

[davekaro]

I created this repo to make sure nothing weird was going on in my app https://github.com/davekaro/test-phlex. It works as is, because it's using the turbo_frame tag. If you uncomment https://github.com/davekaro/test-phlex/blob/main/app/views/posts/show_view.rb#L4 and comment out line 5, this shows it not working. Not sure if helpful for testing.

[davekaro]

Another issue that seems related, if you render a component before the fragment, and that component takes advantage of the fact you can just return a string in the block, then that string is still output in the response. I added this commit https://github.com/davekaro/test-phlex/commit/b7171133e21b37f8b0fd25578b4b4b6980dd9f9c that demonstrates this.

Fixed by phlex-ruby/phlex@1dcd03a

[joeldrapper]

Fixed here 9757231