-
-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(docs): remove $ sign from shell commands #458
Conversation
Hey @nhedger, thanks for bringing this up 👍 I agree with you that this is way more comfortable to copy and paste these single-lined commands. This fits ReactPHP's HTTP component perfectly, because it doesn't contain any multi-lined commands inside its README. The same adjustments should also be made for ReactPHP's other components (same case). As we're also maintaining other projects on GitHub (like Framework X etc.) we have to look at the bigger picture here. While this makes sense for single-lined commands I'm wondering if we should apply the same changes for multi-lined ones. For example:
or
The first example shows the executable command with its following output, removing the I don't want to bloat the whole topic, but please understand that we care about consistency across our multiple projects. I am curious what you think about this. |
curl http://localhost:8080/ Outputs:
|
Hey, Wasn't expecting a long answer for such a small change but I understand your concern so I'll try to explain my point of view. When a code block is annotated as The example output could easily live in another code block that is not annotated, right after. But to be fair, this PR isn't even about that, it was just a matter of simplifying the copy/paste experience. |
And this is why I'm in favour of it. What's you POV @clue ? |
@nhedger Thank you for this PR and sparking the discussion!
I agree the As such, I agree that we can safely remove this from all our docs. I'd like to make sure we do so consistently across all our components, so I'd love to see if anybody feels like picking this up and files a bunch of PRs linked against this original PR 👍 It's currently my understanding we can safely apply this to all single-line commands. Any code fences with multiple commands or commands with outputs may need a slightly bigger change to possibly split this into multiple code fences as suggested above or we may want to keep using the |
Thank you for the great effort @nhedger ! Merging this as most of your other PR's also have been merged at this point and the last 3 should be take long either. |
This PR removes the
$
sign from thebash
code blocks to allow copy/pasting their content as is.