Components with Phlex in Rails

[@johncjensen]

Definitely very intriguing 🤔. Was great seeing some of the potential gotcha issues with needing to pass in instance variables or custom helpers.

[@charb423]

This was an informative video. Also seeing how you walked through a gotcha really helped me understand why you got the error and how to fix it. This definitely made me sub and feel like i made the right decision on learning Ruby and the Rails framework. It is fun but when you run into a gotcha, can have you go crazy a bit especially when you are new to the syntax and flow of things.

[@GorailsTV]

Debugging is probably the most important skill to learn!

[@WickedAyman]

Looking for an Inertia Rails tutorial :))

[@CristianMolina]

I really prefer ruby code for views and components to the mixed mess of templating. If you worked with desktop UI toolkit before is great to work this way with web apps, too..

[@okoni.alesre]

Покажите пожалуйста больше примеров использования Phlex, чтобы было 100% отказ от ".erb", например как использовать в broadcast replace в моделях after_commit, вывод в collections и т п

[@Frexuz]

Nice video and explanations. But I think that I prefer the view_components gem. I guess it's just subjective. You say that you prefer to have the view/template stuff in ruby, and I still prefer them in .html.erb files. It also screws with many html-formatters, or for example, tailwind-css-class-sorter plugins, that just don't pick up .rb files. view_components have a similar way of encapsulating the ruby parts for the components. Anyway, its subjective ;)

[@quickchuck]

agreed!