In rare cases, the version corresponding to the `php` formula might not
be installed, but another alias is linked correctly. That means that the
PHP binary is found, but the core formula is not. PHP Monitor will
incorrectly report that it exists, which means the user can break their
PHP installation. Oops.
This quick fix handles that situation:
- Checks if the PHP binary for the `php` aliased version exists
(located in $optdir/php/bin/php)
- Disables the force load option if the aliased version is missing
(including a tweaked label if the version is missing)
Now correctly detects the following apps that can open a directory:
- PhpStorm (installed via Toolbox)
- Sublime Text
- Sublime Merge
This in addition to:
- PhpStorm (manual installation)
- Visual Studio Code
These need to be installed in the default location.
For VS Code to work, you need to have added `code` to your PATH.
* The information extracted from Homebrew's JSON command now also
includes information about linked keg and installations.
* The mapped versions in the App class now contain information about
the Homebrew installation as well.
* A HomebrewDiagnostics class has been added, which is currently able
to detect conflicts between the `php` formulae of core and the
`shivammathur/php` tap (which is currently an issue, see #54)
* Alerts are now displayed as critical if they are truly problematic.
* PhpInstallation was renamed to ActivePhpInstallation, to make room
for a generic PhpInstallation object which contains cached info.
* Shell.pipe() now returns the contents of standardError if
standardOutput was empty and there was some data in standardError.
This makes it easier to debug the output of commands that output to
standardError. (For example, failed brew commands might.)
