Proposal for a conference talk: How to configure #PHPStorm and all its tooling extensions (xdebug, phpstan, php-cs-fixer, etc.) to use a docker container consistently.
#PhpStorm 2023.2 is here. And it comes with so many really nice new features. Used the preview version of it. You now have native support for #Laravel Pint, an #AI Assistant whose integration is nice, many little UI improvements and so much more. Time to update – or to try it out. Read more about all the new features here: https://blog.jetbrains.com/phpstorm/2023/08/phpstorm-2023-2-is-now-available/#PHP
They use #OpenAI, which means my GitHub OSS has almost certainly been used in training data.
They rely on OpenAI's promise to not ingest any code that is used for "context".
They specifically do not disclaim that their tool could result in me violating someone else's copyright, and they could suggest the same code to someone else, too.
Uninstall this crap, now. It's dangerous and irresponsible
it´s a minor update and it includes a host of bug fixes and quality-of-life improvements.
Here are the most notable changes and bug fixes in this build:
Fix: Setting Sync sync failed. couldn't get settings from server: Authentication required [IDEA-343073]
Fix: Redshift: Unable to see external Datashare databases in Database Explorer [DBE-18822]
The full list of changes in PhpStorm 2023.3.4 is available in the release notes.
feature request for PhpStorm: when the break points are muted, please change the background color of the dubug console, and display a message “break points are muted” above the debug console.
I just lost 30 minutes because i couldn’t figure out why Step Debugging wasn’t working. I’m certain that’ll happen again. Please JevBrains - you’re my only hope
Is there an annotation I can add to a class stub that will tell #PhpStorm that a readonly property is most certainly set in the constructor, so that PhpStorm quits complaining that “Typed property ‘foobar’ might be uninitialized?” #PHP
#PhpStorm needs to add little “play” buttons next to each of the #PHPUnit TestWith attributes.
Along these same lines, when I have a base test case that uses a data provider defined in child test classes, PhpStorm should be able to figure out that the method in the child is a data provider and add “play” buttons there, as well.
Is it just me or is #phpstorm getting worse by the day?
I'm runnig 2024.1 (Build #PS-241.14494.237, built on March 27, 2024) but have to constantly restart the IDE to fix bizarre errors like PHPStorm claiming a property or parameter isn't used while highlighting the very use a line later, inconsistently resolving asserts with instanceof checks - e.g. claiming a method doesn't exist in the class referenced in a different assert and not seeing a parameter that is clearly there... #fail#ensh11n
@blindcoder If you cut out the code and paste it in again, does anything change? I have problems with #PHPStorm myself with the more recent versions, sometimes their #Intellisense (code highlighting, error reporting, warnings, refactorings etc.) seems to get stuck in a certain state, false positives or false negatives are the consequence. So I fix a problem which is underlined red and afterwards the underline stays in.
I as well tinker around with the #copilot plugin.
Interact with Docker containers without leaving PhpStorm (dev.to)
In the previous article, I wrote about a particular setup you can use to configure Docker on WSL...
Docker on WSL with PhpStorm - Best of both worlds (dev.to)
Most of you are aware that using Docker locally on Windows with Hyper-V enabled can be really slow...
How to Compare Files and Sync Changes using PhpStorm (www.webwash.net)
Did you know you can compare and sync files directly in PhpStorm.