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
I've been getting this popup in my #PhpStorm for the last couple of days.
Obviosuly I know why this is happening (NextDNS blocking the request) but I can't see any other info, such as which component is making that call, which URL is actually being requested etc.
Nor is there a way to stop this (clicking 'Reject' just makes the thing pop back up a few seconds later).
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
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.
@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.
This is happening so so much these days. It’s really getting beyond annoying. Today I had to actually quit phpstorm twice, because it was stuck in a false negative state.
I wish they’d just spend some time improving/fixing this, instead of inventing ‘new terminals’, AI, or whatever else
so
discovered that if you're using advanced #docker features in #phpstorm, you might want to make sure you are no longer using docker-compose (you should be using docker compose instead)
piece of cake to deal with this...
change the path to your docker compose executable (see screenshot) and you're all set
GitHub In-Editor Reviewing. Vielleicht erleichtert mir das die Crappyness des GitHub UIs?
Sticky Lines um beim scrollen den Methoden/Funktionskopf als feststehende Zeile hat, die beim wegscrollen dann die nächste Methode zeigt.
Vom neuen Terminal muss ich mich überzeugen lassen (nutze iTerm). Und "Full Line AI" stehe ich eh skeptisch gegenüber. Bugs schaff ich auch ohne AI einzubauen. ;-)
I like the idea behind the new sticky lines feature that #jetbrains released for #phpstorm - but I wish I could toggle which types of information I want sticking.
Having the namespace sticking is just sort of eating up a usable line for me.
Jetzt, wo ich Ausführung von phpstan, cs-fixer und codesniffer in #PHPStorm auch aktiviert habe scheint die Integration manchmal "abzustürzen". Dann werden Fehler einfach nicht mehr angezeigt, auch wenn ich das Projekt schliesse und wieder öffne. Nur PHPStorm Neustart hilft. Nutze lokales PHP Binary und lokales Filesystem (kein Docker). Kann ich das in PHPStorm irgendwo einsehen, ob/wo da ein Prozess hängt?
Are there any developers who have nailed using the Windows keymap for #PHPStorm on Mac?
I'm used to Windows, but my work laptop is a Mac. I'm using the XWin keymap which fixes some things, but of course all the shortcut hints are still in 'Mac language', so I have no clue what to type when I look one up.
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.
“Please complete this survey on a laptop or desktop. Some questions may not function properly on mobile devices.”
That’s a good way to ensure I don’t take your survey, since I’m probably only going to take it when I’m staring at my phone, trying to kill time somewhere.
@sashag The thing is, this is a survey for #JetBrains#PhpStorm, a tool I love and wouldn’t mind taking a survey for, but I’m traveling right now, and will probably not schedule time to remember to take it later.
Jeffrey Way's PhpStorm Setup in 2024 - Laravel News (laravel-news.com)
Jeffrey Way shares his PhpStorm set up.
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.