@calebporzio So many thoughts to share. tl;dr this is so good! Getting to witness the zoomed-out process front to back is even more valuable than understanding all the details bit by bit. I would pay for a series of sped-up overview vids like this, dope.
@jasonlbeggs@jordanpittman@mattstauffer@johnmkoster Iโve succeeded in tricking VSCode into thinking Blade is HTML before but then ran into issue where commented code defaults to <!โ โ> instead of {{โ โ}} and messes with Livewire functionality.
Have you experienced this and/or solved for it w/ VSCode before?
@nicknisi Cool! Cheers to high speeds and reliable service ๐ป
Cox claimed they were installing fiber in my neighborhood (via multiple visits from contractors marking buried lines) but no further word in months ๐คท๐ปโโ๏ธ
@seb_sebsn Iโm guessing thatโs a product misunderstanding. It reminds me of the scenario where @taylorotwell has had to repeatedly explain that โit doesnโt make any sense to compare Livewire and Inertiaโ (despite the fact that seems obvious to many people already familiar w/ the tooling)
Much respect to PHPstorm but that is not an avenue Iโm interested in exploring (all other day job and side project work in any lang/framework is happily done in VSCode)
What VSCode extensions or settings do TALL stack @laravelphp developers use/love/recommend?
Iโve spent a lot of time working with Laravel (using Vue, Raact, others) but relatively little time working in Blade files. What am I missing as it relates to VSCode specifically?
Specifically seeking anything which might help improve:
- syntax highlighting
- blade.php formatting
- commenting out code using default shortcut (without causing Livewire to freak out and botch rendering)