Now that is a lot of work if I had to make each and every one of those changes by hand. I also had hundreds of soft warnings that could be as simple as an unused but declared variable or a typo. I also had 50 or so warnings that don’t stop the website from working but could very well be bugs or potential bugs due to depreciated features that could very well disappear in newer versions of PHP. Yes, I should have been listening to the warnings regarding depreciated code.
#Codekit para windows code#
I had 20+ PHP code errors that broke the website caused by backward-incompatible changes in PHP 8. I then ran an inspection on the entire project which tells PhpStorm to run Linters on the HTML, Sass, Javascript, and PHP. Its previous settings were for php7.4 and ES4. I changed a couple of settings, telling it that I was now using PHP 8 and ES6. Now, I needed to fix my code to get my website back up so I did the smart thing… I stared at the code, tearing my hair out, not knowing where to start or why it didn’t work, and started screaming. But PhpStorm does provide most of the tools that you need on a daily basis.
#Codekit para windows full#
It is an integration tool, meaning certain capabilities do need to be installed separately on your Mac through tools like XCode, Homebrew, or MAMP to get the full experience. After a long search several years ago, I settled on PhpStorm by Jet Brains.Īn integrated development environment means it incorporates all the functionality of all those tools I mentioned, adds a bunch more capabilities, and provides a single window where I can do it all. The crazy part is that I don’t need any of them running technically, not when I have an IDE (Integrated Development Environment). Looking at the programs running on my Mac right now sits BBEdit (which is always running), CodeKit for Sass, SourceTree for git, iTerm for command line where I use Vi (well, Vim), git, sass, ESLint, composer, php, shell scripts, etc, etc, ad nauseum. And that is the problem, code that was written correctly in version 5 and acceptable in version 7 suddenly didn’t work at all in PHP 8. So, yeah, the PHP code has a lot of kruft in it, just like me. It went through rewrites for each successive version, including a brief dalliance with the never-released version 6. One of my sites is based on my own library of PHP code which can be traced all the way back to code I wrote in PHP version 3. That sounds great and all, but PHP 8 does break older code. I decided to simplify my life by using just version 8 of PHP instead of running three different versions: 5, 7, and 8. So I spun up a brand new server without all the kruft. My web server out in the cloud was getting old, cranky, and needing to be retired, like me. I had a problem caused by another problem. An IDE is an integrated development environment and can be real handy. I thought I might throw in my 2 cents regarding a handy tool for coding, an IDE called PhpStorm by Jet Brains. As is typical of me, I have been in stealth mode, supporting you through your product links. Hi Allison and fellow Castaways, long-time listener to the Podfeet family of podcasts and even longer-time developer.
0 kommentar(er)
