Sure. I added a simple selector in app.css which targets “button[data-on]”. When the LiveView state flips to true for the button that style takes over.
Hi Shubhi, I talk about this a bit around 12:50. The key is to make sure you have a value for "win" in your socket assigns. That way it can be referenced in the template and in other event handler functions. In your template you can use standard EEx logic blocks like You won or the more compact You won Let me know if you need more help!
@@headwayio 1.7 introduces a few changes that would by necessity alter the tutorial. For one thing, Tailwind comes pre-configured with 1.7, so that part of the video would ago away. I'm not positive, but I think layouts have changed a bit, which might also necessitate a tutorial change.
Great feedback! You're right about Tailwind and yes there are some minor layout changes coming with 1.7. The majority of what we covered should still be applicable but maybe we can add a disclaimer to skip the Tailwind stuff after 1.7
Thanks, Thiago! The code completion is done with the Elixir LS plugin for Neovim (VS Code has a similar plugin). I also did some video cuts here and there to eliminate some unnecessary typing.
in the video you just mentioned that you updated the css in order to color the buttons when clicked 07:52. how exactly did you go about doing that.
great job dude. I learned a ton.
Glad to hear it!
Thanks For Your Video I am The Beginner of the Phoenix Its Very Useful Me
Good to hear! Happy to help.
In the video you said that you modified the css to toggle the background color. I don't know how you did this. Can you explain?
Sure. I added a simple selector in app.css which targets “button[data-on]”. When the LiveView state flips to true for the button that style takes over.
Great video dude love it ❤
This is amazing! How do you auto-close the HTML tags? Could you please share your neovim config?
Hey thanks! We’ll have Jesse get back to you with an answer.
I've tried to implement this game, but it doesn't show "You won" when the game is completed, how can I figure it out?
Hi Shubhi, I talk about this a bit around 12:50. The key is to make sure you have a value for "win" in your socket assigns. That way it can be referenced in the template and in other event handler functions. In your template you can use standard EEx logic blocks like You won or the more compact You won Let me know if you need more help!
@@hixsonj thanks alot! I'll let you know if I need some more guidance on this topic, and thanks again for helping me out :))
Since your tutorial is new, it would have been useful to have shown it for Phoenix 1.7. As far as I can see there aren't any tutorial for this yet.
Thanks for the feedback Charles. Jesse should be able to comment on this next week. What about 1.7 would you have liked to see?
@@headwayio 1.7 introduces a few changes that would by necessity alter the tutorial. For one thing, Tailwind comes pre-configured with 1.7, so that part of the video would ago away. I'm not positive, but I think layouts have changed a bit, which might also necessitate a tutorial change.
Great feedback! You're right about Tailwind and yes there are some minor layout changes coming with 1.7. The majority of what we covered should still be applicable but maybe we can add a disclaimer to skip the Tailwind stuff after 1.7
Very powerful
Hi, are you using what to auto complete your code? Awesome video btw.
Great question, and thanks for the feedback! I'll connect with Jesse so he can jump in here and answer your question.
Thanks, Thiago! The code completion is done with the Elixir LS plugin for Neovim (VS Code has a similar plugin). I also did some video cuts here and there to eliminate some unnecessary typing.