It’s a possibility to even fix them automatically! I like this feature, because it acts as a double-check for every commit I make, saving me the time to get back and fix my mistakes, or worse - let the SAT (Static Analysis Tool) or any other CI checks to find it.
#PHPSTORM PROJECT SETTINGS CODE#
Which one would you prefer to see in your IDE?Īdditionally, you can always rely on PhpStorm’s “Perform code analysis” check before commit - it will warn if any of the files included in the commit have problems found by inspections, allowing you to safely fix them before.
![phpstorm project settings phpstorm project settings](https://miro.medium.com/max/687/1*T1w1LeVbGx7Bx-GVEk1Mcw.png)
The example above provides the difference between a file with problems and without. It would be solved by having the same set-up. When I see yellow - it makes it hard to focus on what design problem are we solving, instead - I’m looking what are the mistakes the code. For example, they have default inspections enabled, which are not customised for the given project but I have it otherwise, changed a few things so I can safely rely on PhpStorm showing no problem markers in my window. You won’t be frustrated and will save brain power when working together with your peers because you will have the same IDE setup! When pairing with fellow developers, I have a problem, that our PhpStorm inspection settings are different. If any of these looks interesting for you, read on! Not using PhpStorm? Maybe your IDE has similar ways of sharing configuration? Increase the productivity of all your teams Allow different projects with unique configurations.Bring more clarity to difficult projects using scopes.Be easily informed of updated code guidelines.Save time in PRs by focusing only on important bits.Increase the productivity of all your teams.I feel these are the main benefits of versioning PhpStorm configuration: So I’ve set out to research and experiment with it, see what each of the files does and how can it benefit me and my teammates. idea folder into VCS, but adding it without understanding implications seemed odd. It made me wonder how can my tool help me? I’ve been using PhpStorm since the beginning of time, and the official JetBrains documentation recommends adding. I’m working at a company which has multiple GIT repositories and I see how developers spend hours configuring their PhpStorm, or just using defaults and wasting time fixing simple mistakes reported in a code review, which could’ve been fixed automatically. But do we? Do we know their true potential? How many times did you just blindly added.
#PHPSTORM PROJECT SETTINGS HOW TO#
Craftsmen are successful only when they know how to use their tools. Some smart people told me once, that knowing your tools well is one of the best ways to keep productive and focus on what really matters - delivering value to your customers.