15:50 I really don't understand why touch: true on the relationship would cause the posts to re-render. Very confusing API. Why `turbo_stream_from @user` causes the list of @posts to re-render?
touch: true updates the timestamp column on the associated model which then triggers a morph type of response. Assuming you're subscribed to updates using the "turbo_stream_from" helper method, rails should tap into those streams and using morphing to update the page. It's pretty magical and I agree it's tough to follow. I'm still trying to wrap my head around it myself.
Super cool feature. Thats a bit pity to see it relates on timestamps of a parent record when we talk about lists. Because on big projects there are usually at least a few after update callbacks. On the other hand, it should rely on something and updated at field sounds reasonable. However, I'd love to see it configurable in the future
Mostly just how I had it in my notes for the blog post. I'm not 100% sure but the route I chose uses a dedicated gem (tailwind-rails) and the app creation route uses postcss.
This is amazing..Thanks to all the creators and contributors to Ruby on Rails..
15:50 I really don't understand why touch: true on the relationship would cause the posts to re-render. Very confusing API. Why `turbo_stream_from @user` causes the list of @posts to re-render?
touch: true updates the timestamp column on the associated model which then triggers a morph type of response. Assuming you're subscribed to updates using the "turbo_stream_from" helper method, rails should tap into those streams and using morphing to update the page. It's pretty magical and I agree it's tough to follow. I'm still trying to wrap my head around it myself.
Hey, which icon extension do you use for vs code? I really like how it looks
Super cool feature. Thats a bit pity to see it relates on timestamps of a parent record when we talk about lists. Because on big projects there are usually at least a few after update callbacks. On the other hand, it should rely on something and updated at field sounds reasonable. However, I'd love to see it configurable in the future
Totally agree 👍
So, people finally found morphdom.. Nice.
Why do you install tailwind after app creation instead of create app with tailwind framework?
Mostly just how I had it in my notes for the blog post. I'm not 100% sure but the route I chose uses a dedicated gem (tailwind-rails) and the app creation route uses postcss.
😎
what is yjit and how to install it's
Just In Time - it is built into Ruby 3.1. You could just manipulate its configuration
@@sumskyi thank you