FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

net: export isIPv4, isIPv6 directly from cares by thefourtheye · Pull Request #7481 · nodejs/node · GitHub

/ node Public

net: export isIPv4, isIPv6 directly from cares - #7481

Closed
thefourtheye wants to merge 1 commit into
nodejs:masterfrom
thefourtheye:avoid-isIP-functions
Closed

net: export isIPv4, isIPv6 directly from cares#7481
thefourtheye wants to merge 1 commit into
nodejs:masterfrom
thefourtheye:avoid-isIP-functions

Conversation

thefourtheye commented Jun 29, 2016
edited
Loading

Copy link
Copy Markdown
Contributor
Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)

net

Description of change

The function objects encapsulating isIPv4 and isIPv6 are not
necessary. They can be directly exposed from cares.

CI Run: https://ci.nodejs.org/job/node-test-pull-request/3128/

The function objects encapsulating `isIPv4` and `isIPv6` are not
necessary. They can be directly exposed from `cares`.
thefourtheye added the net Issues and PRs related to the net subsystem. label Jun 29, 2016

cjihrig commented Jun 29, 2016

Copy link
Copy Markdown
Contributor

LGTM. Seems consistent with how isIP() is defined.

targos commented Jun 29, 2016

Copy link
Copy Markdown
Member

LGTM

2 similar comments

jasnell commented Jun 29, 2016

Copy link
Copy Markdown
Member

LGTM

Copy link
Copy Markdown
Member

LGTM

Copy link
Copy Markdown
Contributor Author

Landed in 3ae4377

thefourtheye deleted the avoid-isIP-functions branch July 8, 2016 14:45
thefourtheye added a commit that referenced this pull request Jul 8, 2016
The function objects encapsulating `isIPv4` and `isIPv6` are not
necessary. They can be directly exposed from `cares`.

PR-URL: #7481
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>

Copy link
Copy Markdown
Contributor

@thefourtheye lts? Likely should wait a couple releases first, but wanted to check in.

Copy link
Copy Markdown
Member

This should be able to go pretty safely into v4, yes.

evanlucas pushed a commit that referenced this pull request Jul 13, 2016
The function objects encapsulating `isIPv4` and `isIPv6` are not
necessary. They can be directly exposed from `cares`.

PR-URL: #7481
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
MylesBorins pushed a commit that referenced this pull request Aug 30, 2016
The function objects encapsulating `isIPv4` and `isIPv6` are not
necessary. They can be directly exposed from `cares`.

PR-URL: #7481
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
MylesBorins pushed a commit that referenced this pull request Sep 28, 2016
The function objects encapsulating `isIPv4` and `isIPv6` are not
necessary. They can be directly exposed from `cares`.

PR-URL: #7481
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
rvagg pushed a commit that referenced this pull request Oct 18, 2016
The function objects encapsulating `isIPv4` and `isIPv6` are not
necessary. They can be directly exposed from `cares`.

PR-URL: #7481
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
MylesBorins pushed a commit that referenced this pull request Oct 26, 2016
The function objects encapsulating `isIPv4` and `isIPv6` are not
necessary. They can be directly exposed from `cares`.

PR-URL: #7481
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
MylesBorins mentioned this pull request Oct 26, 2016
This file contains hidden or 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

net Issues and PRs related to the net subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants


Back | FazBrowse Home | New Git URL