[Doc] Show how to install the phar by direct download #5274
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! |
|
Thank you for merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my highly opinionated mind, the correct way to install a tool like Psalm is to download a binary. This would be obvious for any PHP developer if the tool (psalm) was written in GoLang or Ruby. Nobody would ever see a Ruby tool and think "I wish I can download this with composer".
Don't get me wrong, the
psalm/pharpackage has its use cases, but it should not be the "standard way".Using
wgetto download a phar is the recommended way of PHPUnit.Since each release of psalm has the
psalm.pharattached to it, we can use this special link. See Github docs.