Skip to content

doc: formatting issues for child_process docs #6911

Closed

Description

@mscdex
  • Version: v5.11.0+
  • Platform: n/a
  • Subsystem: doc, child_process

There are some formatting issues for exec() and execFile() in the child_process docs. Specifically:

  • f85412d erroneously added a backslash in front of an asterisk that was already contained within backticks. This causes the backslash to show up when rendered. The backslash can be safely removed. Fixed by ed11ac6.
  • The maxBuffer link is not styled like the other properties listed and looks out of place. My suggestion would be to have <code>-wrapped content within links to continue to have the same gray background color normally, but switch to the green background color on hover like normal links. There may be other instances of this in the docs, I have not checked.

Activity

  1. added
    child_processIssues and PRs related to the child_process subsystem.
    docIssues and PRs related to Node.js documentation.
    good first issueIssues that are suitable for first-time contributors.
    on May 21, 2016
  2. rodmachen commented on May 24, 2016

    @rodmachen
    Contributor

    I'm starting work on this issue.

    cc: @evanlucas

  3. lance commented on May 24, 2016

    @lance
    Member

    @rodmachen Sorry! Seems there was a race condition here.

  4. rodmachen commented on May 24, 2016

    @rodmachen
    Contributor

    I have fixed the "backslash in backticks" issue and that commit is included in the PR.

    The maxBuffer links are a larger question. Do we need to review styling of such links across all docs? Is this styling issue that needs to be broken out and worked on independently?

    I'm open to suggestions.

  5. mscdex commented on May 24, 2016

    @mscdex
    ContributorAuthor

    /cc @nodejs/documentation What does everyone think about the current styling of backtick-enclosed links?

  6. added a commit that references this issue on May 30, 2016
  7. added a commit that references this issue on Jun 2, 2016
  8. tanujasawant commented on Oct 7, 2016

    @tanujasawant
    Contributor

    May I work on this if there's more work to be done?
    Everything about maxBuffer seems fine except its appearance in the link is different because of <code>

  9. jasnell commented on May 30, 2017

    @jasnell
    Member

    @mscdex ... still an issue?

  10. mscdex commented on May 30, 2017

    @mscdex
    ContributorAuthor

    @jasnell This specific instance was fixed in ea5a2f4. But I think the general issue regarding the current styling of backtick-enclosed links may still be valid.

  11. maclover7 commented on Nov 26, 2017

    @maclover7
    Contributor

    Going to close out this issue since the maxBuffer specific problem was fixed. Please feel free to open a new issue regarding backtick-enclosed links if still necessary!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    child_processIssues and PRs related to the child_process subsystem.docIssues and PRs related to Node.js documentation.good first issueIssues that are suitable for first-time contributors.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions