| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
This one has been there for so long we might need to do a deprecation cycle on it. Marking semver-major defensively. Ping @nodejs/ctc |
Sorry, something went wrong.
|
(to clarify, I would highly doubt that it's being used, but it pays to be safe) |
Sorry, something went wrong.
|
This needs some more reviews from @nodejs/ctc |
Sorry, something went wrong.
|
@jasnell I guess it is safe to land this as is? |
Sorry, something went wrong.
|
Perhaps we should ping @ChALkeR and ask him to please please please do a quick ecosystem search, just to be safe. We should also do a CITGM run just in case. It also needs CI |
Sorry, something went wrong.
|
CITGM https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/962 |
Sorry, something went wrong.
There was a problem hiding this comment.
Can we deprecate this like we normally do? It shouldn't cost anything. If it does, we will get complaints which will show it is being used.
Sorry, something went wrong.
|
It wouldn't hurt to deprecate it. |
Sorry, something went wrong.
|
Yep, I'm good with a regular deprecation. |
Sorry, something went wrong.
|
Thanks all. I will change to deprecate it first. |
Sorry, something went wrong.
|
Hi everyone, I updated this PR with deprecation. |
Sorry, something went wrong.
There was a problem hiding this comment.
Lgtm besides the nits.
Sorry, something went wrong.
There was a problem hiding this comment.
Would you mind escaping the underscore?
Sorry, something went wrong.
There was a problem hiding this comment.
Also the DEP ID is off.
Sorry, something went wrong.
There was a problem hiding this comment.
This should actually be DEP00XX until it lands. The person landing needs to assign the specific code.
Sorry, something went wrong.
There was a problem hiding this comment.
And the
Module._debug = util.deprecate(debug, 'Module._debug is deprecated.',
'DEP0076');should be DEP00XX also?
Sorry, something went wrong.
There was a problem hiding this comment.
Yeah, all of the DEP00.. identifiers.
Sorry, something went wrong.
The _debug of Module is undocumented and it useless here.
|
Hi all, I have updated this PR. |
Sorry, something went wrong.
|
@evanlucas the PR was updated with your suggestion. PTAL |
Sorry, something went wrong.
|
Our deprecation guidelines don't cover this. So I'll just ask here. Do we allow an undocumented API to be runtime deprecated directly without documenting and deprecating first? |
Sorry, something went wrong.
|
@thefourtheye that is a good point. I guess we should go ahead and improve the deprecation guidelines. I personally do not feel like it is the right thing to do to document a so far undocumented feature with the goal of actually removing it at some point as that is somewhat counterproductive. |
Sorry, something went wrong.
|
I think it's likely safe to dismiss @evanlucas' objection since this was changed to a deprecation as he requested. Evan is on vacation right now so may not be able to rereview soon |
Sorry, something went wrong.
Was changed to a deprecation as requested
Yes, so long as deprecations.md is updated appropriately. |
Sorry, something went wrong.
Sorry, something went wrong.
The _debug of Module is undocumented and it useless here. PR-URL: #13948 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Timothy Gu <timothygu99@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
The _debug of Module is undocumented and it useless here. PR-URL: nodejs/node#13948 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Timothy Gu <timothygu99@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
| Back | FazBrowse Home | New Git URL |
The _debug of Module is undocumented and it useless here.
Checklist
Affected core subsystem(s)
module