I’m trying to run “Debug” (for step-debugging with #Xdebug) in #PhpStorm while running a #Pest test. I do this all the time with standard #PHPUnit tests, and I’ve never had this problem…
The test runner stops immediately, and PhpStorm reports in the debug console, “Test framework quit unexpectedly.”
Has anyone else seen this error? Do you know what causes it?
Switching back-and-forth between #CLion and #PhpStorm for the same project (so I can use intellisense and syntax highlighting on .php and .phpt files) is a pain in the ass, and for some reason, it corrupts the .idea folder, so I have to keep deleting it and letting the IDEs recreate it. #JetBrains
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.
Does #PhpStorm have any tools to help with resolving merge/rebase conflicts? I’m not finding anything, but maybe I’m searching for the wrong terms. #PHP
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
Did #PhpStorm recently change the way it connects to #Xdebug when executing tests from PhpStorm? I’m no longer able to get the debugger panel to work for a project that I’ve never had a problem using Xdebug in.
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
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.
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
Most of my #PhpStorm projects handle indentation of comment blocks properly, but sometimes, I’ll create a project in which PhpStorm behaves oddly. Like here.
How do I tell PhpStorm to properly indent these comment blocks automatically?
Anyone here use #PHPStorm and know how to change the appearance of the "Type hint" helpers in this JS code?
I find the : Element and : Date helpers extremely confusing to read and I'd prefer them formatted much more like the blocked out selectors: type helpers.
I can't find any way to change the style of those particular type hints tho.
#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.
I think it's a pretty good advice to clear caches within #PHPStorm now and then. It prevents from a lot of headache, when PHPStorm does not behave as expected once again. File -> Invalidate Caches...
Warning! Re-Indexing of projects might take some time!
When running tests “with Coverage” in any #JetBrains IDE, where does it store the coverage files?
My project is running in containers with docker compose, and this is all set up properly. In fact, the tests run, and presumably, the coverage report is generated, but the IDE doesn’t show the coverage, and I think it’s because it must be storing the coverage report on the container somewhere, and the IDE can’t access it when trying to display the lines covered.